FWN/Beats/Virtualization: Difference between revisions

  $> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
  [rawvirt]
  name=Virtualization Rawhide for Fedora 12
  baseurl=http://jforbes.fedorapeople.org/virt-preview/f12/$basearch/
  enabled=1
  gpgcheck=0
  EOF
  $> yum update

@@ Line 2: / Line 2: @@
 {{Anchor|Virtualization}}
 == Virtualization ==
 In this section, we cover discussion of Fedora virtualization technologies on the
-@fedora-virt, @fedora-xen-list, and @libvirt-list lists.
+@fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list,
+@virt-tools-list, and @ovirt-devel-list lists.
 Contributing Writer: [[User:Dale | Dale Bewley]]
@@ Line 13: / Line 15: @@
 [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
-==== Guest Bridge Configuration with libvirt and netcf ====
+==== Fedora Virtualization Status ====
-[[AndrésGarcía|Andrés García]]
+[[MarkMcLoughlin|Mark McLoughlin]]
-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.
+<ref>http://www.redhat.com/archives/fedora-virt/2009-November/msg00045.html</ref>
-It is possible in to configure bridges using {{command|virsh}} 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 {{command|virsh}}.
+<references />
-Support for {{package|virt-manager}} integration is targeted<ref>http://fedoraproject.org/wiki/Features/Shared_Network_Interface</ref> for Fedora 13.
+==== Rawvirt Rawhide Virtualization for Fedora 12 ====
+[[JustinForbes|Justin Forbes]]
+announced<ref>http://www.redhat.com/archives/fedora-virt/2009-November/msg00041.html</ref>
+"As was done for Fedora 11 users, the tradition continues, only the
+locations have changed.
-<references />
+We've set up a repository for people running Fedora 12 who would like
+to test the rawhide/F13 virt packages. To use it, do e.g."
-==== New Release libguestfs 1.0.78 ====
+<pre>
-[[RichardJones|Richard Jones]] announced<ref>http://www.redhat.com/archives/virt-tools-list/2009-November/msg00023.html</ref>
+  $> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
-version 1.0.78 of {{package|libguestfs}}<ref>http://libguestfs.org/</ref>, the library for accessing and modifying virtual machine filesystems.
+  [rawvirt]
+  name=Virtualization Rawhide for Fedora 12
+  baseurl=http://jforbes.fedorapeople.org/virt-preview/f12/$basearch/
+  enabled=1
+  gpgcheck=0
+  EOF
+  $> yum update
+</pre>
-'''New Features:'''
+The Virtualization Preview Repository<ref>http://fedoraproject.org/wiki/Virtualization_Preview_Repository</ref>
-* FUSE support so you can mount guest filesystems in the host <ref>http://rwmj.wordpress.com/2009/11/03/browsing-guests-using-fuse/</ref>
+is for people who would like to test the very latest virtualization related packages. This repository is intended primarily as an aid to testing / early experimentation. It is not intended for 'production' deployment.
-* Support for btrfs, gfs, gfs2, hfs, hfs+, nilfs2, jfs, reiserfs, xfs<ref>http://rwmj.wordpress.com/2009/11/08/filesystem-metadata-overhead/</ref>
-* Support for huge (multi-exabyte) sparse virtual disks<ref>http://rwmj.wordpress.com/2009/11/04/petabytes-exabytes-why-not/</ref>
-* New partitioning API, supports GPT and more<ref>http://libguestfs.org/guestfs.3.html#guestfs_part_add</ref>
-* New tools:
-:* <code>virt-ls</code><ref>http://rwmj.wordpress.com/2009/10/19/new-tool-virt-ls/</ref>
-:* <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 />
@@ Line 51: / Line 50: @@
 [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
-==== No Xen dom0 in Fedora 12 Hopefully 13 ====
+====  ====
-[[ZhangEnming|Zhang Enming]]
+<references />
-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.
+=== Virtualization Tools List ===
+This section contains the discussion happening on the
+[http://www.redhat.com/mailman/listinfo/virt-tools-list virt-tools-list list].
-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
+<references />
-"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]]
+=== Libguestfs List ===
-noted<ref>http://www.redhat.com/archives/fedora-xen/2009-November/msg00020.html</ref>
+This section contains the discussion happening on the
-"pv_ops dom0 kernel has only recently started working for many/most
+[http://www.redhat.com/mailman/listinfo/libguestfs libguestfs list].
-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 />
@@ Line 76: / Line 71: @@
 [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
-==== Keeping Guest Configurations in Sync on Multiple Hosts ====
+====  ====
-[[ThomasTreutner|Thomas Treutner]]
+<references />
-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]]
+=== oVirt Devel List ===
-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.
+This section contains the discussion happening on the
-"A migrated domain stays defined on the source node and is transient on
+[http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
-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 />

Search

FWN/Beats/Virtualization: Difference between revisions

Revision as of 17:41, 22 November 2009

Contents

Virtualization

Fedora Virtualization List

Fedora Virtualization Status

Rawvirt Rawhide Virtualization for Fedora 12

Fedora Xen List

Virtualization Tools List

Libguestfs List

Libvirt List

oVirt Devel List