|
|
| (448 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 and Virtinst Closely Related ====
| |
| After upgrading <code>virt-manager</code> to 0.6.0, [[MaikelDollé|Maikel Dollé]] received[1] the error ''ImportError: cannot import name Storage''. [[ColeRobinson|Cole Robinson]] explained[2] <code>virt-manager</code> is tied closely with <code>virtinst</code> and installing <code>virtinst</code> 0.400.0 would likely fix the problem.
| |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00038.html
| |
| | |
| [2] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00039.html
| |
| | |
| ==== Migration Support in Virt-manager GUI ====
| |
| [[ShigekiSakamoto|Shigeki Sakamoto]] followed[1] up on a previous[2] request for comments on a patch, submitted by same, which works to allow the migration of domains from within the <code>virt-manager</code> GUI. [[DanielBerrange|Daniel P. Berrange]] suggested[3] using a submenu rather than a pop-up window, and commented on the sanity checks[4] in libvirt.
| |
| | |
| Live Migration Sanity Checks were recently discussed on <code>@libvir</code>
| |
| list (see FWN #141 ''Live Migration Sanity Checks''[5]).
| |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00045.html
| |
| | |
| [2] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00016.html
| |
| | |
| [3] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00046.html
| |
| | |
| [4] http://wiki.libvirt.org/page/TodoPreMigrationChecks
| |
| | |
| [5] http://fedoraproject.org/wiki/FWN/Issue141#Live_Migration_Sanity_Checks
| |
| | |
| === Fedora Xen List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
| |
| | |
| ==== DomU Network Interface Problem Leads to Discussion of HVM Requirements ====
| |
| Guillaume[1] asked[1] about a paravirtualized domU which did not show any network interfaces.
| |
| There was a suggestion made that this could be due to a lack of HVM support in the host hardware, which isn't the case. [[PaulWouters|Paul Wouters]] cleared[2] up such confusion by describing the main virtualization techniques used in Fedora. Quoting:
| |
| | |
| * Xen hypervisor for para_virt guests does not need HVM.
| |
| : Problem here is that Fedora 8 is the last release to support this setup on x86_64, though work is in progress to add this support to Fedora 9/10. Para_virt guests are booted via kernel= and rootfs images, or via pygrub, which is just a wrapper for grabbing kernel from bootable disk images.
| |
| | |
| * Qemu is a software emulator for various architectures including PC hardware.
| |
| : It requires no HVM instructions, but it can use them if they exist via the kernel "kvm" code. This is how Fedora9 does its VM's via the libvirt and virt-install. This does NOT [sic] use or require a xen hypervisor.
| |
| | |
| * Xenner is a software emulation for the Xen hypervisor.
| |
| : It requires HVM because it uses the kernel "kvm" code. The idea behind Xenner is that you can run VM's based on kernel-xen kernels (eg migration from Fedora8)
| |
|
| |
|
| Paul went on to mention other[5] virtualization technologies such as VirtualBox/Vmx, lguest, uml, virtuoso, and openvz.
| | Contributing Writer: [[User:Dale | Dale Bewley]] |
|
| |
|
| [1] https://www.redhat.com/archives/fedora-xen/2008-September/msg00018.html | | === 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/fedora-xen/2008-September/msg00021.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. |
|
| |
|
| In another post[3] Paul suggested that Guillaume's domU may have an initrd which lacks <code>xenblk</code> and <code>xennet</code>, and pointed[4] to a debate in the FC6 era concerning the <code>xenblk</code> kernel module.
| | <references /> |
|
| |
|
| [3] https://www.redhat.com/archives/fedora-xen/2008-September/msg00022.html
| | ==== 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. |
|
| |
|
| [4] https://www.redhat.com/archives/fedora-xen/2007-April/msg00054.html | | [[DanielBerrange|Daniel Berrange]] |
| | 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." |
|
| |
|
| [5] http://virt.kernelnewbies.org/TechComparison
| | <references /> |
|
| |
|
| === Libvirt List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
|
| |
|
| === oVirt Devel List === | | ==== ==== |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
| | <references /> |
|
| |
|
| === Other Virtualization News === | | ==== ==== |
| This section contains virtualization news which may not have been directly discussed on the above mailing lists.
| | <references /> |
libvirt