(link some names) |
|||
| Line 35: | Line 35: | ||
==== Fedora Virt Status Update ==== | ==== Fedora Virt Status Update ==== | ||
Mark McLoughlin posted<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00093.html</ref> another weekly status update including details on numerous virtualization developments and bugs. | [[User:markmc|Mark McLoughlin]] posted<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00093.html</ref> another weekly status update including details on numerous virtualization developments and bugs. | ||
<references /> | <references /> | ||
==== Improved Guest Mouse Pointer Movement ==== | ==== 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. | [[DanielBerrange|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 | "The default mouse for KVM guests is a PS/2 mouse. This causes pain for users | ||
| Line 66: | Line 66: | ||
* http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge | * 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 | On the <code>KVM</code> and <code>QEMU</code> merge, [[DanielBerrange|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. | 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 | Hopefully come F12, more of the <code>KVM</code> bits will be in <code>QEMU</code> mainline, so | ||
| Line 87: | Line 87: | ||
==== About Libvirt VirtIO and Xen ==== | ==== About Libvirt VirtIO and Xen ==== | ||
Patrick Archibal had a few questions<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00422.html</ref> about virtualization and the relation of <code>libvirt</code><ref>http://www.libvirt.org/</ref>, <code>VirtIO</code><ref>http://wiki.libvirt.org/page/Virtio</ref>, <code>KVM</code><ref>http://kvm.qumranet.com/kvmwiki</ref>, and <code>Xen</code><ref>http://www.xen.org/</ref>. Daniel P. Berrange took the time to provide a detailed response<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00423.html</ref> to each of Patrick's questions. A selection follows. | Patrick Archibal had a few questions<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00422.html</ref> about virtualization and the relation of <code>libvirt</code><ref>http://www.libvirt.org/</ref>, <code>VirtIO</code><ref>http://wiki.libvirt.org/page/Virtio</ref>, <code>KVM</code><ref>http://kvm.qumranet.com/kvmwiki</ref>, and <code>Xen</code><ref>http://www.xen.org/</ref>. [[DanielBerrange|Daniel P. Berrange]] took the time to provide a detailed response<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00423.html</ref> to each of Patrick's questions. A selection follows. | ||
* What is the difference between <code>libvirt</code> and <code>virtio</code>? | * What is the difference between <code>libvirt</code> and <code>virtio</code>? | ||
| Line 117: | Line 117: | ||
Michael Kress wanted<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00479.html</ref> to encrypt the session between a windows <code>VNC</code> client and a <code>KVM</code> guest. The thread was long with a lot of back and forth touching on windows clients, certificate setup, and {{package|stunnel}}. | Michael Kress wanted<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00479.html</ref> to encrypt the session between a windows <code>VNC</code> client and a <code>KVM</code> guest. The thread was long with a lot of back and forth touching on windows clients, certificate setup, and {{package|stunnel}}. | ||
Daniel P. Berrange pointed out <code>libvirt</code>'s <code>RemoteTLS</code><ref>http://virt-manager.org/page/RemoteTLS</ref> documentation and described<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00526.html</ref> the Fedora 11 feature VirtVNCAuth<ref>http://fedoraproject.org/wiki/Features/VirtVNCAuth</ref> which dovetails with <code>VeNCrypt</code><ref>http://sourceforge.net/projects/vencrypt</ref> | [[DanielBerrange|Daniel P. Berrange]] pointed out <code>libvirt</code>'s <code>RemoteTLS</code><ref>http://virt-manager.org/page/RemoteTLS</ref> documentation and described<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00526.html</ref> the Fedora 11 feature VirtVNCAuth<ref>http://fedoraproject.org/wiki/Features/VirtVNCAuth</ref> which dovetails with <code>VeNCrypt</code><ref>http://sourceforge.net/projects/vencrypt</ref> | ||
to "Define a mapping of SASL authentication into the VNC protocol, and implement it for QEMU and GTK-VNC, providing strongly authenticated, securely encrypted remote access of virtual guest consoles." | to "Define a mapping of SASL authentication into the VNC protocol, and implement it for QEMU and GTK-VNC, providing strongly authenticated, securely encrypted remote access of virtual guest consoles." | ||
<references /> | <references /> | ||
Revision as of 20:18, 1 March 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
virt-manager Redesigned 'New VM' Wizard
Cole Robinson with the help of Tim Allen and Jeremy Perry
started[1] work on a resdesign of the 
virt-managerxen specific assumptions and the
state of libvirt/virtinst at the time: many of those assumptions don't
apply today, or require a bit more thought since we now support both
xen
and qemu based VMs." See the post for full details on the long list of changes and screenshots[2].
Hot Add USB Device to Guest
Cole Robinson answered[1] a question about hot adding a USB device to a running guest. The steps are
"Use 'lsusb' to determine the bus and device", use this to create an XML
snippet[2], and then feed that snippet to 'virsh attach-device.
Fedora Virtualization List
This section contains the discussion happening on the fedora-virt list.
Fedora Virt Status Update
Mark McLoughlin posted[1] another weekly status update including details on numerous virtualization developments and bugs.
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
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:
- 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 Fedora 12 was:
- http://fedoraproject.org/wiki/Features/Shared_Network_Interface
- http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge
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.
dom0 Kernel Experimentation Continues
Michael Young made his work more accessible when he began[1] creating experimental dom0 kernel builds[2] within Koji. This latest kernel has gotten as far as booting in single user mode.
Libvirt List
This section contains the discussion happening on the libvir-list.
About Libvirt VirtIO and Xen
Patrick Archibal had a few questions[1] about virtualization and the relation of libvirt[2], VirtIO[3], KVM[4], and Xen[5]. Daniel P. Berrange took the time to provide a detailed response[6] to each of Patrick's questions. A selection follows.
- What is the difference between
libvirtandvirtio?
"libvirt provides a API for the host OS, allowing management of virtual
machines, storage, networking, host devices, etc.
virtio is basically providing paravirtualized device drivers between guest
and host, and has several aspects
- A generic infrastructure layer in guest kernel for writing device drivers that talk to the host
- A generic host<->guest data transport running as a PCI device
- A generic host<->guest data transport using a ring buffer
- Guest implementations for paravirt network, disk & memory balloon drivers
- QEMU host backends for network, disk & memory balloon drivers"
- Why must hypervisor developers (
XenandKVM) develop drivers each time there are new devices?
"The virtio infrastructure is intended to provide generic drivers that can be
used on any hypervisor. Currently supports KVM and LGuest. Xen has its own
device drivers because they were developed years ago outside the context of
the Linux kernel community just for Xen's needs."
- Can we use
VirtIOwithXen?
"VirtIO is currently only supported for KVM and LGuest. It could in theory be implemented for Xen too, but its not clear if it is worth the effort."
Encrypted VNC to Guests and TLS
Michael Kress wanted[1] to encrypt the session between a windows VNC client and a KVM guest. The thread was long with a lot of back and forth touching on windows clients, certificate setup, and
Daniel P. Berrange pointed out libvirt's RemoteTLS[2] documentation and described[3] the Fedora 11 feature VirtVNCAuth[4] which dovetails with VeNCrypt[5]
to "Define a mapping of SASL authentication into the VNC protocol, and implement it for QEMU and GTK-VNC, providing strongly authenticated, securely encrypted remote access of virtual guest consoles."