|
|
| (256 intermediate revisions by 3 users not shown) |
| Line 2: |
Line 2: |
|
| |
|
| {{Anchor|Virtualization}} | | {{Anchor|Virtualization}} |
| | |
|
| |
|
| == Virtualization == | | == Virtualization == |
| In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. | | 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]
| |
|
| |
| ==== New Options for Guest Cloning ====
| |
| Cole Robinson posted<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00051.html</ref> a patch to enable <code>virt-install</code> to
| |
| "build a guest around an existing disk image, skipping the OS install step."
| |
| Cole also
| |
| posted<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00050.html</ref>
| |
| a patch for <code>virt-clone</code> which allows for cloning from an XML file
| |
| "rather than require the use of a guest defined on the current connection."
| |
|
| |
| <references />
| |
|
| |
| ==== Obtaining Guest IP Address from the Host ====
| |
| Thomas Mackell inquired<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00036.html</ref> about a way to obtain the IP address of a guest that was easier than logging into it and running <code>ifconfig</code>. Cole Robinson pointed out {{package|virt-mem}}<ref>http://et.redhat.com/~rjones/virt-mem/</ref> which is a collection of utilities for interrogating <code>KVM</code> guests. Tools included are
| |
| <code>virt-uname</code>, <code>virt-dmesg</code>, <code>virt-ps</code>, and <code>virt-ifconfig</code>.
| |
|
| |
| <references />
| |
|
| |
|
| === Fedora Virtualization List === | | === Fedora Virtualization List === |
| Line 32: |
Line 14: |
| [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. | | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| ==== Fedora Virt Status Update ==== | | ==== Virt Status Report ==== |
| Mark McLoughlin posted two<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00077.html</ref>
| | [[JustinForbes|Justin Forbes]] |
| <ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00078.html</ref> very detailed weekly status reports since the last FWN Virtualization beat. | | 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. |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| ==== Qemu Packaging and noarch BIOS Firmware ==== | | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| The process <ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00066.html</ref> of building BIOS firmwares to support architecturally diverse guests on architecturally diverse hosts
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| is very involved and repetitive. Glauber Costa learned<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00068.html</ref> of changes coming to [[Koji]] which could simplify the process by allowing for bundled BIOS images to be built as "<code>noarch</code>" RPMs. These would be readily available to hosts on any architecture in the repository. Save for some "second class citizens"<ref>http://www.redhat.com/archives/fedora-virt/2009-February/msg00072.html</ref> in the repo.
| | compared to Fedora 12. |
|
| |
|
| <references />
| | [[DanielBerrange|Daniel Berrange]] |
| | | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| === Fedora Xen List ===
| | "The KVM based virtualization in RHEL-5.4 is not nearly so far behind |
| This section contains the discussion happening on the
| | Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was |
| [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. | | 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 |
| ==== dom0 Kernel Experimentation Continues ====
| | kvm-83 and kvm-84." |
| Michael Young continued<ref>http://www.redhat.com/archives/fedora-xen/2009-February/msg00031.html</ref> to help others experiment with the nacent dom0 support in the {{package|kernel}} and posted another RPM. There are still significant problems precluding its use for anything beyond testing.
| |
|
| |
|
| <references /> | | <references /> |
|
| |
|
| === Libvirt List ===
| |
| This section contains the discussion happening on the
| |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
|
| |
| ==== Snapshot Volumes ====
| |
| Nick Moffitt asked<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00195.html</ref> "Is there any interface to <code>libvirtd</code> that allows it to create volumes that are snapshots of existing volumes?"
| |
|
| |
| Daniel P. Berrange pointed<ref>http://libvirt.org/formatstorage.html#StorageVolBacking</ref> out this feature was recently added to {{package|libvirt}} 0.6.0.
| |
| "Basically when creating a storage volume, you just need to pass information about the backing storage volume. It'll thus create a volume which is a snapshot of this backing store."
| |
|
| |
|
| | ==== ==== |
| <references /> | | <references /> |
|
| |
|
| ==== netcf Network Interface Configuration Library ==== | | ==== ==== |
| David Lutterkort has been working on the disconnect between
| |
| {{package|libvirt}} and host network interface configuration for some time.
| |
| (See FWN#159 "Configuring Host Interfaces RFC")
| |
| <ref>http://fedoraproject.org/wiki/FWN/Issue159#Configuring_Host_Interfaces_RFC</ref>
| |
| "After talking with Dan Williams, who is working in {{package|NetworkManager}}", it became<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00228.html</ref> clear to David that solving this problem "is also
| |
| useful for NM and would help them with handling system-wide interface
| |
| configuration." David then began work on <code>netcf</code><ref>http://git.et.redhat.com/?p=netcf.git;a=tree</ref>
| |
| | |
| Mark McLoughlin complimented<ref>http://www.redhat.com/archives/libvir-list/2009-February/msg00229.html</ref>
| |
| the work and updated the shared network interface feature page<ref>http://fedoraproject.org/wiki/Features/Shared_Network_Interface</ref>. The goal of this feature in development is to "Enable guest virtual machines to share a physical network interface (NIC) with other guests and the host operating system. This allows guests to independently appear on the same network as the host machine."
| |
| | |
| <references /> | | <references /> |
libvirt