From Fedora Project Wiki

< FWN‎ | Beats

 
(130 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
{{Anchor|Virtualization}}
 
{{Anchor|Virtualization}}
 +
  
 
== 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
 +
@fedora-virt list.
  
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
=== Enterprise Management Tools List ===
 
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
 
 
====  ====
 
<references />
 
  
 
=== Fedora Virtualization List ===
 
=== Fedora Virtualization List ===
Line 19: Line 14:
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
  
==== Adding a VM to Virtual Machine Manager ====
+
==== Virt Status Report ====
Dennis J.  asked<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00026.html</ref>
+
[[JustinForbes|Justin Forbes]]
"How do I add a custom-built vm to {{package|virt-manager}}?"
+
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.
 +
Justin pointed out F13 bugs<ref>http://fedoraproject.org/wiki/Virtualization_bugs</ref> now include Important and Pony classifications in addition to Blocker and Target.
  
This is a two step process with a few ways to accomplish them.
+
<references />
# Create an XML representation<ref>http://www.libvirt.org/formatdomain.html</ref> of the guest, or domain, configuration.
 
# Import this definition into {{package|libvirt}}. i.e. <code>virsh define guest.xml</code>
 
  
The {{package|python-virtinst|virt-image}}<ref>http://people.redhat.com/dlutter/virt-image/virt-image-xml.html</ref>
+
==== RHEL and Fedora Virtualization Feature Parity ====
tool was suggested and worked for Dennis.
+
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
There is also a perl script<ref>http://fedoraproject.org/wiki/FWN/Issue174#Virt-Manage_an_Existing_Guest</ref> that can be used to create an XML definition from the set of <code>qemu-kvm</code> command line arguments used to create the guest. There is a public API in <code>libvirt</code> for converting back and forth between the native hypervisor configurations and XML representations.<ref>http://fedoraproject.org/wiki/FWN/Issue176#Converting_Between_Domain_XML_and_Native_Configurations</ref>
+
compared to Fedora 12.
  
Finally, <code>virt-install</code> added an <code>--import</code> option which allows creating a guest from an existing disk image, bypassing any OS install phase.<ref>http://fedoraproject.org/wiki/FWN/Issue166#New_Release_virtinst_0.4.2</ref>
+
[[DanielBerrange|Daniel Berrange]]
 +
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
 +
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
 +
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
 +
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
 +
also pretty close to that using what's best described as a hybrid of
 +
kvm-83 and kvm-84."
  
 
<references />
 
<references />
  
==== libosinfo: Library for Virt OS/distro Metadata ====
 
[[ColeRobinson|Cole Robinson]]
 
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00100.html</ref> a request for comments on "the initial work for a new library, <code>libosinfo</code><ref>http://fedorapeople.org/~crobinso/osinfo/</ref> (better name
 
recommendations appreciated). This library will provide OS meta data for use
 
in virt applications, replacing the dictionary we currently keep in
 
{{package|python-virtinst|virtinst}}." The work was based on
 
a post<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00028.html</ref> by [[DanielBerrange|Daniel Berrange]].
 
  
 +
====  ====
 
<references />
 
<references />
 
=== Fedora Xen List ===
 
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
  
 
====  ====
 
====  ====
<references />
 
 
=== Libvirt List ===
 
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
 
==== VNC Authorization per Guest  ====
 
[[ChristianWeyermann|Christian Weyermann]]
 
asked<ref>http://www.redhat.com/archives/libvir-list/2009-June/msg00090.html</ref>
 
how to restrict "users to only be able to connect to their own virtual machines via VNC."
 
 
[[DanielBerrange|Daniel Berrange]]
 
said "there is no way to
 
specify authorization data on a per-VM basis. So if you authenticate
 
successfully you have access."
 
 
[[HughBrock|Hugh Brock]]
 
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
 
anyone to actually do the work yet... patches welcome :)"
 
 
 
<references />
 
<references />

Latest revision as of 18:09, 18 December 2009



Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @fedora-virt list.

Contributing Writer: Dale Bewley

Fedora Virtualization List

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

Virt Status Report

Justin Forbes posted[1] a Fedora virtualization status report. Justin pointed out F13 bugs[2] now include Important and Pony classifications in addition to Blocker and Target.

RHEL and Fedora Virtualization Feature Parity

Robert Day wondered how the virtualization features[1] of Red Hat Enterprise Linux 5.4 compared to Fedora 12.

Daniel Berrange explained[2] "The KVM based virtualization in RHEL-5.4 is not nearly so far behind Fedora as you might think. The Package-x-generic-16.pnglibvirt mgmt stack in RHEL-5.4 was rebased to be near parity with Fedora 11, and KVM in RHEL-5.4 is also pretty close to that using what's best described as a hybrid of kvm-83 and kvm-84."