|
|
| (456 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | [[Category:Virtualization]] <!-- do not copy into FWN issue --> |
| | |
| {{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 of Fedora virtualization technologies on the |
| | | @fedora-virt list. |
| Contributing Writer: [[DaleBewley | Dale Bewley]]
| |
| | |
| === Enterprise Management Tools List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
| |
| | |
| ==== Virt-manager 0.6.0 Released ====
| |
| [[ColeRobinson|Cole Robinson]] announced[1] the release of virt-manager[2] 0.6.0.
| |
| Features include:
| |
| * Remote storage management and provisioning
| |
| * Remote VM installation
| |
| * Use Avahi to list libvirtd instances
| |
| * Virtio and USB options when adding a disk device
| |
| and many more.
| |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00026.html
| |
| | |
| [2] http://www.virt-manager.org
| |
| | |
| ==== Virtinst 0.400.0 Released ====
| |
| [[ColeRobinson|Cole Robinson]] announced[1] the release of virtinst 0.400.0.
| |
| Features include:
| |
| * New tool 'virt-convert'
| |
| * New tool 'virt-pack'
| |
| * Support for remote VM installation
| |
| * Use virtio disk/net drivers if chosen os entry supports it
| |
| and many more.
| |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00027.html
| |
| | |
| === Fedora Xen List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
| |
| | |
| ==== Laying the Groundwork for Xen Domain 0 Support ====
| |
| There are further developments in the state of Xen in upstream Linux (see FWN#137[3]). Pasi Kärkkäinen forwarded[1] a patch announcement[2] from xen-devel list. This set of seven patches begin to lay the groundwork for Xen domain 0 support.
| |
| | |
| [1] https://www.redhat.com/archives/fedora-xen/2008-September/msg00001.html
| |
| | |
| [2] http://lists.xensource.com/archives/html/xen-devel/2008-09/threads.html#00170
| |
| | |
| [3] http://fedoraproject.org/wiki/FWN/Issue137#State_of_Xen_in_Upstream_Linux
| |
| | |
| [[DanielBerrange|Daniel P. Berrange]] said[4] these patches will make their way into [[Releases/Rawhide | rawhide]] when they are merged into the LKML[5] dev tree line used by rawhide at that time.
| |
| | |
| [4] https://www.redhat.com/archives/fedora-xen/2008-September/msg00003.html
| |
| | |
| [5] http://lkml.org
| |
| | |
| === Libvirt List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
| | |
| ==== Libvirt 0.4.5 Released ====
| |
| [[DanielVeillard|Daniel Veillard]] announced[1] the release of libvirt 0.4.5. In addition to a long changelog, the "main features are the improvement of OpenVZ and LXC, the uniform XML handling (and hence format) th[r]ough all drivers, improvements in devices handling for QEmu/KVM and storage pool source discovery."
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00186.html
| |
| | |
| ==== Segfault if no Qemu Emulator Passed ====
| |
| [[ColeRobinson|Cole Robinson]] patched[1] a bug that resulted in a segfault if
| |
| a Qemu domain is defined without an emulator value. [[DanielBerrange|Daniel Berrange]] expressed[2] displeasure at letting this bug slip through and proposed a "brown paper bag" release. [[DanielVeillard|Daniel Veillard]] advised[3] against rushing the fix, and offered to push the patch to Fedora's build while other distributions could pick up the fix in a week or two when libvirt 0.4.6 would presumably be released.
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00199.html
| |
| | |
| [2] https://www.redhat.com/archives/libvir-list/2008-September/msg00202.html
| |
| | |
| [3] https://www.redhat.com/archives/libvir-list/2008-September/msg00206.html
| |
| | |
| Daniel Berrange pointed out code test coverage reports[4] on the build server, and highlighted the need to create a functional test rig for the mass of code that is simply not possible to unit test due to interactions with host OS state / functionality.
| |
| | |
| [4] http://builder.virt-manager.org/module-libvirt--devel.html
| |
| | |
| ==== Ability to Nice KVM Processes ====
| |
| [[HenriCook|Henri Cook]] expressed[1] a desire to nice KVM processes, and proposed a means to pass arbitrary command string parameters to the process startup.
| |
| | |
| As mentioned[2] in FWN #141, [[DanielBerrange|Daniel Berrange]] pointed out[3] the goal of libvirt is consistent API representation across hypervisors. Fortunately there is a 'schedular parameters' API in libvirt. All that's needed is for someone to implement the schedular parameters driver API for KVM.
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00209.html
| |
| | |
| [2] http://fedoraproject.org/wiki/FWN/Issue141#Exposing_Unique_Hypervisor_Features
| |
| | |
| [3] https://www.redhat.com/archives/libvir-list/2008-September/msg00210.html
| |
| | |
| ==== RFC Thoughts on Open Source Hypervisor Management ====
| |
| [[NathanCharles|Nathan Charles]] described[1] his ideal clustered VM provisioning system. Features would include
| |
| * cluster administration is done from the command line
| |
| * cluster administration can be performed from any node
| |
| * a new node can join a cluster on a local subnet with one command
| |
| * local storage resources are presented to the cluster so there is no need to have predefined NAS/SAN/iSCSI
| |
| * cluster will load balance vm instances from node to node
| |
| * a node shouldn't need more than one nic but adding additional nic's provides failover and load balancing
| |
| Nathan acknowledged oVirt's virtues, but stated it requires a lot of substantial changes and significant modification to work with an existing provisioning infrastructure. Nathan requested comments on his thoughts.
| |
|
| |
|
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00195.html | | Contributing Writer: [[User:Dale | Dale Bewley]] |
|
| |
|
| The only reply[2] so far came from [[StefanKonink|Stefan de Konink]], who pointed to some code[3] which seems[4] to be a "handler for libvirt using avahiclient".
| | === Fedora Virtualization List === |
| | This section contains the discussion happening on the |
| | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| [2] https://www.redhat.com/archives/libvir-list/2008-September/msg00196.html | | ==== Virt Status Report ==== |
| | [[JustinForbes|Justin Forbes]] |
| | posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report. |
| | Justin pointed out F13 bugs<ref>http://fedoraproject.org/wiki/Virtualization_bugs</ref> now include Important and Pony classifications in addition to Blocker and Target. |
|
| |
|
| [3] http://repo.or.cz/w/handlervirt.git
| | <references /> |
|
| |
|
| [4] http://kinkrsoftware.nl/projecten.html#virt
| | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| | compared to Fedora 12. |
|
| |
|
| === oVirt Devel List ===
| | [[DanielBerrange|Daniel Berrange]] |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
| | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| | "The KVM based virtualization in RHEL-5.4 is not nearly so far behind |
| | Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was |
| | rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is |
| | also pretty close to that using what's best described as a hybrid of |
| | kvm-83 and kvm-84." |
|
| |
|
| === Other Virtualization News ===
| | <references /> |
| This section contains virtualization news which may not have been directly discussed on the above mailing lists.
| |
|
| |
|
| ==== Red Hat Acquires Makers of KVM, Qumranet Inc. ====
| |
| Red Hat has acquired[1][2] Qumranet, Inc., the inventor and key maintainer of KVM.
| |
|
| |
|
| [1] http://www.redhat.com/about/news/prarchive/2008/qumranet.html
| | ==== ==== |
| | <references /> |
|
| |
|
| [2] http://www.redhat.com/promo/qumranet/
| | ==== ==== |
| | <references /> |
libvirt