From Fedora Project Wiki

(→‎Post 10 Release Quirks: f10 domu on f8 dom0)
Line 105: Line 105:


=== Post 10 Release Quirks ===
=== Post 10 Release Quirks ===
* On a F8 dom0. Installing F9 domU pulls kernel from releases/9/Fedora/x86_64/os/images/xen/vmlinuz this does not exist on F10 and creation fails.
==== Installing F10 DomU on F8 Dom0 ====
On a F8 dom0. Installing F9 domU pulls kernel from releases/9/Fedora/x86_64/os/images/xen/vmlinuz this does not exist on F10 and thus creation fails. The version of {{package|python-virtinst}} on F8 does not know the kernel path changed. Try this test version and give it some positive karma if it works for you.
* http://koji.fedoraproject.org/koji/buildinfo?buildID=71125
* https://bugzilla.redhat.com/show_bug.cgi?id=458164


=== Windows KVM Guest and Paravirt NIC Drivers ===
=== Windows KVM Guest and Paravirt NIC Drivers ===

Revision as of 20:04, 26 November 2008

Dale Bewley

DaleBewley FirstnameLastname-head.png I'm vegan and I mountain bike a lot.

Contact

Activities within Fedora

Wiki Work

Virtualization Quick Start

Docs Virtualization Beat

FWN Virtualization Beat

153, 152, 151, 150 n/a, 149, 148, 147, 146, 145, 144, 143, 142, 141, 140 n/a, 139 n/a, 138, 137

Notes To Self

Virtualization Release Notes

I'm gathering links to become oriented with the Fedora Docs Project and Virtualization features for F10.

Howto

Content

Versions

Virtualization Package Versions
Package F9 Release F9 Updates (20081110) F10 Release Upstream (20081110) Rel Notes
kvm 65-1 65-10 74-5 78 http://kvm.qumranet.com/kvmwiki/ChangeLog
libvirt 0.4.2-1 0.4.6-2 0.4.6-3 0.4.6 http://www.libvirt.org/news.html
python-virtinst 0.300.3-5 0.300.3-7 0.400.0-4 0.400.0 http://virt-manager.et.redhat.com/download.html
virt-df n/a 2.1.1-8 2.1.4-2 2.1.4 http://et.redhat.com/~rjones/virt-df/
virt-manager 0.5.4-3 0.5.4-4 0.6.0-3 0.6.0 http://virt-manager.et.redhat.com/download.html
virt-mem n/a n/a 0.2.9-6 0.3.1 http://et.redhat.com/~rjones/virt-mem/faq.html
virt-top 0.4.1.1-1 1.0.1-4 1.0.3-2 1.0.3 http://et.redhat.com/~rjones/virt-top/ChangeLog.txt
virt-viewer 0.0.3-1 n/a 0.0.3-3 0.0.3 http://virt-manager.et.redhat.com/download.html
xen 3.2.0-10 3.2.0-15 3.3.0-1 3.3.0 http://www.xen.org/download/
xenner 0.29-2 0.41-1 0.46-3 0.46 http://cvs.bytesex.org/xenner.html
xenwatch n/a 0.5.3-1 0.5.3-1 0.5.3 http://cvs.bytesex.org/xenwatch.html
  • Quick hack to gather info for table above
#!/bin/bash
grep -v '^#' pkgs.in | while read line; do
    grep -v '^#' dist.in | while read dist; do
            pkg=`echo $line | awk '{print $1}'`
            notes=`echo $line | awk '{print $2}'`
            ver=`koji latest-pkg "$dist" "$pkg" | tail -1 | awk '{print $1}'`
            echo "$pkg, $dist, $ver, $notes"
    done
done

Post 10 Release Quirks

Installing F10 DomU on F8 Dom0

On a F8 dom0. Installing F9 domU pulls kernel from releases/9/Fedora/x86_64/os/images/xen/vmlinuz this does not exist on F10 and thus creation fails. The version of Package-x-generic-16.pngpython-virtinst on F8 does not know the kernel path changed. Try this test version and give it some positive karma if it works for you.

Windows KVM Guest and Paravirt NIC Drivers

As seen in FWN#152. The Package-x-generic-16.pngvirt-manager GUI doesn't have the knobs in the UI yet to enable virtio drivers. THe Package-x-generic-16.pnglibvirt framework underneath does support it, so it can be done by hand. Here's how. (not yet tested)

  • Download the drivers to guest
  • Shutdown the guest virsh shutdown domain
  • Dump the libvirt XML virsh dumpxml domain > domain.xml, and change the network settings. To the <interface> block add:
 <model type='virtio'/>
  • Redefine the domain with the altered config virsh define domain.xml
  • Start the guest virsh start domain and install the driver within Windows

See also: http://www.linux-kvm.com/content/tip-how-setup-windows-guest-paravirtual-network-drivers