I'm happy to announce a new virt-manager release, version 0.8.0. The release can be downloaded from:
http://virt-manager.org/download.html
The direct download link is:
http://virt-manager.org/download/sources/virt-manager/virt-manager-0.8.0.tar...
This release includes:
- New 'Clone VM' Wizard - Improved UI, including an overhaul of the main 'manager' view - System tray icon for easy VM access (start, stop, view console/details) - Wizard for adding serial, parallel, and video devices to existing VMs. - CPU pinning support (Michal Novotny) - Ability to view and change VM security (sVirt) settings (Dan Walsh) - Many bug fixes and improvements
Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback!
Thanks, Cole
Hello,
new virt-manager looks nice and is working well for me, but I have some comments:
- gray color for "Not Connected" hosts looks a bit cold. I have aprox 10 hosts configured and whole screen is cold. May be it will be nicer to add an image, like for running/stopped guest and also ability to connect/disconned by clicking on this image.
- host CPU usage is missing. In older virt-manager there was also CPU usage graphs on main screen for host, not only for guests
- guest CPU usage box is too high, if I have multiple hosts and guests, they need to be on multiple pages due to hight of this box.
- when tryed to force poweroff guest with older libvirt, guest was stopped, but python exception was raised. After update of libvirt from virt-preview repository this message disappeared.
- only one graph can be displayed. I have to choose, if I need network, disk or CPU graph and only one can be displayed. With older version there was multiple graphs available.
- in virt-manager icon on panel, can you please sort hosts in same order like in main window and may be hide "not connected" hosts (virt-manager icon can't do anything with non-connected hosts).
And one thing, which can make me happy. When I am trying virtual machines, I often reinstall existing one. Then I need to boot from network and after installation again from disk. I can't test new gPXE until it will work with my F11 kernel, may be it's better with this, but with currently functional bootrom I can't boot from disk if network boot is enabled and vice versa. If my guest is set to boot from disk (after previous installation) and I need to reinstall it, I have to do these steps:
- click details panel (i) - click "Boot Options" - click on "Boot Device" menu - select "Network (PXE)" and confirm (click) - click "Apply" - click back to guest console - click start (play button)
If my guest was running and I have to force it off, these additional steps are required:
- click on "v" button right of poweroff button - click force off - click "Yes"
Can this process be a bit simplified, 7-10 steps are too many. When testing development/rawhide systems, I have to repeat these steps multiple times. Do we really need this "Apply" button. I looked a bit to virt-manager sources and may be apply code can be called after boot device was changed.
These are only suggestions for improvements. You can ignore them, if you consider it non useful. :-)
Btw, virt-manager-0.8 in virt-preview can be useful. :-)
Thank you for a nice software.
SAL
On Tue, Jul 28, 2009 at 10:54:24PM -0400, Cole Robinson wrote:
I'm happy to announce a new virt-manager release, version 0.8.0. The release can be downloaded from:
http://virt-manager.org/download.html
The direct download link is:
http://virt-manager.org/download/sources/virt-manager/virt-manager-0.8.0.tar...
This release includes:
- New 'Clone VM' Wizard
- Improved UI, including an overhaul of the main 'manager' view
- System tray icon for easy VM access (start, stop, view console/details)
- Wizard for adding serial, parallel, and video devices to existing VMs.
- CPU pinning support (Michal Novotny)
- Ability to view and change VM security (sVirt) settings (Dan Walsh)
- Many bug fixes and improvements
Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback!
Thanks, Cole
On 29/07/09 11:21, Ján ONDREJ (SAL) wrote:
And one thing, which can make me happy. When I am trying virtual machines, I often reinstall existing one. Then I need to boot from network and after installation again from disk. I can't test new gPXE until it will work with my F11 kernel, may be it's better with this, but with currently functional bootrom I can't boot from disk if network boot is enabled and vice versa. If my guest is set to boot from disk (after previous installation) and I need to reinstall it, I have to do these steps:
- click details panel (i)
- click "Boot Options"
- click on "Boot Device" menu
- select "Network (PXE)" and confirm (click)
- click "Apply"
- click back to guest console
- click start (play button)
That's not a virt-manager issue, it's a qemu issue I assume.
It works for me though - if I have network boot selected that I can bring up the boot menu with F12 and select the hard disk instead?
What I suspect you may be referring to is the fact that if you don't have network boot set as the default then the F12 boot menu doesn't include the network option - so you can't be set to boot from the hard disk by default and then choose to boot from network instead using the boot menu.
I too find that rather annoying, but as I say it is (I believe) a qemu issue rather than a libvirt issue.
Tom
On Wed, Jul 29, 2009 at 11:30:41AM +0100, Tom Hughes wrote:
On 29/07/09 11:21, Ján ONDREJ (SAL) wrote:
And one thing, which can make me happy. When I am trying virtual machines, I often reinstall existing one. Then I need to boot from network and after installation again from disk. I can't test new gPXE until it will work with my F11 kernel, may be it's better with this, but with currently functional bootrom I can't boot from disk if network boot is enabled and vice versa. If my guest is set to boot from disk (after previous installation) and I need to reinstall it, I have to do these steps:
- click details panel (i)
- click "Boot Options"
- click on "Boot Device" menu
- select "Network (PXE)" and confirm (click)
- click "Apply"
- click back to guest console
- click start (play button)
That's not a virt-manager issue, it's a qemu issue I assume.
It works for me though - if I have network boot selected that I can bring up the boot menu with F12 and select the hard disk instead?
What I suspect you may be referring to is the fact that if you don't have network boot set as the default then the F12 boot menu doesn't include the network option - so you can't be set to boot from the hard disk by default and then choose to boot from network instead using the boot menu.
I too find that rather annoying, but as I say it is (I believe) a qemu issue rather than a libvirt issue.
I agree. On a real PC, I can press "F12" key to boot from PXE or to select different like preset boot device.
But virt-manager can simplify change to/from PXE, for example: - change input box for boot device to radius buttons - remove "Apply" button and apply automatically (at least if possible)
SAL
-
Cole Robinson -
Ján ONDREJ (SAL) -
Tom Hughes