- 1 Virtualization
- 1.1 Enterprise Management Tools List
- 1.2 Fedora Virtualization List
- 1.3 Fedora Xen List
- 1.4 Libvirt List
In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies.
Contributing Writer: Dale Bewley
Enterprise Management Tools List
This section contains the discussion happening on the et-mgmt-tools list
New Release virt-manager 0.7.0
Virtual Machine Manager provides a graphical tool for administering virtual
QEmu. Start, stop, add or remove virtual devices,
connect to a graphical or serial console, and see resource usage statistics
for existing VMs on local or remote machines. Uses
as the backend
- Redesigned 'New Virtual Machine' wizard (Jeremy Perry, Tim Allen, Cole Robinson)
- Option to remove storage when deleting a virtual machine.
- File browser for libvirt storage pools and volumes, for use when attaching storage to a new or existing guest.
- Physical device assignment (PCI, USB) for existing virtual machines.
- Bug fixes and minor improvements.
New Release virtinst 0.4.3
virtinst is a module that helps build and install
libvirt based virtual
machines. It currently supports
Xen virtual machines. Package
includes several command line utilities, including
and install new VMs) and
virt-clone (clone an existing virtual machine).
This is largely a bug fix release.
Fedora Virtualization List
This section contains the discussion happening on the fedora-virt list.
Serial Console Support in virt-manager
Jan ONDREJ tested the new
0.7.0 on Fedora 10, and had some suggestions.
Starting an domain starts my serial console owned by root and is not accesssible from virt-manager (virt-viewer). After changing ownership it's immediatelly available. Is it possible to change this in time of virtual machine creation? (in libvirt or where?) Another feature enhacement can be adding "Serial 0" tab automatically, when there is no Console available for guest. Message "Console not configured for guest" can be sometimes misinterpretated, because I can have serial console for my guest. I prefer to use serial consoles, because they do not need to install graphical environment on host. They have multiple advantages, like access from another machine using serial or ipmi console, viewing crash status, when host crashes, ... And last possible enhancement: when pressing F10 key in guest's serial console, is it possible to avoid opening of "File menu" and send this key to serial 0, as it is done in VGA console?
Yes, this is one of the drawbacks of not running virt-manager as root: since the qemu:///system libvirt connection will launch your guests as root, a regular user won't be able to access ptys. I don't know of a proper solution to it all, other then running the app as root or changing the the pty permissions as you did. > Another feature enhacement can be adding "Serial 0" tab automatically, > when there is no Console available for guest. Message "Console not > configured for guest" can be sometimes misinterpretated, because I can have > serial console for my guest. I see what you mean. The wording could certainly be better, and It would make sense to try to connect to the serial console if no graphics device is attached. Thanks for the idea. > > And last possible enhancement: when pressing F10 key in guest's serial > console, is it possible to avoid opening of "File menu" and send this key to > serial 0, as it is done in VGA console? > We would probably need some sort of keygrab process like we do for VNC to get this right. Not sure if that's even an option for the VTE widget though.
Fedora Xen List
This section contains the discussion happening on the fedora-xen list.
dom0 Kernel: Better, Still Not Ready
Michael explained, "The current plan is to wait until basic
dom0 support makes it into the vanilla
kernel, which should happen for 2.6.30, and then decide if
dom0 can be enabled and if the patches for full
dom0 support can safely be added without affecting ordinary operation."
"At the moment there are still things that are broken such as
X support in some cases, and there are also Fedora patches that have been omitted because they were tricky to merge, so it is too early to start adding
dom0 support to official Fedora kernels."
Missing Hypervisor Capabilities Restored
This section contains the discussion happening on the libvir-list.
In an attempt to make it easier to backup
KVM windows guests,
virsh function. "Modelled on the
virDomainSave function it takes
an optional script which it will execute (and pass the name of the
domain as an argument) while the domain is paused, then resume the
domain." Within this script, a backup of the guest domain could be created.
The patch was seen as too ad-hoc, and not accepted as-is.
"I think this can help administrators in a controlled situation,
but I'm hoping a real snapshotting API will be possible at some point
goes though the list of storage resources used by the
domain and properly make a snapshot using a storage API or return
an error if that's not possible."
Daniel P. Berrange
what he would like to see.
"In terms of API I think I'd like to see
snapshotting available as part
of a more generic save/restore API. I tend to think of the current API
as providing 'unmanaged save/restore'". Libvirt does not track saved images,
so does not know if a snapshot is available to be started at the restart of
"Thus I think the first step towards a general snapshot facility would
be to provide an API for 'managed save/restore' where we explicitly
track saved images."
"With this, you could configure
libvirtd, so that when starting up, it"
would "see if the guest was suspended before
the previous host shutdown, and if so, then restore from that saved
image automatically. Or make it skip autostart completely, if any save
images exist, and allow an admin defined initscript to do auto restore
from the save image."
Memory Ballooning Support for QEMU
Daniel P. Berrange patched the QEMU driver to fully suport full memory ballooning.