FWN/Beats/Virtualization: Difference between revisions

This has been covered in FWN, find ref
I am planning on running several virtual machines on a single host.  I
will have two or three Linux baeed virtual machines and one or two
Windoze.  I plan on using a F11 host system.

I need most of these to run automatically on boot-up of the host
system.  It would be really nice if I could use something like the
Ctl-Alt-FN to be able to access and switch between virtual machines.
This needs to be stable.  The machines that these virtual machines are
intended to replace are often running hundreds of days between
reboots.

My gut feel is that the virt-manager suite might be the way to go,
editting the apropriate xml files as required.  I also see there
is a qemu launcher and it seems to work okay.  I suspect there are
others as well.

What tends to be the consensus here on the various virtual machine
managers?  Are there white papers somewhere that could give some
insight?

For stability and long-term maintainability, I wonder if you've
considered using RHEL or CentOS?  That means you have to use Xen as
the hypervisor, but if you use libvirt / virsh / virt-manager, the
future upgrade path to KVM is reasonable.  All tools stay the same,
and you just need to run our forthcoming v2v tool on the guests (or
reinstall the guests) when you upgrade.

The only one we're supporting here on
Fedora<ref>http://fedoraproject.org/wiki/Virtualization</ref> is libvirt / virsh /
virt-manager.  Use 'virsh edit <domain>' to edit the XML for a domain.
The same commands will work on RHEL / CentOS too.

I suspect this is the result of trying to use SELinux to protect everything 
and the mandatory access control idea that everything is disallowed except 
that which is explicitly permitted.

But, I just do not understand what and why CD/DVD images and devices are being 
protected.  Furthermore, when virtualization changes a file's context 
(including /dev/sr0), could this effect other valid usage of these 
files/devices?  If there is no effect for other applications, then just what is 
protected?

@@ Line 119: / Line 119: @@
 === Fedora-Xen List ===
+This section contains the discussion happening on the
+[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
-==== Forward-ported Xen dom0 Kernel Patches ====
+==== Xen dom0 Forward Ported to Latest Kernel ====
-Previous dom0 support in Fedora was based on patches against 2.6.18 which were carried
+Previously, Xen dom0 support in Fedora was provided by forward porting the Xensource patches from kernel 2.6.18 to version found in the Fedora release at the time. This consumed resources and led to separate {{package|kernel}} and {{package|kernel-xen}} packages for a time. As of
-forward to the kernel version found in the Fedora release of the time. As of
+[[Releases/9|Fedora 9]]<ref>http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Virtualization.html</ref> this practice was deamed<ref>https://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html</ref> untenable, and support for hosting Xen guests was dropped from Fedora.
-Fedora 9 <ref>http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Virtualization.html</ref>
- this practice ceased and work began on creating a pv_ops-based kernel<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> cabable
-of functioning as a dom0, and based on the most recent kernel.
-This work is incomplete and not expected to be until F12 or F13, but
+Work has since focused on creating a paravirt operations dom0<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> kernel based on the most recent upstream vanilla kernel. This work is incomplete and not expected to be done before F12 or even F13. However, experimental dom0 kernels<ref>http://fedoraproject.org/wiki/FWN/Issue170#Experimental_Dom0_Kernel_Update</ref> have been created for the adventurous.
-there have been experimental kernels built (add link to previous dom0 news).
 [[PasiKärkkäinen|Pasi Kärkkäinen]]
 tells<ref>http://www.redhat.com/archives/fedora-xen/2009-July/msg00000.html</ref> us
-<pre>
+the Xen 2.6.18 patches have now been forward-ported to the current 2.6.29 and
-For reference here are the latest Xenlinux 2.6.18 forward-ported patches to
+.6.30 kernel. "Forward-porting has been done by Novell for OpenSUSE. Novell also has a forward-port to 2.6.27 for SLES11."
-standard/kernel.org Linux 2.6.29 and 2.6.30. Forward-porting has been
-done by Novell for OpenSUSE. Novell also has a forward-port to 2.6.27 for SLES11.
-See this thread for the latest patches:
+The patches can be found
-http://www.nabble.com/2.6.30-dom0-Xen-patches-td24293721.html
+here<ref>http://www.nabble.com/2.6.30-dom0-Xen-patches-td24293721.html</ref>
+here <ref>http://code.google.com/p/gentoo-xen-kernel/downloads/list</ref>
+and here<ref>http://x17.eu/xen/</ref>.
-Patches for 2.6.29 and 2.6.30 available here:
+Pasi added "These patches are still more stable and mature than the
-http://code.google.com/p/gentoo-xen-kernel/downloads/list
+pv_ops dom0 code.. Also, these patches have the full Xen feature set
+(pv_ops still lacks some features)."
-Also available here:
+More history is avilable<ref>http://fedoraproject.org/wiki/Virtualization/History</ref>.
-http://x17.eu/xen/
-Someone interested in building Xen dom0 capable kernel for F11, based on
-these patches? These patches are still more stable and mature than the
-pv_ops dom0 code.. Also, these patches have the full Xen feature set
-(pv_ops still lacks some features).
-If you have any problems with these patches, please post to xen-devel mailinglist.
-</pre>
 <references />

Search

FWN/Beats/Virtualization: Difference between revisions

Revision as of 03:49, 10 July 2009

Contents

Virtualization

Enterprise Management Tools List

Fedora Virtualization List

New list for libguestfs

Fedora Virt Status Update

USB Passthrough to Virtual Machines

best Fedora virtualization

Libvirt List

Fedora-Xen List

Xen dom0 Forward Ported to Latest Kernel