|
|
| (124 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]. |
|
| |
|
| ==== F12 Feature: Host Information ==== | | ==== Virt Status Report ==== |
| [[RichardJones|Richard Jones]] | | [[JustinForbes|Justin Forbes]] |
| posted<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00123.html</ref> | | posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report. |
| an RFC for a feature<ref>http://fedoraproject.org/wiki/Features/Hostinfo</ref> he's working on for [[Releases/12|Fedora 12]].
| | 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. |
| The feature will "Allow a virtual machine to see information and statistics from the
| |
| host operating system."
| |
| | |
| For example, it will "Allow a virtual machine to look at host information (such as number of
| |
| physical, not just virtual CPUs), and statistics like the load on the
| |
| host."
| |
| | |
| [[DanielBerrange|Daniel Berrange]]
| |
| noted<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00130.html</ref>
| |
| that "a core goal of this
| |
| hostinfo service is to avoid any use of networking. We don't want to
| |
| presume that a guest has a NIC, nor that the host has a configured
| |
| NIC on the same LAN as the guest." So this feature will make use of serial
| |
| ports to pass queries and responses between the guest and the host.
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== libguestfs Super-minimized Appliance ==== | | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| [[RichardJones|Richard Jones]]
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| created<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00118.html</ref>
| | compared to Fedora 12. |
| a set of "very experimental" patches to {{package|libguestfs}}
| |
| "which allow you to build a so-called 'supermin (super-minimized) appliance'."
| |
| | |
| Within <code>libguestfs</code>, "The normal appliance is a self-contained Linux operating system, based
| |
| on the Fedora/RHEL/CentOS Linux distro. So it contains a complete
| |
| copy of all the libraries and programs needed, like kernel, libc,
| |
| bash, coreutils etc etc."
| |
| | |
| "The supermin appliance removes the kernel and all the executable
| |
| libraries and programs from the appliance. That just leaves a
| |
| skeleton of config files and some data files, which is obviously
| |
| massively smaller than the normal appliance. At runtime we rebuild
| |
| the appliance on-the-fly from the libraries and programs on the host
| |
| (eg. pulling in the real /lib/libc.so, the real /bin/bash etc.)"
| |
|
| |
|
| "The new appliance is a mere 500K, so <code>libguestfs</code> RPMs will be a lot
| | [[DanielBerrange|Daniel Berrange]] |
| smaller. Of course that just means they will have many more
| | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| dependencies, so the amount pulled down will be the same or greater."
| | "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 /> |
|
| |
|
| ==== A guest fish in the pipes ====
| |
| [[RichardJones|Richard Jones]]
| |
| patched<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00177.html</ref>
| |
| {{package|libguestfs|guestfish}}. "This patch adds support for pipes to guestfish, so you can pipe output
| |
| from a <code>guestfish</code> command through a command on the host. The canonical
| |
| example is:
| |
|
| |
| ><fs> hexdump /bin/ls | less
| |
|
| |
| Another example, looking for root backdoors in the password file:
| |
|
| |
| ><fs> cat /etc/passwd | awk -F: '$3 == 0 { print }' | grep -v ^root:
| |
|
| |
| Anything right of the first pipe symbol gets passed to the local
| |
| shell, thus expansion, redirection and so on work on that."
| |
|
| |
|
| | ==== ==== |
| <references /> | | <references /> |
|
| |
|
| |
|
| |
| === Libvirt List ===
| |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
|
| |
| ==== Safe PCI Device Passthrough ====
| |
| [[MirkoRaasch|Mirko Raasch]]
| |
| asked<ref>http://www.redhat.com/archives/libvir-list/2009-June/msg00516.html</ref>
| |
| "How can i start my guest with three pci devices passed through and {{package|libvirt}}?" Starting <code>qemu</code> by hand appeared to work.
| |
| But virsh start produced an error:
| |
| <pre>
| |
| libvirtd: 15:44:55.459: warning : pciTrySecondaryBusReset:483 : Other
| |
| devices on bus with 0000:05:01.0, not doing bus reset
| |
| </pre>
| |
|
| |
| [[DanielBerrange|Daniel Berrange]]
| |
| recalled<ref>http://www.redhat.com/archives/libvir-list/2009-June/msg00518.html</ref>
| |
| "what <code>libvirt</code> is complaining about is that there are other devices
| |
| in the PCI bus which are not associated with this guest, and thus there
| |
| is no way to safely reset the device you are trying to assign, without
| |
| endangering the host OS or other guest OS."
| |
|
| |
| Adding "when you launch QEMU manually there is no
| |
| checking for whether the PCI devices are in use by other guests,
| |
| or by the host OS. So while it may launch QEMU, it is not running
| |
| safely, and eg, if your guest OS does a PCI bus reset it could
| |
| kill/harm your host OS."
| |
|
| |
| PCI device passthrough is a new feature<ref>http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment</ref> in Fedora 11.
| |
|
| |
| <references />
| |
|
| |
| ==== VMware ESX driver status update ====
| |
| [[MatthiasBolte|Matthias Bolte]]
| |
| continued<ref>http://www.redhat.com/archives/libvir-list/2009-June/msg00469.html</ref> work (FWN #177<ref>http://fedoraproject.org/wiki/FWN/Issue177#Libvirt_VMWare_ESX_Driver_In_Development</ref>) to create a VMware ESX driver for <code>libvirt</code>.
| |
|
| |
| Matthias is currently "working on the VMX config to domain XML mapping for
| |
| dump/create XML" using the VMware Infrastructure API<ref>http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/</ref>.
| |
|
| |
| <references />
| |
|
| |
| === oVirt Devel List ===
| |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
| |
|
| |
|
| ==== ==== | | ==== ==== |
| <references /> | | <references /> |
libvirt