|
|
(171 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]] |
|
| |
|
| |
|
| |
|
| === Fedora Virtualization List === | | === Fedora Virtualization List === |
Line 14: |
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. |
| | | 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. |
| 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.
| |
| The package is currently being reviewed<ref>https://bugzilla.redhat.com/show_bug.cgi?id=495564</ref> for inclusion the Fedora repo.
| |
| | |
| "<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 /> |
|
| |
|
| | ==== 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. |
|
| |
|
| | | [[DanielBerrange|Daniel Berrange]] |
| ==== Only libvirt Bug Fixes in updates-testing ====
| | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| [[DanielBerrange|Daniel Berrange]] described | | "The KVM based virtualization in RHEL-5.4 is not nearly so far behind |
| "introducing major new features into the stable release stream" as a problem<ref>http://fedoraproject.org/wiki/FWN/Issue171#Virtualization_Technology_Preview_Repo</ref> and switch to "a pretty strong bugfix only policy..."
| | Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was |
| [[MarkMcLoughlin|Mark McLoughlin]]
| | rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is |
| announced<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00136.html</ref>
| | also pretty close to that using what's best described as a hybrid of |
| that this has now happened:
| | kvm-83 and kvm-84." |
| * {{package|libvirt}} 0.6.1 has been unpushed from F9 and F10 updates-testing
| |
| * The latest version available in F9 and F10 updates is 0.5.1
| |
| * We do not expect to push new versions to F9 and F10, only bug fix updates for 0.5.1
| |
| | |
| The rapid speed of Fedora releases every 6 months
| |
| can not keep up with the lightning fast <code>libvirt</code> releases happening every month<ref>http://fedoraproject.org/wiki/FWN/Issue169#More_Formal_libvirt_Release_Scheduling</ref>. To gain access to the new features and technologies offered by these new releases, Mark offers
| |
| "We are still planning on setting up a 'preview' repository where
| |
| the latest versions of virt packages from rawhide will be available
| |
| to Fedora stable release users".
| |
| | |
| In the meantime [[DanielVeillard|Daniel Veillard]]
| |
| posts<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00283.html</ref>
| |
| a src rpm with each release<ref>ftp://libvirt.org/libvirt/</ref> and | |
| "I also build binaries rpms for the flavour of the day I run on
| |
| my workstation which is why you will find signed binaries too for
| |
| F9 x86_64".
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== Fedora Virtualization Status Report ====
| |
| [[MarkMcLoughlin|Mark McLoughlin]]
| |
| provided<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00170.html</ref>
| |
| another excellent round up of the latest bugs and developments with
| |
| virtualization in Fedora.
| |
|
| |
|
| | ==== ==== |
| <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 />
| |
| | |
| === 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 />
| |
| | |
| ==== KVM Migration Support in F11 ====
| |
| Abhishek Jha
| |
| <ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00501.html</ref>
| |
| "needed to know if libvirt supports migration via the QEMU/KVM driver. (
| |
| virDomainMigrate)".
| |
| | |
| [[DanielBerrange|Daniel Berrange]]
| |
| answered<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00509.html</ref>
| |
| "Yes it is supported in <code>KVM</code> >= 79, or <code>QEMU</code> >= 0.10.0 and <code>libvirt</code> 0.6.0
| |
| IIRC." With the latest version of {{package|libvirt}} available for Fedora 10
| |
| being 0.5.1, this means migration of KVM guests will not be supported in Fedora until F11 comes out next month.<ref>http://fedoraproject.org/wiki/Releases/11/Schedule</ref>
| |
| | |
| "ALso note that successful migration depends on the hardware config of
| |
| your guest. In theory any config should work, but in practice there
| |
| have been bugs in the device state save/restore process of various
| |
| types of device. So test your particular VM config successfully
| |
| migrates before relying on it in production."
| |
| | |
| <references /> | | <references /> |