FWN/Beats/Virtualization: Difference between revisions

Latest revision as of 18:09, 18 December 2009

Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @fedora-virt list.

Contributing Writer: Dale Bewley

Fedora Virtualization List

This section contains the discussion happening on the fedora-virt list.

Virt Status Report

Justin Forbes posted^[1] a Fedora virtualization status report. Justin pointed out F13 bugs^[2] now include Important and Pony classifications in addition to Blocker and Target.

↑ http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html
↑ http://fedoraproject.org/wiki/Virtualization_bugs

RHEL and Fedora Virtualization Feature Parity

Robert Day wondered how the virtualization features^[1] of Red Hat Enterprise Linux 5.4 compared to Fedora 12.

Daniel Berrange explained^[2] "The KVM based virtualization in RHEL-5.4 is not nearly so far behind Fedora as you might think. The libvirt mgmt stack in RHEL-5.4 was rebased to be near parity with 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."

↑ http://www.redhat.com/virtualization/rhev/
↑ http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html

@@ Line 1: / Line 1: @@
 [[Category:Virtualization]] <!-- do not copy into FWN issue -->
+{{Anchor|Virtualization}}
-{{Anchor|Virtualization}}
 == Virtualization ==
@@ Line 14: / Line 14: @@
 [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
-==== KVM and Paravirtualization ====
+==== Virt Status Report ====
-The Linux Kernel-based Virtual Machine is a form of hardware assisted
+[[JustinForbes|Justin Forbes]]
-virtualization<ref>http://en.wikipedia.org/wiki/Hardware-assisted_virtualization</ref>
+posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.
-as opposed to software-only or paravirtualization. This means the underlying
+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.
-hardware must have CPU features like Intel-VT or AMD-V. While common in the
-last few years, there are still many servers in operation which lack these extensions.
-[[GiovanniTirloni|Giovanni Tirloni]]
-asked<ref>http://www.redhat.com/archives/fedora-virt/2009-October/msg00090.html</ref>
-about the state of paravirtualization support in KVM, and
-asked about a set of KVM patches<ref>http://people.redhat.com/mingo/kvm-paravirt-patches/</ref>.
-[[DorLaor|Dor Laor]]
-answered<ref>http://www.redhat.com/archives/fedora-virt/2009-October/msg00092.html</ref>
-there is no plan to support non-VT hardware with KVM. While Xen is not
-supported on Fedora, it is still a paravirtualization for such hardware option under Redhat 5.
 <references />
-==== Installing Virtio Drivers in Windows XP Setup ====
+==== RHEL and Fedora Virtualization Feature Parity ====
-[[RichardHughes|Richard Hughes]]
+Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
-posted<ref>http://www.redhat.com/archives/fedora-virt/2009-October/msg00101.html</ref>
+compared to Fedora 12.
-the following directions for installing VirtIO drivers<ref>http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers</ref> during Windows XP setup.
-* create a 1.44Mb image file
-* mount it by loopback
-* format it with vfat
-* copy the {{filename|Install/Xp/x86/viostor.sys}}, {{filename|Install/Xp/x86/wnet.inf}}, and the txtsetup.oem file below to the root of the mounted image
-* umount the loop device
-* attach the floppy image as a floppy storage element in the VM's details pane
-* boot the VM
-* remember to press F6 when booting the windows xp setup and select the VirtoIO device.
-File {{filename|txtsetup.oem}}:
-<pre>
-[Disks]
-d1 = "Viostor SCSI driver disk",\disk1.tag,\
-[Defaults]
-SCSI = viostor
-[SCSI]
-viostor = "Viostor SCSI Controller"
-[Files.SCSI.viostor]
-driver = d1,viostor.sys,viostor
-inf = d1,wnet.inf
-[HardwareIds.scsi.viostor]
-id = "PCI\VEN_1AF4&DEV_1001","viostor"
-</pre>
-Richard added "I'm still unable to install XP using ide, scsi or virtio drivers
+[[DanielBerrange|Daniel Berrange]]
-as it gives the message "Setup was unable to format the partition. The
+explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
-disk maybe damaged." -- any ideas welcome."
+"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."
 <references />
-=== Other Sources ===
-==== Using Kernel Samepage Merging with KVM ====
-An upcoming feature  of [[Releases/12|Fedora 12]] is
-KSM<ref>http://fedoraproject.org/wiki/Features/KSM</ref>.
-"Kernel SamePage Merging is a recent linux kernel feature which combines
-identical memory pages from multiple processes into one copy on write memory
-region."
-[[HaydnSolomon|Haydn Solomon]] described<ref>http://www.linux-kvm.com/content/using-ksm-kernel-samepage-merging-kvm</ref> how KSM and KVM work together.
+====  ====
 <references />
-=== Virtualization Tools List ===
+====  ====
-This section contains the discussion happening on the
-[http://www.redhat.com/mailman/listinfo/virt-tools-list virt-tools-list list].
-==== libosinfo Revisited ====
-[[ArjunRoy|Arjun Roy]]
-revived<ref>http://www.redhat.com/archives/virt-tools-list/2009-October/msg00091.html</ref>
-discussion of a library to track details of OS distributions for use by tools
-such as {{package|python-virtinst}} and <code>virt-inspector</code>. LibOSinfo was first proposed<ref>http://fedoraproject.org/wiki/FWN/Issue180#libosinfo:_Library_for_Virt_OS.2Fdistro_Metadata</ref>
-by [[ColeRobinson|Cole Robinson]].
 <references />

Search