FWN/Beats/Virtualization: Difference between revisions

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]

↑ http://www.redhat.com/archives/fedora-virt/2009-February/msg00093.html

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 python-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.

At this time, the list of features approved for inclusion in Fedora 11 are:

Deferred to F12 was:

http://fedoraproject.org/wiki/Features/Shared_Network_Interface

Not addressed in the meeting was:

http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge

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.

@@ Line 4: / Line 4: @@
 == 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: [[User:Dale | Dale Bewley]]
@@ Line 12: / Line 12: @@
 [http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
-==== New Options for Guest Cloning ====
+====  ====
-Cole Robinson posted<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00051.html</ref> a patch to enable <code>virt-install</code> to
-"build a guest around an existing disk image, skipping the OS install step."
-Cole also
-posted<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00050.html</ref>
-a patch for <code>virt-clone</code> which allows for cloning from an XML file
-"rather than require the use of a guest defined on the current connection."
-<references />
-==== Obtaining Guest IP Address from the Host ====
-Thomas Mackell inquired<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00036.html</ref> about a way to obtain the IP address of a guest that was easier than logging into it and running <code>ifconfig</code>. Cole Robinson pointed out {{package|virt-mem}}<ref>http://et.redhat.com/~rjones/virt-mem/</ref> which is a collection of utilities for interrogating <code>KVM</code> guests. Tools included are
-<code>virt-uname</code>, <code>virt-dmesg</code>, <code>virt-ps</code>, and <code>virt-ifconfig</code>.
 <references />
@@ Line 33: / Line 20: @@
 ==== Fedora Virt Status Update ====
-Mark McLoughlin posted two<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00077.html</ref>
+TODO<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00093.html</ref>
-<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00078.html</ref> very detailed weekly status reports since the last FWN Virtualization beat. Each one is full of details on the latest bugs and developments in the field.
+<references />
+==== 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 />
-==== Qemu Packaging and noarch BIOS Firmware ====
+==== Approved F11 Virtualization Features ====
-The process <ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00066.html</ref> of building BIOS firmwares to support architecturally diverse guests on architecturally diverse hosts
+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.
-is very involved and repetitive. Glauber Costa learned<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00068.html</ref> of changes coming to [[Koji]] which could simplify the process by allowing for bundled BIOS images to be built as "<code>noarch</code>" RPMs. These would be readily available to hosts on any architecture in the repository. Save for some "second class citizens"<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00072.html</ref> in the repo.
+At this time, the list of features approved for inclusion in Fedora 11 are:
+* http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
+* http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
+* http://fedoraproject.org/wiki/Features/VirtImprovedConsole
+* http://fedoraproject.org/wiki/Features/VirtVNCAuth
+Deferred to F12 was:
+* http://fedoraproject.org/wiki/Features/Shared_Network_Interface
+Not addressed in the meeting was:
+* http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge
 <references />
@@ Line 48: / Line 59: @@
 [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
-==== dom0 Kernel Experimentation Continues ====
+====  ====
-Michael Young continued<ref>http://www.redhat.com/archives/fedora-xen/2009-February/msg00031.html</ref> to help others experiment with the nacent dom0 support in the {{package|kernel}} and posted another RPM. There are still significant problems precluding its use for anything beyond testing.
 <references />
@@ Line 57: / Line 66: @@
 [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
-==== Support for Snapshot Volumes ====
+====  ====
-Nick Moffitt asked<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00195.html</ref> "Is there any interface to <code>libvirtd</code> that allows it to create volumes that are snapshots of existing volumes?"
-Daniel P. Berrange pointed<ref>http://libvirt.org/formatstorage.html#StorageVolBacking</ref> out this feature was recently added to {{package|libvirt}} 0.6.0.
-"Basically when creating a storage volume, you just need to pass information about the backing storage volume. It'll thus create a volume which is a snapshot of this backing store."
 <references />
-==== netcf Network Interface Configuration Library ====
+=== oVirt Devel List ===
-David Lutterkort has been working on the disconnect between
+This section contains the discussion happening on the
-{{package|libvirt}} and host network interface configuration for some time.
+[http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
-(See FWN#159 "Configuring Host Interfaces RFC")
-<ref>http://fedoraproject.org/wiki/FWN/Issue159#Configuring_Host_Interfaces_RFC</ref>
-"After talking with Dan Williams, who is working in {{package|NetworkManager}}", it became<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00228.html</ref> clear to David that solving this problem "is also
-useful for NM and would help them with handling system-wide interface
-configuration." David then began work on <code>netcf</code><ref>http://git.et.redhat.com/?p=netcf.git;a=tree</ref>
-Mark McLoughlin complimented<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00229.html</ref>
-the work and updated the shared network interface feature page<ref>http://fedoraproject.org/wiki/Features/Shared_Network_Interface</ref>. The goal of this feature in development is to "Enable guest virtual machines to share a physical network interface (NIC) with other guests and the host operating system. This allows guests to independently appear on the same network as the host machine."
+====  ====
 <references />

Search