| Line 4: | Line 4: | ||
== Virtualization == | == Virtualization == | ||
In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-xen-list, and @libvirt-list lists. | In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-virt, @fedora-xen-list, and @libvirt-list lists. | ||
Contributing Writer: [[User:Dale | Dale Bewley]] | Contributing Writer: [[User:Dale | Dale Bewley]] | ||
=== Fedora Virtualization List === | === Fedora Virtualization List === | ||
| Line 43: | Line 36: | ||
a post<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00028.html</ref> by [[DanielBerrange|Daniel Berrange]]. | a post<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00028.html</ref> by [[DanielBerrange|Daniel Berrange]]. | ||
<references /> | <references /> | ||
| Line 64: | Line 50: | ||
said "there is no way to | said "there is no way to | ||
specify authorization data on a per-VM basis. So if you authenticate | specify authorization data on a per-VM basis. So if you authenticate | ||
successfully you have access." | successfully you have access." [[HughBrock|Hugh Brock]] | ||
[[HughBrock|Hugh Brock]] | |||
added<ref>http://www.redhat.com/archives/libvir-list/2009-June/msg00137.html</ref> | added<ref>http://www.redhat.com/archives/libvir-list/2009-June/msg00137.html</ref> | ||
"It is on our wish list for Real Soon Now, but we haven't identified | "It is on our wish list for Real Soon Now, but we haven't identified | ||
Revision as of 04:44, 15 June 2009
Virtualization
In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-virt, @fedora-xen-list, and @libvirt-list lists.
Contributing Writer: Dale Bewley
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 
virt-manager
This is a two step process with a few ways to accomplish them.
- Create an XML representation[2] of the guest, or domain, configuration.
- Import this definition into
libvirtvirsh define guest.xml
The 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]
- ↑ http://www.redhat.com/archives/fedora-virt/2009-June/msg00026.html
- ↑ http://www.libvirt.org/formatdomain.html
- ↑ http://people.redhat.com/dlutter/virt-image/virt-image-xml.html
- ↑ http://fedoraproject.org/wiki/FWN/Issue174#Virt-Manage_an_Existing_Guest
- ↑ http://fedoraproject.org/wiki/FWN/Issue176#Converting_Between_Domain_XML_and_Native_Configurations
- ↑ http://fedoraproject.org/wiki/FWN/Issue166#New_Release_virtinst_0.4.2
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
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 :)"