From Fedora Project Wiki


In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list lists.

Contributing Writer: Dale Bewley

Enterprise Management Tools List

This section contains the discussion happening on the et-mgmt-tools list

Fedora Virtualization List

This section contains the discussion happening on the fedora-virt list.

best Fedora virtualization

Rich Mahn asked[1]

I am planning on running several virtual machines on a single host.  I
will have two or three Linux baeed virtual machines and one or two
Windoze.  I plan on using a F11 host system.

I need most of these to run automatically on boot-up of the host
system.  It would be really nice if I could use something like the
Ctl-Alt-FN to be able to access and switch between virtual machines.
This needs to be stable.  The machines that these virtual machines are
intended to replace are often running hundreds of days between

My gut feel is that the virt-manager suite might be the way to go,
editting the apropriate xml files as required.  I also see there
is a qemu launcher and it seems to work okay.  I suspect there are
others as well.

What tends to be the consensus here on the various virtual machine
managers?  Are there white papers somewhere that could give some

Richard Jones answered[2]

For stability and long-term maintainability, I wonder if you've
considered using RHEL or CentOS?  That means you have to use Xen as
the hypervisor, but if you use libvirt / virsh / virt-manager, the
future upgrade path to KVM is reasonable.  All tools stay the same,
and you just need to run our forthcoming v2v tool on the guests (or
reinstall the guests) when you upgrade.
The only one we're supporting here on
Fedora<ref></ref> is libvirt / virsh /
virt-manager.  Use 'virsh edit <domain>' to edit the XML for a domain.
The same commands will work on RHEL / CentOS too.

Rich Mahn reported problems with ISO images stored on NFS and Gene Czarcinski opened[3] a bug (RHBZ #508865

I suspect this is the result of trying to use SELinux to protect everything 
and the mandatory access control idea that everything is disallowed except 
that which is explicitly permitted.

But, I just do not understand what and why CD/DVD images and devices are being 
protected.  Furthermore, when virtualization changes a file's context 
(including /dev/sr0), could this effect other valid usage of these 
files/devices?  If there is no effect for other applications, then just what is 


Libvirt List

This section contains the discussion happening on the libvir-list.