|
|
| (17 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 |
| @fedora-virt, @fedora-xen-list, and @libvirt-list lists. | | @fedora-virt list. |
|
| |
|
| Contributing Writer: [[User:Dale | Dale Bewley]] | | Contributing Writer: [[User:Dale | Dale Bewley]] |
| Line 13: |
Line 14: |
| [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. | | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| ==== Guest Bridge Configuration with libvirt and netcf ==== | | ==== Virt Status Report ==== |
| [[AndrésGarcía|Andrés García]] | | [[JustinForbes|Justin Forbes]] |
| thought<ref>http://www.redhat.com/archives/fedora-virt/2009-November/msg00002.html</ref> he read somewhere that with [[Releases/12|Fedora 12]] there was going to be a way to configure virtual network bridges automagically", but was only aware of the manual<ref>http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared_physical_device.22.29</ref> means of configuration.
| | 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. |
| It is possible in to configure bridges using <code>virsh</code> thanks to the Network Interface Management<ref>http://fedoraproject.org/wiki/Features/Network_Interface_Management</ref> feature and {{package|netcf}}<ref>http://linux-kvm.com/content/netcf-silver-bullet-network-configuration</ref>. However, the process is manual and not in the GUI. [[DaleBewley|Dale Bewley]] blogged<ref>http://tofu.org/drupal/node/86</ref> about how to manually create a bridge in Fedora 12 using <code>virsh</code>.
| |
| | |
| Support for {{package|virt-manager}} integration is targeted<ref>http://fedoraproject.org/wiki/Features/Shared_Network_Interface</ref> for Fedora 13.
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== New Release libguestfs 1.0.78 ==== | | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| [[RichardJones|Richard Jones]] announced<ref>http://www.redhat.com/archives/virt-tools-list/2009-November/msg00023.html</ref>
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| version 1.0.78 of {{package|libguestfs}}<ref>http://libguestfs.org/</ref>, the library for accessing and modifying virtual machine filesystems.
| | compared to Fedora 12. |
|
| |
|
| '''New Features:'''
| | [[DanielBerrange|Daniel Berrange]] |
| * FUSE support so you can mount guest filesystems in the host <ref>http://rwmj.wordpress.com/2009/11/03/browsing-guests-using-fuse/</ref>
| | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| * Support for btrfs, gfs, gfs2, hfs, hfs+, nilfs2, jfs, reiserfs, xfs<ref>http://rwmj.wordpress.com/2009/11/08/filesystem-metadata-overhead/</ref>
| | "The KVM based virtualization in RHEL-5.4 is not nearly so far behind |
| * Support for huge (multi-exabyte) sparse virtual disks<ref>http://rwmj.wordpress.com/2009/11/04/petabytes-exabytes-why-not/</ref>
| | Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was |
| * New partitioning API, supports GPT and more<ref>http://libguestfs.org/guestfs.3.html#guestfs_part_add</ref>
| | rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is |
| * New tools:
| | also pretty close to that using what's best described as a hybrid of |
| :* <code>virt-ls</code><ref>http://rwmj.wordpress.com/2009/10/19/new-tool-virt-ls/</ref>
| | kvm-83 and kvm-84." |
| :* <code>virt-tar</code><ref>http://rwmj.wordpress.com/2009/10/19/new-tool-virt-tar/</ref>
| |
| :* <code>virt-edit</code><ref>http://rwmj.wordpress.com/2009/09/23/virt-edit/</ref>
| |
| :* <code>virt-rescue</code><ref>http://rwmj.wordpress.com/2009/09/22/virt-rescue/</ref>
| |
| * Windows Registry support, tools and library<ref>http://rwmj.wordpress.com/2009/10/29/virt-win-reg-get-at-the-windows-registry-in-your-windows-guests/</ref> <ref>http://rwmj.wordpress.com/2009/10/28/libhivex-windows-registry-hive-extractor-library/</ref>
| |
| * OCaml bindings for <code>virt-inspector</code>
| |
| * RELAX NG schema for <code>virt-inspector</code>
| |
| * New APIs: <code>utimens</code>, <code>vfs_type</code>, <code>truncate</code>, <code>truncate_size</code>, <code>lchown</code>, <code>lstatlist</code>, <code>lxattrlist</code>, <code>readlinklist</code>, <code>case_sensitive_path</code>, <code>find0</code>, <code>mkfs_b</code>, <code>mke2journal</code>, <code>and more ...
| |
| * New program: OCaml viewer<ref>http://rwmj.wordpress.com/2009/09/29/graphical-virt-df/</ref>
| |
| * Allow stdout to be redirected when running guestfish remotely (Matt Booth).
| |
| * Remove requirement for vmchannel support in qemu (horray!) and the tricky main loop code.
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| === Fedora Xen List ===
| |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
| |
|
| |
| ==== No Xen dom0 in Fedora 12 Hopefully 13 ====
| |
| [[ZhangEnming|Zhang Enming]]
| |
| was disappointed<ref>http://www.redhat.com/archives/fedora-xen/2009-November/msg00019.html</ref> to learn<ref>http://fedoraproject.org/wiki/Docs/Beats/Virtualization</ref> the pv_ops dom0 support<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> for hosting Xen guests, dropped in Fedora 9, is still not present in Fedora 12.
| |
| Zhang referenced numerous videos documenting success in creating "a fully working Xen pv-ops dom0 Fedora 11 host operating system."
| |
|
| |
| While there are experimental patches which may be applied<ref>http://fedoraproject.org/wiki/FWN/Issue190#Dom0_Kernel_Status</ref> <ref>http://wiki.xensource.com/xenwiki/XenParavirtOps</ref> to the kernel to enable support for dom0, they are not yet in the upstream kernel which forms the basis the Fedora kernel package.
| |
|
| |
| It was decided<ref>http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html</ref> two years ago this month that
| |
| Fedora "simply cannot spend more time forward porting Xen kernels" and
| |
| "the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops."
| |
| See FWN#137.<ref>http://fedoraproject.org/wiki/FWN/Issue137#kernel-xen_is_Dead</ref>
| |
|
| |
| [[PasiKärkkäinen|Pasi Kärkkäinen]]
| |
| noted<ref>http://www.redhat.com/archives/fedora-xen/2009-November/msg00020.html</ref>
| |
| "pv_ops dom0 kernel has only recently started working for many/most
| |
| people, so it was too late for F12 release" and
| |
| "There are still some missing features, most notably missing blktap2 support
| |
| for tap:aio: file-based images."
| |
|
| |
|
| | ==== ==== |
| <references /> | | <references /> |
|
| |
|
| === Libvirt List === | | ==== ==== |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
| | |
| ==== Keeping Guest Configurations in Sync on Multiple Hosts ====
| |
| [[ThomasTreutner|Thomas Treutner]]
| |
| asked<ref>http://www.redhat.com/archives/libvir-list/2009-November/msg00495.html</ref> "is there any best-practice how to keep VM definitions in sync across a couple of hosts? Is it reasonable to put {{filename|/etc/libvirt/qemu/}} on a NFS share?"
| |
| | |
| [[MatthiasBolte|Matthias Bolte]]
| |
| explained<ref>http://www.redhat.com/archives/libvir-list/2009-November/msg00498.html</ref> "No, it's not safe to share {{filename|/etc/libvirt/qemu/}}", but also didn't find it necessary to keep the configs in sync.
| |
| "A migrated domain stays defined on the source node and is transient on
| |
| the destination node. A transient domain has no persistent config on
| |
| its node and is lost when destroyed."
| |
| | |
| Matthias mentioned a patch<ref>http://www.redhat.com/archives/libvir-list/2009-October/msg00318.html</ref> to the <code>virDomainMigrate</code><ref>http://www.libvirt.org/html/libvirt-libvirt.html#virDomainMigrate</ref> function by [[ChrisLalancette|Chris Lalancette]] which will be in {{package|libvirt}} 0.7.3.
| |
| The patch adds a new flag which will allow domains to be migrated persistently. Version 0.7.3 is targeted<ref>http://www.redhat.com/archives/libvir-list/2009-November/msg00480.html</ref>
| |
| for release on November 20th.
| |
| | |
| <references /> | | <references /> |
libvirt