[PATCH]: Make autogen.sh print out the right string at the end

Trivial fix for a simple cut-n-paste error, so that autogen.sh says "Now type
'make' to compile virt-viewer".

Signed-off-by: Chris Lalancette <clalance@...>

diff -r 09761c04bdcd autogen.sh
--- a/autogen.sh	Fri Jan 25 16:27:04 2008 -0500
+++ b/autogen.sh	Mon Mar 03 00:30:03 2008 -0500
@@ -45,5 +45,5 @@ cd $THEDIR

 $srcdir/configure --enable-warnings "$@" && {
     echo 
-    echo "Now type 'make' to compile gtk-vnc."
+    echo "Now type 'make' to compile virt-viewer."
 }

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools

[PATCH]: Disable accelerator keys when "grabbed"

Hello,
     Currently in virt-viewer, when you type either Alt-f, Alt-s, or Alt-h, the
accelerator for the menu on top kicks in.  That's fine, except that when the
pointer is grabbed, this is really not what the user expects; the user is
expecting that key combination to go through to the guest.  The attached patch
does this; basically it disables the accelerators when the pointer is grabbed,
and re-enabled them when the pointer is ungrabbed.

Signed-off-by: Chris Lalancette <clalance@...>

diff -r 09761c04bdcd src/main.c
--- a/src/main.c	Fri Jan 25 16:27:04 2008 -0500
+++ b/src/main.c	Mon Mar 03 04:53:00 2008 -0500
@@ -69,6 +69,26 @@ static const struct keyComboDef keyCombo
 	{ { GDK_Print }, 1, "_PrintScreen"},
 };

+enum menuNums {
+	FILE_MENU,
+	SEND_KEY_MENU,
+	HELP_MENU,
+	LAST_MENU // sentinel
+};
+
+struct menuItem {
+	guint menu;
+	GtkWidget *label;
+	const char *ungrabbed_text;
+	const char *grabbed_text;

FreeLinuxPC.org and a neat Cobbler trick/idea (WIP)

The UCLUG guys at FreeLinuxPC.org have a warehouse of 600 computers they 
are setting up to give away to kids that need them.

Before this happens, they need to be securely erased.   Now, we have 
instructions for using Cobbler to PXE DBAN (a secure erasure
tool), and they could set up one network for erasure and another network 
for installation, but, at least theoretically, is it possible for Cobbler
to install one OS (DBAN) and then install another right afterwards, 
using the Cobbler API to switch between them at reboot, so you don't have
to move machines between networks or issue any cobbler commands at 
all?   The theory is yes, though we're figuring this out.

This is a fun problem, a good cause, and a chance to abuse the Cobbler 
API some.   Here goes...

Scenario:
    -- You have a bunch of new machines come in off trucks
    -- You need Cobbler records for each of them (per MAC), but do not 
want to record them manually
    -- Each new machine should be securely erased.
    -- After the machine is erased, it should get a new OS.
    -- once the final OS is installed, the system should not be PXE'd again

Proposed Solution: 

-- First create two cobbler scripts using the Cobbler XMLRPC Read-Write 
API (to be provided later...stay tuned)
    -- add_system.cgi, which detects the MAC from HTTP vars and adds it 
to cobbler
    -- change_profile.cgi, which detects the MAC and takes a "profile" 

Re: FreeLinuxPC.org and a neat Cobbler trick/idea (WIP)

Michael DeHaan wrote:
> The UCLUG guys at FreeLinuxPC.org have a warehouse of 600 computers 
> they are setting up to give away to kids that need them.
>
> Before this happens, they need to be securely erased.   Now, we have 
> instructions for using Cobbler to PXE DBAN (a secure erasure
> tool), and they could set up one network for erasure and another 
> network for installation, but, at least theoretically, is it possible 
> for Cobbler
> to install one OS (DBAN) and then install another right afterwards, 
> using the Cobbler API to switch between them at reboot, so you don't have
> to move machines between networks or issue any cobbler commands at 
> all?   The theory is yes, though we're figuring this out.
>
> This is a fun problem, a good cause, and a chance to abuse the Cobbler 
> API some.   Here goes...
>
> Scenario:
>    -- You have a bunch of new machines come in off trucks
>    -- You need Cobbler records for each of them (per MAC), but do not 
> want to record them manually
>    -- Each new machine should be securely erased.
>    -- After the machine is erased, it should get a new OS.
>    -- once the final OS is installed, the system should not be PXE'd 
> again
>
> Proposed Solution:
> -- First create two cobbler scripts using the Cobbler XMLRPC 
> Read-Write API (to be provided later...stay tuned)
>    -- add_system.cgi, which detects the MAC from HTTP vars and adds it 

Koan Does VMware (it seems to work here, testing welcome)

Read about how to set it up here.

https://fedorahosted.org/cobbler/wiki/KoanDoesVmware

Having Cobbler managing your PXE infrastructure is a requirement since 
this a hybrid install method -- some parameters are pulled from Cobbler 
over XMLRPC, others are pulled from PXE (which we expect is Cobbler).

VMware can not be supported to the same level as the libvirt backed 
offerings, but this looks pretty good, and I welcome more testing and 
feature contributions from heavy users of VMware.   I've only tested 
this with the free VMware server.

--Michael

[Patch] delete button disable/available when Run/Shutdown a guest

Hi there,

Please help to review this little patch.

When you shutdown a guest in virt-manager, the Delete button status 
don't change, you have to click some other guest, then click back to 
this guest, and Delete button change to available.
Meanwhile, when you Run a stopped guest, the Delete button also don't 
change to disable automatically...

So add the attached patch for this problem.

Thanks,
Henry

diff -Nrup virt-manager-0.4.0.mod.5/src/virtManager/manager.py virt-manager-0.4.0.mod.6/src/virtManager/manager.py
--- virt-manager-0.4.0.mod.5/src/virtManager/manager.py	2008-02-15 20:26:11.000000000 +0800
+++ virt-manager-0.4.0.mod.6/src/virtManager/manager.py	2008-03-04 21:42:28.931255000 +0800
@@ -719,10 +719,12 @@ class vmmManager(gobject.GObject):
     def start_vm(self, ignore):
         vm = self.current_vm()
         vm.startup()
+        self.window.get_widget("vm-delete").set_sensitive(False)

     def stop_vm(self, ignore):
         vm = self.current_vm()
         vm.shutdown()
+        self.window.get_widget("vm-delete").set_sensitive(True)

Re: [Patch] delete button disable/available when Run/Shutdown a guest

Henry Zhang wrote:
> Hi there,
> 
> Please help to review this little patch.
> 
> When you shutdown a guest in virt-manager, the Delete button status 
> don't change, you have to click some other guest, then click back to 
> this guest, and Delete button change to available.
> Meanwhile, when you Run a stopped guest, the Delete button also don't 
> change to disable automatically...
> 
> So add the attached patch for this problem.
> 
> 
> Thanks,
> Henry
> 
> 

Hi,

This has actually already been fixed upstream:

http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=dc9c723e13ff

Things can move pretty fast so its always good to make sure you have
the latest checkout before submitting a patch.

Thanks,
Cole

Re: [PATCH] fix typos for virtinst

On Fri, Feb 29, 2008 at 03:04:15PM +0900, Atsushi SAKAI wrote:
> Hi,
> 
> It fix typos. 
> Before applying, ImageFetcher.py patch effects po file.
> Please care.
> 
>  man/en/virt-install.1    |    2 +-
>  virtinst/ImageFetcher.py |    2 +-
>  virtinst/OSDistro.py     |    2 +-
>  virtinst/util.py         |    2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)

I've applied this change, and also subsequently re-generated the .pot file
to contain latest translatable strings from the source.

Dan.
--

-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Re: [Patch] delete button disable/available when Run/Shutdown a guest

Hi,

Sure the change is so fast....

So I just noticed another problem, in virt-manager, most of GtkEntry 
widget can't recognize Enter, for example when create a guest, after 
input some characters for system name, then with Enter, it can't go 
forward to next step, you have to click Forward button. I think we 
should make the text entry sensitive to Enter. Same problem occur when 
try to input password for access VNC viewer...

Is there a patch ready for this problem?

Thanks,
Henry

Cole Robinson 写道:
> Henry Zhang wrote:
>> Hi there,
>>
>> Please help to review this little patch.
>>
>> When you shutdown a guest in virt-manager, the Delete button status 
>> don't change, you have to click some other guest, then click back to 
>> this guest, and Delete button change to available.
>> Meanwhile, when you Run a stopped guest, the Delete button also don't 
>> change to disable automatically...
>>
>> So add the attached patch for this problem.
>>

Re: a couple of questions -Newbie

On Tue, Mar 04, 2008 at 09:01:22AM -0700, Spencer Parker wrote:
> Now when I run virt-top with the script option it just hangs...how long 
> till it dies?  Or is there a way to daemonize it?

Which version of virt-top is this?

Script mode is designed to run forever.  If used in conjunction with
--csv then you'll get an ever longer CSV file.  But you also add
either '-n <iterations>' or '--end-time <time>'[1] to make it stop
early (or just kill it instead).

For example:

  virt-top -c test:///default --script --csv /tmp/test.csv -n 10

will run for 30 seconds, produce a 11 line (10 measurements + title)
CSV file, and then exit.  If it _doesn't_ do that, then please file a
bug.

The virt-top manpage explains all the options in some detail.

Rich.

[1] Various <time> formats as explained in the manpage.

--

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v