From Fedora Project Wiki

< FWN‎ | Beats

 
(178 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
{{Anchor|Virtualization}}
 
{{Anchor|Virtualization}}
 +
  
 
== Virtualization ==
 
== Virtualization ==
In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, and @libvirt-list of Fedora virtualization technologies.  
+
In this section, we cover discussion of Fedora virtualization technologies on the
 +
@fedora-virt list.
  
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
=== Enterprise Management Tools List ===
 
 
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
 
 
==== ====
 
<references />
 
  
 
=== Fedora Virtualization List ===
 
=== Fedora Virtualization List ===
Line 20: Line 14:
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
  
==== New Release libguestfs 1.0.10 ====
+
==== Virt Status Report ====
[[RichardJones|Richard Jones]]
+
[[JustinForbes|Justin Forbes]]
announced<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00220.html</ref> release 1.0.10 of {{package|libguestfs}}<ref>http://et.redhat.com/~rjones/libguestfs/</ref>
+
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.  
Born only a couple of weeks ago(FWN#171<ref>http://fedoraproject.org/wiki/FWN/Issue171#Guest_Configuration_with_augeas_and_libguestfs</ref>), <code>libguestfs</code> has progressed very far very fast.
+
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.
 
 
"<code>libguestfs</code> is a library for accessing and modifying guest disk images. Amongst the things this is good for: making batch configuration changes to guests, getting disk used/free statistics (see also: {{package|virt-df}}), migrating between virtualization systems (see also: virt-p2v), performing partial backups, performing partial guest clones, cloning guests and changing registry/UUID/hostname info, and much else besides."
 
 
 
'''Features in 1.0.10 include:'''
 
* bindings for: C, C++, Perl, Python, OCaml, Ruby, Java and shell scripting
 
* KVM support
 
* QEMU binary is completely configurable at compile & runtime
 
* ext4 support
 
* support for uploading and downloading arbitrary-sized files
 
* support for uploading and downloading tar and tar.gz content
 
* support for querying size of block devices, setting r/o
 
* support for reading ext2/3 superblocks
 
* stat, lstat, statvfs commands
 
* commands to mount filesystems read-only
 
* run arbitrary commands from the guest
 
* file(1) command
 
* readline in guestfish with history and tab completion
 
* guestfish 'edit' command
 
* big documentation improvements, including more on the internals
 
* pkgconfig file
 
 
 
Richard posted some example uses<ref>http://et.redhat.com/~rjones/libguestfs/recipes.html</ref>
 
of the <code>libguestfs</code> command line tool called <code>guestfish</code>.
 
  
 
<references />
 
<references />
  
==== Non-root User Image Locations ====
+
==== RHEL and Fedora Virtualization Feature Parity ====
[[RobertDay|Robert Day]]
+
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
asked<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00195.html</ref>
+
compared to Fedora 12.
"by default, new VM images are created in
 
{{filename|/var/lib/libvirt/images}}, and that directory is not accessible to
 
non-root users."
 
 
 
[[DanielBerrange|Daniel Berrange]]
 
<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00198.html</ref>
 
<pre>
 
There are two classes of libvirt driver connection
 
  
- Privileged, per-host connections
+
[[DanielBerrange|Daniel Berrange]]
- Unprivileged, per-user connections
+
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
Xen provides a per-host connection. UserModeLinux and QEMU provide
+
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
both (qemu:///system and qemu:///session). VirtualBox just proivides
+
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
a per-user instance (vbox:///session) and so on.
+
also pretty close to that using what's best described as a hybrid of
 
+
kvm-83 and kvm-84."
Now by default in Fedora, when connecting to QEMU, virt-manager will
 
use the privileged per-host connection, so VMs end up in the system
 
directory /var/lib/libvirt/images.
 
 
 
Our goal (perhaps for F12) should be for local desktop virt use
 
cases to use the unprivileged  QEMU connection qemu://session
 
by default, and have VM disk images stored in your home directory
 
</pre>
 
<pre>
 
> How would we allow KVM access? Unix groups or something else?
 
 
 
Two options
 
 
 
- A UNIX group for /dev/kvm
 
- Just make it world writable
 
 
 
 
 
In theory now KVM no longer pins all guest RAM into host RAM, it is
 
reasonable safe to allow users to access it without any restrictions.
 
(eg option 2) Will need to confirm with KVM developers if this is
 
really so, but that was the intention last time i asked them.
 
</pre>
 
<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00239.html</ref>
 
<pre>
 
Historically SELinux has wanted images in particular locations. With
 
the introduction of SVirt in libvirt, we have much more advanced
 
SELinux integration and will in fact automatically re-label images
 
to match the needs of a VM. So allowing arbitary locations *and*
 
still being in compliance with SELinux policy is now practical
 
</pre>
 
  
 
<references />
 
<references />
  
=== Fedora Xen List ===
 
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
 
==== Dom0 Kernel Not Before 2.6.31 ====
 
The upstream Xen dom0 work done by Jeremy Fitzhardinge has been cleaned up and
 
reorganized<ref>http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00955.html</ref>
 
into
 
* [http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/master xen-tip/master] - Known-working branch, with only tested changes
 
* [http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/next xen-tip/next] - Current bleeding edge; should at least compile
 
 
[[MichaelYoung|Michael Young]]
 
built<ref>http://www.redhat.com/archives/fedora-xen/2009-April/msg00012.html</ref>
 
a new experimental dom0 kernel "version (2.6.30-0.1.2.21.rc3.xendom0.fc12) is based on the Fedora devel kernel branch and xen-tip/next branch from the pvops kernel repository."
 
This kernel may be found in Michael's yum repo<ref>http://fedorapeople.org/~myoung/dom0/</ref>.
 
 
Michael added that "very few xen patches made it into 2.6.30, just bugfixes and tidy ups, so we are waiting at least until 2.6.31<ref>http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00961.html</ref> for mainline dom0 support."
 
  
 +
====  ====
 
<references />
 
<references />
  
=== Libvirt List ===
+
==== ====
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
 
 
==== New Release libvirt 0.6.3 ====
 
[[DanielVeillard|Daniel Veillard]]
 
announced<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00504.html</ref>
 
a new {{package|libvirt}} release, version 0.6.3. 
 
 
 
"The main points are the VirtualBox driver and a number of bug fixes."
 
Read the post for details of other changes.
 
 
 
'''New features:'''
 
* VirtualBox driver support (Pritesh Kothari)
 
* virt-xml-validate new command (Daniel Berrange)
 
'''Improvements:'''
 
* add SCSI storage rescan (David Allan)
 
* rootless LXC containers support improvements (Serge Hallyn)
 
* getHostname support for LXC (Dan Smith)
 
* cleanup and logging output of some domain functions (Guido Gunther)
 
* drop pool lock when allocating volumes (Cole Robinson)
 
* LXC handle kernel without CLONE_NEWUSER support (Serge Hallyn)
 
* cpu pinning on defined Xen domains (Takahashi Tomohiro)
 
* dynamic bridge names support (Soren Hansen)
 
* LXC use of private /dev/pts when available (Daniel Berrange)
 
* virNodeDeviceCreateXML and virNodeDeviceDestroy entry points (Dave Allan)
 
 
 
[[DanielVeillard|Daniel Veillard]]
 
followed the announcement with a roadmap
 
<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00508.html</ref>
 
suggesting "a new release around May 25, which would mean entering code
 
feature freeze around May 18". 
 
Version 0.6.2 was released April 3rd (FWN#170<ref>http://fedoraproject.org/wiki/FWN/Issue170#New_Release_libvirt_0.6.2</ref>).
 
 
 
 
<references />
 
<references />

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.

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 Package-x-generic-16.pnglibvirt 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."