|
|
| (119 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 @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list lists. | | 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 19: |
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 list for libguestfs ==== | | ==== Virt Status Report ==== |
| [[RichardJones|Richard Jones]] | | [[JustinForbes|Justin Forbes]] |
| announced<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00107.html</ref>
| | posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report. |
| the creation of a new list<ref>http://www.redhat.com/mailman/listinfo/libguestfs</ref> dedicated to
| | 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. |
| "{{package|libguestfs}}/<code>guestfish</code>/<code>virt-inspector</code> discussion/development".
| |
| | |
| <references />
| |
| | |
| ==== Fedora Virt Status Update ====
| |
| [[MarkMcLoughlin|Mark McLoughlin]]
| |
| posted<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00083.html</ref>
| |
| another Fedora Virt Status Update reminding that [[releases/12|Fedora 12]] is
| |
| quickly approaching with the Feature Freeze on 2009-07-28.
| |
| | |
| Also mentioned were:
| |
| * Details of a fix for "a dramatic slowdown in virtio-blk performance in F-11 guests"<ref>https://bugzilla.redhat.com/509383</ref>
| |
| * Note on Xen Dom0 support.
| |
| * New wiki pages created.
| |
| * Detailed run-down of current virt bugs.
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== USB Passthrough to Virtual Machines ==== | | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| [[MarkMcLoughlin|Mark McLoughlin]]
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| posted instructions<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00182.html</ref>
| | compared to Fedora 12. |
|
| |
|
| <pre>This has been covered in FWN, find ref</pre> | | [[DanielBerrange|Daniel Berrange]] |
| | 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 |
| | 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 |
| | also pretty close to that using what's best described as a hybrid of |
| | kvm-83 and kvm-84." |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== best Fedora virtualization ====
| |
| [[RichMahn|Rich Mahn]]
| |
| asked<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00201.html</ref>
| |
|
| |
| <pre>
| |
| I am planning on running several virtual machines on a single host. I
| |
| will have two or three Linux baeed virtual machines and one or two
| |
| Windoze. I plan on using a F11 host system.
| |
|
| |
| I need most of these to run automatically on boot-up of the host
| |
| system. It would be really nice if I could use something like the
| |
| Ctl-Alt-FN to be able to access and switch between virtual machines.
| |
| This needs to be stable. The machines that these virtual machines are
| |
| intended to replace are often running hundreds of days between
| |
| reboots.
| |
|
| |
| My gut feel is that the virt-manager suite might be the way to go,
| |
| editting the apropriate xml files as required. I also see there
| |
| is a qemu launcher and it seems to work okay. I suspect there are
| |
| others as well.
| |
|
| |
| What tends to be the consensus here on the various virtual machine
| |
| managers? Are there white papers somewhere that could give some
| |
| insight?
| |
| </pre>
| |
|
| |
| [[RichardJones|Richard Jones]]
| |
| answered<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00202.html</ref>
| |
| <pre>
| |
| For stability and long-term maintainability, I wonder if you've
| |
| considered using RHEL or CentOS? That means you have to use Xen as
| |
| the hypervisor, but if you use libvirt / virsh / virt-manager, the
| |
| future upgrade path to KVM is reasonable. All tools stay the same,
| |
| and you just need to run our forthcoming v2v tool on the guests (or
| |
| reinstall the guests) when you upgrade.
| |
| </pre>
| |
| <pre>
| |
| The only one we're supporting here on
| |
| Fedora<ref>http://fedoraproject.org/wiki/Virtualization</ref> is libvirt / virsh /
| |
| virt-manager. Use 'virsh edit <domain>' to edit the XML for a domain.
| |
| The same commands will work on RHEL / CentOS too.
| |
| </pre>
| |
|
| |
| [[RichMahn|Rich Mahn]] reported problems with ISO images stored on NFS and
| |
| [[GeneCzarcinski|Gene Czarcinski]]
| |
| opened<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00015.html</ref>
| |
| a bug ({{bz|508865}}
| |
| <pre>
| |
| I suspect this is the result of trying to use SELinux to protect everything
| |
| and the mandatory access control idea that everything is disallowed except
| |
| that which is explicitly permitted.
| |
|
| |
| But, I just do not understand what and why CD/DVD images and devices are being
| |
| protected. Furthermore, when virtualization changes a file's context
| |
| (including /dev/sr0), could this effect other valid usage of these
| |
| files/devices? If there is no effect for other applications, then just what is
| |
| protected?
| |
| </pre>
| |
| 507555
| |
|
| |
|
| | ==== ==== |
| <references /> | | <references /> |
|
| |
|
| === Libvirt List ===
| | ==== ==== |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
| | |
| ==== ==== | |
| <references /> | | <references /> |
libvirt