|
|
| Line 1: |
Line 1: |
| {{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 on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. |
| Line 10: |
Line 11: |
| === Fedora Xen List === | | === Fedora Xen List === |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. |
|
| |
| ==== DomU I/O Performance Sanity Check ====
| |
| [[AskHansen|Ask Bjørn Hansen]] asked[1] if the disk throughput he experienced matched what others see.
| |
| The dom0 host achieved 120MB/sec sequential write speed, and a domU only 22MB/sec.
| |
|
| |
| [[TroelsArvin|Troels Arvin's]] experiences with paravirt Xen on raw devices were fine for normal I/O but bad for low-level operations like file system creation. Troel also posted[3] some benchmark results in 2007.
| |
|
| |
| [1] https://www.redhat.com/archives/fedora-xen/2008-October/msg00012.html
| |
|
| |
| [2] https://www.redhat.com/archives/fedora-xen/2008-October/msg00013.html
| |
|
| |
| [3] http://article.gmane.org/gmane.comp.emulators.xen.user/29483
| |
|
| |
|
| === Libvirt List === | | === Libvirt List === |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. |
|
| |
| ==== sVirt Initial Prototype Release ====
| |
| [[JamesMorris|James Morris]] requested[1] comments on an initial prototype of <code>sVirt</code>[2] v0.10.
| |
| <code>sVirt</code> was first mentioned in FWN #138[3].
| |
|
| |
| "The purpose of this release is to establish a proof of concept of applying
| |
| security labels to VMs, and for discussion of the underlying technical approach."
| |
|
| |
| "With this release, it is possible to define a security label for a
| |
| <code>KVM</code>/<code>QEMU</code> domain in its XML configuration ('<code>virsh edit</code>'), launch the domain
| |
| and have it transition to the specified security label ('<code>virsh start</code>'),
| |
| then query the security label of the running domain ('<code>virsh dominfo</code>')."
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00478.html
| |
|
| |
| [2] http://www.selinuxproject.org/page/SVirt
| |
|
| |
| [3] http://fedoraproject.org/wiki/FWN/Issue138#sVirt_project_to_Integrate_SELinux_and_Linux-based_Virtualization
| |
|
| |
| ==== Hot-add SCSI/VirtIO Disks for KVM Guests ====
| |
| [[GuidoGünther|Guido Günther]] supplied[1] a patch to add hot plugging and
| |
| unplugging[2] of SCSI/VirtIO disks for <code>KVM</code> guests.
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00391.html
| |
|
| |
| [2] https://www.redhat.com/archives/libvir-list/2008-October/msg00427.html
| |
|
| |
| ==== Domain Events Support Completed ====
| |
| After three[1] rounds, [[BenGuthro|Ben Guthro's]] domain events patches have been committed. This major API addition led[2] [[DanielVeillard|Daniel Veillard]] to speculate that the next release version number may jump to 0.5.0. Domain events are only emitted from <code>KVM</code> guests. The other hypervisor drivers will require more work to properly emit domain events.
| |
|
| |
| The <code>python</code> bindings are forthcoming. [3]
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00537.html
| |
|
| |
| [2] https://www.redhat.com/archives/libvir-list/2008-October/msg00594.html
| |
|
| |
| [3] https://www.redhat.com/archives/libvir-list/2008-October/msg00598.html
| |
|
| |
|
| === oVirt Devel List === | | === oVirt Devel List === |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list]. | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list]. |
|
| |
| ==== New Model for Network Interface Configuration ====
| |
| [[DanielBerrange|Daniel P. Berrange]] offered[1] that
| |
| "network configuration UI discussions have all focused around
| |
| the idea of configuring NICs on machines" and this is the wrong model. Adding,
| |
| "if we can model a network as a global entity in its own right,
| |
| we can simplify configuration of host interfaces" to "simply a
| |
| matter of association, and optionally defining an address."
| |
|
| |
| "So this kind of modelling can make our UI for setting up host networking
| |
| much clearer / simpler, avoiding lots of redundant questions. Also, by
| |
| having an explicit 'network <-> interface <-> host' assoication, we
| |
| can trivally determine whether it is possible to migrate between two
| |
| hosts from a network topology POV - its merely checking one DB relation."
| |
|
| |
| This idea was met with acceptance.
| |
|
| |
| [1] https://www.redhat.com/archives/ovirt-devel/2008-October/msg00325.html
| |
|
| |
|
| |
| Daniel illustrated[2] the concept with the following entity relationship diagram.
| |
| <pre>
| |
| 1 n n 1
| |
| Network <-----> Interface <----> Node
| |
| ^ 1 ^ 1
| |
| | |
| |
| V n V n
| |
| NetAddress Address
| |
| </pre>
| |
|
| |
| [[MohammedMorsi|Mohammed Morsi]] created[3] a UML diagram[4] of the model as
| |
| well.
| |
|
| |
| [2] https://www.redhat.com/archives/ovirt-devel/2008-October/msg00330.html
| |
|
| |
| [3] https://www.redhat.com/archives/ovirt-devel/2008-October/msg00348.html
| |
|
| |
| [4] http://www.ovirt.org/page/Redesigned_Network_Configuration
| |
|
| |
| Interface configuration was recently discussed in this[5] thread as well.
| |
|
| |
| [5] https://www.redhat.com/archives/ovirt-devel/2008-October/msg00234.html
| |
