From Fedora Project Wiki


In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-xen-list, and @libvirt-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.

Adding a VM to Virtual Machine Manager

Dennis J. asked[1] "How do I add a custom-built vm to Package-x-generic-16.pngvirt-manager?"

This is a two step process with a few ways to accomplish them.

  1. Create an XML representation[2] of the guest, or domain, configuration.
  2. Import this definition into Package-x-generic-16.pnglibvirt. i.e. virsh define guest.xml

The Package-x-generic-16.pngvirt-image[3] tool was suggested and worked for Dennis. There is also a perl script[4] that can be used to create an XML definition from the set of qemu-kvm command line arguments used to create the guest. There is a public API in libvirt for converting back and forth between the native hypervisor configurations and XML representations.[5]

Finally, virt-install added an --import option which allows creating a guest from an existing disk image, bypassing any OS install phase.[6]

libosinfo: Library for Virt OS/distro Metadata

Cole Robinson posted[1] a request for comments on "the initial work for a new library, libosinfo[2] (better name recommendations appreciated). This library will provide OS meta data for use in virt applications, replacing the dictionary we currently keep in Package-x-generic-16.pngvirtinst." The work was based on a post[3] by Daniel Berrange.

Fedora Xen List

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

Libvirt List

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

VNC Authorization per Guest

Christian Weyermann asked[1] how to restrict "users to only be able to connect to their own virtual machines via VNC."

Daniel Berrange said "there is no way to specify authorization data on a per-VM basis. So if you authenticate successfully you have access."

Hugh Brock added[2] "It is on our wish list for Real Soon Now, but we haven't identified anyone to actually do the work yet... patches welcome :)"