- 1 Virtualization
- 1.1 Enterprise Management Tools List
- 1.2 Fedora Virtualization List
- 1.3 Fedora Xen List
- 1.4 Libvirt List
- 1.5 oVirt Devel List
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
Improved Guest Mouse Pointer Movement
Daniel P. Berrange announced an improvement to mouse pointer movement in Fedora 10 and 11
"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." 
Approved F11 Virtualization Features
Features approved for inclusion in Fedora 11 at this time are:
Deferred to Fedora 12 was:
QEMU merge, Daniel P. Berrange explained 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.
This section contains the discussion happening on the libvir-list.
About Libvirt VirtIO and Xen
Patrick Archibal had a few questions about virtualization and the relation of
Xen. Daniel P. Berrange took the time to provide a detailed response to each of Patrick's questions. A selection follows.
- What is the difference between
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 (
KVM) develop drivers each time there are new devices?
virtio infrastructure is intended to provide generic drivers that can be
used on any hypervisor. Currently supports
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
"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 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
RemoteTLS documentation and described the Fedora 11 feature VirtVNCAuth which dovetails with
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."
oVirt Devel List
This section contains the discussion happening on the ovirt-devel list.