|
|
| (90 intermediate revisions by 2 users not shown) |
| Line 2: |
Line 2: |
|
| |
|
| {{Anchor|Virtualization}} | | {{Anchor|Virtualization}} |
| | |
|
| |
|
| == Virtualization == | | == Virtualization == |
| In this section, we cover discussion of Fedora virtualization technologies on the | | In this section, we cover discussion of Fedora virtualization technologies on the |
| @et-mgmnt-tools-list, @fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list,
| | @fedora-virt list. |
| @virt-tools-list, and @ovirt-devel-list lists.
| |
|
| |
|
| 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]
| |
|
| |
| ==== Good Bye to ET-Mgmt-Tools List ====
| |
| [[DanielBerrange|Daniel Berrange]]
| |
| announced<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00046.html</ref> the end of life for the et-mgmt-tools list and the birth of the @virt-tools-list. "In retrospect this was a really bad choice of names for a mailing list
| |
| and causes endless confusion for people wrt what to discuss where. Most
| |
| of the emerging technology projects have lists of their own
| |
| ({{package|cobbler}}<ref>http://fedorahosted.org/mailman/listinfo/cobbler</ref><ref>http://fedorahosted.org/mailman/listinfo/cobbler-devel</ref>,
| |
| {{package|augeas}}<ref>http://www.redhat.com/mailman/listinfo/augeas-devel</ref>,
| |
| {{package|libguestfs}}<ref>http://www.redhat.com/mailman/listinfo/libguestfs</ref>,
| |
| {{package|libvirt}}<ref>http://www.redhat.com/mailman/listinfo/libvir-list</ref>)
| |
| and it is about time that {{package|virt-manager}} and friends joined them."
| |
|
| |
| "To that end we have created a new mailing list 'virt-tools-list'<ref>http://www.redhat.com/mailman/listinfo/virt-tools-list</ref>. This
| |
| will be the new home for all developer & user discussions relating to
| |
| the following applications:"
| |
| * virt-manager
| |
| * virt-viewer
| |
| * virt-install
| |
| * virt-clone
| |
| * virt-image
| |
| * virt-convert
| |
|
| |
| <references />
| |
|
| |
|
| === Fedora Virtualization List === | | === Fedora Virtualization List === |
| Line 41: |
Line 14: |
| [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. | | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| ==== Virtual Machine Disk Setup Tips ==== | | ==== Virt Status Report ==== |
| [[RichMahn|Rich Mahn]] | | [[JustinForbes|Justin Forbes]] |
| recognized<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00141.html</ref>
| | posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report. |
| "that the best
| | 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. |
| performance for virtual disks is with the backing storage on the host
| |
| being a parititon or LV. Since I want some flexibility I will use
| |
| LVs, with virtio disks on most of the VMs." But Rich
| |
| had
| |
| several questions (paraphrased below) about how best to configure the backing stores for virtual machines and the disks within them.
| |
| [[DanielBerrange|Daniel Berrange]] provided some answers (also paraphrased
| |
| below).
| |
| | |
| * '''Q:''' If each VM needs three file systems: {{filename|/boot}}, {{filename|root}}, and {{filename|swap}}. "Is it better to create three LVs (each) on the hosts, and treat it as three separate disks on the VMs?"
| |
| : '''A:''' "There's no point separating /boot & root onto separate virtual disks." "The only separation I'd do is for the OS system disks, vs application data disks..." This makes it easier to provision a new VM with the latest disto and reassign the data disk to the new guest.
| |
| | |
| * '''Q:''' "Do I get better performance/stability by NOT using lvm on the VMs?"
| |
| : '''A:''' "LVM makes is easier to resize guest FS. eg add a second disk to the guest, format it as a LVM PV and add it to your VG. That's pretty much only wayto add more capacity on a running guest."
| |
| | |
| * '''Q:''' "Do I get the best performance/stability by creating an LV for each disk I need, and then NOT partitioning it on the VM, but using the whole disk for a file system?"
| |
| : '''A:''' "Anaconda will refuse to install onto a raw disk, it mandates partitioning. Second point is that not using a partition table can cause unexpected problems..."
| |
| | |
| * '''Q:''' "Are these issues too miniscule in their effects that I probably shouldn't even be worrying about" trying to avoid using partitions and LVM?
| |
| : '''A:''' "That's certainly my opinion. Sure you get some performance but you loose the great administrative flexibility of LVM."
| |
|
| |
|
| <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]] |
| === Libguestfs List ===
| | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| This section contains the discussion happening on the
| | "The KVM based virtualization in RHEL-5.4 is not nearly so far behind |
| [http://www.redhat.com/mailman/listinfo/libguestfs libguestfs list].
| | 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 |
| ==== New Release libguestfs 1.0.59 ====
| | also pretty close to that using what's best described as a hybrid of |
| [[RichardJones|Richard Jones]] | | kvm-83 and kvm-84." |
| announced<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00023.html</ref>
| |
| the release of {{package|libguestfs}} 1.0.59.
| |
| | |
| '''New Features:'''
| |
| * Support for Linux extended attributes.
| |
| * Allow guestfish to be controlled remotely, so you can use one guestfish instance in a long-running shell script.
| |
| * Support for reiserfs.
| |
| * New function 'guestfs_zfile' -- 'file' inside compressed files.
| |
| * New guestfish command 'reopen' -- reopen guestfish connection.
| |
| * guestfish -x option (echo commands).
| |
| * New function 'guestfs_version' to get the library version.
| |
| | |
| See previous release announcement for 1.0.57 in
| |
| FWN#184<ref>http://fedoraproject.org/wiki/FWN/Issue184#New_Mailing_List_and_New_Releases_of_libguestfs</ref>
| |
| and be sure to see the project homepage<ref>http://libguestfs.org/</ref> for
| |
| extensive usage examples.
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== New Hypervisor Migration Tool virt-v2v ====
| |
| [[MatthewBooth|Matthew Booth]]
| |
| posted<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00024.html</ref>
| |
| his "initial thoughts on the design for the v2v tool". This tool will be used
| |
| to implement the planned Fedora 12 feature "Xen to KVM Migration"<ref>http://fedoraproject.org/wiki/Features/Xen_to_KVM_migration</ref>.
| |
|
| |
|
| | ==== ==== |
| <references /> | | <references /> |
|
| |
|
| | | ==== ==== |
| | |
| === Libvirt List === | |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
| | |
| ==== Split RPC Dispatching from Remote API Handlers ====
| |
| [[DanielBerrange|Daniel Berrange]]
| |
| posted<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00303.html</ref>
| |
| a set of 9 patches.
| |
| "The current <code>libvirtd</code> remote protocol dispatch code is written in
| |
| such a way that assumes the only incoming messages from clients
| |
| are method calls. This makes it very hard to support data streams.
| |
| This patch series does an incrmental refactoring of alot of code
| |
| to allow data streams to be easily wired in."
| |
| | |
| <references />
| |
| | |
| ==== Allow QEMU VMs to be Run Unprivileged ====
| |
| [[DanielBerrange|Daniel Berrange]]
| |
| submitted<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00390.html</ref> a patch which
| |
| "makes it such that the" privileged "<code>libvirtd</code> daemon can
| |
| run unprivileged QEMU guests. The default remains unchanged with
| |
| QEMU running as root:root, but the package maintainer can request
| |
| an alternative default user at build time, and the sysadmin can
| |
| also override this at install time with {{filename|/etc/libvirt/qemu.conf}}."
| |
| | |
| This patch is in support of the planned [[releases/12 | Fedora 12]] feature "VirtPrivileges"<ref>http://fedoraproject.org/wiki/Features/VirtPrivileges</ref>.
| |
| | |
| <references />
| |
| | |
| ==== cgroups Support in QEMU Driver ====
| |
| [[DanielBerrange|Daniel Berrange]]
| |
| added<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00435.html</ref>
| |
| "cgroups<ref>http://www.mjmwired.net/kernel/Documentation/cgroups.txt</ref> support to the QEMU driver."
| |
| | |
| <references />
| |
| | |
| ==== Experimental Tunnelled Migration ====
| |
| [[ChrisLalancette|Chris Lalancette]]
| |
| posted<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00433.html</ref>
| |
| "the current version of the tunnelled migration patch, based
| |
| upon [[DanielBerrange|Daniel Berrange]]'s generic datastream work. In order to use this work, you must first
| |
| grab danpb's data-streams git branch<ref>http://gitorious.org/~berrange/libvirt/staging</ref>". Chris's work on secure guest migration was covered in
| |
| FWN #168<ref>http://fedoraproject.org/wiki/FWN/Issue168#Secure_Guest_Migration_Draft_Patch</ref>.
| |
| | |
| <references /> | | <references /> |
libvirt