From Fedora Project Wiki

< FWN‎ | Beats

 
(252 intermediate revisions by 3 users not shown)
Line 2: Line 2:


{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


== Virtualization ==
== Virtualization ==
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.  
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].


==== Fedora Virt Status Update ====
==== Virt Status Report ====
TODO<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00093.html</ref>
[[JustinForbes|Justin Forbes]]
<references />
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.
==== Improved Guest Mouse Pointer Movement ====
Daniel P. Berrange announced<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00083.html</ref> an improvement to mouse pointer movement in Fedora 10 and 11 <code>KVM</code> guests.
 
"The default mouse for KVM guests is a PS/2 mouse. This causes pain for users
because it only works with relative coordinates, which means we are forced to
grab the mouse pointer in the VNC client.
 
KVM can emulate a USB graphics tablet which works in absolute coordinate mode,
and thus gives flawless mouse motion tracking without needing any grab in the
client." <ref>https://bugzilla.redhat.com/show_bug.cgi?id=487025</ref>
 
USB tablet will now be used by default {{package|python-virtinst}} in F11.


<references />
<references />


==== Approved F11 Virtualization Features ====
==== RHEL and Fedora Virtualization Feature Parity ====
Chris Lalancette relayed<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00097.html</ref> the outcome of the [[FESCO]] meeting on February 27<ref>http://fedoraproject.org/wiki/Extras/SteeringCommittee/Meeting-20090227</ref> as it relates to virtualization.
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
compared to Fedora 12.


Features approved for inclusion in Fedora 11 at this time are:
[[DanielBerrange|Daniel Berrange]]
* http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
* http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
* http://fedoraproject.org/wiki/Features/VirtImprovedConsole
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
* http://fedoraproject.org/wiki/Features/VirtVNCAuth
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."


Deferred to Fedora 12 was:
* http://fedoraproject.org/wiki/Features/Shared_Network_Interface
* http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge
On the <code>KVM</code> and <code>QEMU</code> merge, Daniel P. Berrange explained<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00094.html</ref> that "The <code>QEMU</code> upstream release will be so close to the feature freeze, that we don't
want to risk causing <code>KVM</code> regressions by trying to then merge the two.
Hopefully come F12, more of the <code>KVM</code> bits will be in <code>QEMU</code> mainline, so
work we need todo to merge would be minimal."
<references />
=== Fedora Xen List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
====  ====
<references />
<references />


=== Libvirt List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].


====  ====
====  ====
<references />
<references />
=== oVirt Devel List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].


====  ====
====  ====
<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."