|
|
| (416 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | [[Category:Virtualization]] <!-- do not copy into FWN issue --> |
| | |
| {{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: [[DaleBewley | Dale Bewley]]
| |
| | |
| === Enterprise Management Tools List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
| |
| | |
| === Fedora Xen List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
| |
| | |
| ==== Support for F10 domU on RHEL5.2 dom0 ====
| |
| [[JonStanley|Jon Stanley]] noticed[1] that a RHEL 5.2 dom0 was unable to
| |
| install a current Fedora 10 Rawhide domU.
| |
| [[MarkMcLoughlin|Mark McLoughlin]] explained[2] that the
| |
| "older virt-install doesn't know to look in the 'images-xen' stanza
| |
| in the '.treeinfo' file to determine which images to use". Patches are being
| |
| backported to RHEL 5.3 for this[3]. A further issue[4] is a lack of bzimage
| |
| support in the <code>libxc</code> of RHEL.
| |
| | |
| [1] https://www.redhat.com/archives/fedora-xen/2008-October/msg00002.html
| |
| | |
| [2] https://www.redhat.com/archives/fedora-xen/2008-October/msg00003.html
| |
| | |
| [3] https://bugzilla.redhat.com/460585
| |
| | |
| [4] https://bugzilla.redhat.com/457199
| |
| | |
| [[MichaelYoung|Michael Young]] asked[5] about a timeline for these patches and expressed concern that there could be "a period of time where there won't be any supported Redhat or Fedora platform to run Xen guests, and of course the lack of current support in RHEL is reducing the testing that Fedora 10 xen is getting."
| |
| | |
| [5] https://www.redhat.com/archives/fedora-xen/2008-October/msg00006.html
| |
| | |
| === Libvirt List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
| | |
| ==== KVM Domain Migration Not Yet Supported ====
| |
| [[KennethNagin|Kenneth Nagin]] noticed[1] a problem migrating a KVM guest.
| |
| [[DanielBerrange|Daniel P. Berrange]] said[2] that's because it's not yet supported. "Currently KVM's private fork of QEMU
| |
| has some migration support, but this is not written in a suitable
| |
| way for " libvirt "to use - it blocks the QEMU monitor on startup. Upstream
| |
| QEMU is getting better migration support and once that's done we can
| |
| support it in libvirt."
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00147.html
| |
| | |
| [2] https://www.redhat.com/archives/libvir-list/2008-October/msg00148.html
| |
| | |
| ==== Disable QEMU Drive Cacheing ====
| |
| [[DanielBerrange|Daniel P. Berrange]] posted[1] a patch with the following explaination.
| |
| | |
| QEMU defaults to allowing the host OS to cache all disk I/O. This has a
| |
| couple of problems
| |
|
| |
|
| * It is a waste of memory because the guest already caches I/O ops
| | Contributing Writer: [[User:Dale | Dale Bewley]] |
| * It is unsafe on host OS crash - all unflushed guest I/O will be lost, and there's no ordering guarantees, so metadata updates could be flushed to disk, while the journal updates were not. Say goodbye to your filesystem.
| |
| * It makes benchmarking more or less impossible / worthless because what the benchmark things are disk writes just sit around in memory so guest disk performance appears to exceed host diskperformance.
| |
|
| |
|
| This patch disables caching on all QEMU guests. NB, Xen has long done this | | === Fedora Virtualization List === |
| for both PV & HVM guests - QEMU only gained this ability when -drive was
| | This section contains the discussion happening on the |
| introduced, and sadly kept the default to unsafe cache=on settings.
| | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00180.html | | ==== Virt Status Report ==== |
| | [[JustinForbes|Justin Forbes]] |
| | 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. |
|
| |
|
| ==== NSIS Windows Installer in Nightly Builds ====
| | <references /> |
| [[RichardJones|Richard W.M. Jones]] added[1] NSIS[2] support to generate a Windows installer in the nightly build. Richard also recently blogged[3] on the subject on MinGW and NSIS.
| |
|
| |
|
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00191.html
| | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| | compared to Fedora 12. |
|
| |
|
| [2] http://nsis.sourceforge.net/ | | [[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." |
|
| |
|
| [3] http://camltastic.blogspot.com/2008/10/mingw-compile-software-for-windows.html
| | <references /> |
|
| |
|
| In reply to another thread[4] [[DanielBerrange|Daniel P. Berrange]] explained
| |
| support is targeted for "client-mode only. ie, allow
| |
| use of libvirt clients to connect to remote Linux hosts running libvirtd", and that there
| |
| is no emminent Hyper-V or VMWare support.
| |
|
| |
|
| [4] https://www.redhat.com/archives/libvir-list/2008-October/msg00304.html
| | ==== ==== |
| | <references /> |
|
| |
|
| === oVirt Devel List === | | ==== ==== |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
| | <references /> |
libvirt