(start on issue 144) |
(→Fedora Xen List: DomU Network Interface Problem Leads to Discussion of HVM Requirements) |
||
| Line 11: | 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 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. | |||
[1] https://www.redhat.com/archives/fedora-xen/2008-September/msg00018.html | |||
[2] https://www.redhat.com/archives/fedora-xen/2008-September/msg00021.html | |||
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. | |||
[3] https://www.redhat.com/archives/fedora-xen/2008-September/msg00022.html | |||
[4] https://www.redhat.com/archives/fedora-xen/2007-April/msg00054.html | |||
[5] http://virt.kernelnewbies.org/TechComparison | |||
=== Libvirt List === | === Libvirt List === | ||
Revision as of 00:55, 22 September 2008
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
Fedora Xen List
This section contains the discussion happening on the 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. 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.
[1] https://www.redhat.com/archives/fedora-xen/2008-September/msg00018.html
[2] https://www.redhat.com/archives/fedora-xen/2008-September/msg00021.html
In another post[3] Paul suggested that Guillaume's domU may have an initrd which lacks xenblk and xennet, and pointed[4] to a debate in the FC6 era concerning the xenblk kernel module.
[3] https://www.redhat.com/archives/fedora-xen/2008-September/msg00022.html
[4] https://www.redhat.com/archives/fedora-xen/2007-April/msg00054.html
[5] http://virt.kernelnewbies.org/TechComparison
Libvirt List
This section contains the discussion happening on the libvir-list.
oVirt Devel List
This section contains the discussion happening on the ovirt-devel list.
Other Virtualization News
This section contains virtualization news which may not have been directly discussed on the above mailing lists.