From Fedora Project Wiki

< FWN‎ | Beats

(start new issue)
Line 41: Line 41:
 
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.
 
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.
  
At this time, the list of features approved for inclusion in Fedora 11 are:
+
Features approved for inclusion in Fedora 11 at this time are:
 
* http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
 
* http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
 
* http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
 
* http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
Line 47: Line 47:
 
* http://fedoraproject.org/wiki/Features/VirtVNCAuth
 
* http://fedoraproject.org/wiki/Features/VirtVNCAuth
  
Deferred to F12 was:
+
Deferred to Fedora 12 was:
 
* http://fedoraproject.org/wiki/Features/Shared_Network_Interface
 
* http://fedoraproject.org/wiki/Features/Shared_Network_Interface
 +
* http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge
  
Not addressed in the meeting was:
+
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
* http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge
+
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 />
 
<references />

Revision as of 21:27, 28 February 2009


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.

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.

Fedora Virt Status Update

TODO[1]

Improved Guest Mouse Pointer Movement

Daniel P. Berrange announced[1] an improvement to mouse pointer movement in Fedora 10 and 11 KVM 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." [2]

USB tablet will now be used by default Package-x-generic-16.pngpython-virtinst in F11.

Approved F11 Virtualization Features

Chris Lalancette relayed[1] the outcome of the FESCO meeting on February 27[2] as it relates to virtualization.

Features approved for inclusion in Fedora 11 at this time are:

Deferred to Fedora 12 was:

On the KVM and QEMU merge, Daniel P. Berrange explained[3] that "The QEMU upstream release will be so close to the feature freeze, that we don't want to risk causing KVM regressions by trying to then merge the two. Hopefully come F12, more of the KVM bits will be in QEMU mainline, so work we need todo to merge would be minimal."

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.


oVirt Devel List

This section contains the discussion happening on the ovirt-devel list.