Showing headlines posted by dba477

Rebuild procedure of regular qemu-kvm package to support spice on Natty Narwhal follows bellow. It depends on all packages from ppa:serge-hallyn/spice2 except qemu-kvm-spice. New packages install spice enabled /usr/bin/qemu* binaries and graphical spice client. I just disabled libvirtd's AppArmor profile to be able manage domains via virt-manager. Spice install may be performed via virt-install. It would understand options "--graphics spice", "--video qxl". All required packages have been uploaded and built in PPA Spice on Ubuntu 11.04

Packages installed via ppa:serge-hallyn/spice2 have been tested for F14, W7 KVMs installs and runtime. qemu-kvm-spice (0.14.0+noroms-0ubuntu4qxl2) package is based on the most recent RH’s QXL patches sets for qemu-kvm-0.14.tar.gz. Add new repository to system . . .

Primary target is to get virt-install supporting options “--graphics spice”,”--video qxl”,”--channel spicevmc”. One drawback has been noticed. Virt-manager requires “Add hardware”->”Graphics”->”VNS Server” before you can proceed with normal VNC installation. Obvious workaround via option “Customize configuration before install”.

Following bellow is brief exercise managing Gnome 3 Desktop to create Ubuntu Maverick Meerkat KVM and run it in spice session.First of all after “yum update” i verified current “qemu” and “libvirt” status on Fedora 15. Virtualization Group has been selected during initial install.Then added Virt-Manager to favourites to avoid several mouse clicks at every start up.

The most recent patches to Fedoras Qemu 0.14 came into qemu-0.14.0-4.fc14.src.rpm on 03/18/2011. Following bellow is brief description of F14 KVM and Spice Server set up via “Libvirt Preview”. Configured KVM Server allows to create Ubuntu 11.04 Desktop KVM (alpha 3), which may run in spice session after QXL driver install.

Following bellow is attempt to test mentioned patch to resolve problem with loading KVM with “-vga qxl” by /usr/bin/qemu-kvm (v. 0.14) on Fedora 14 ( Libvirt Preview Environment ) . View : http://patchwork.ozlabs.org/patch/84704/. Test was successful for SL6,F14,W2K3,W7 KVMs (without QXL driver installed) and failed on Ubuntu 10.10 KVM no matter of presence or absence of QXL driver.

Fedora 14 has version of Libvirt 0.8.7 and qemu-0.13.0-1 installed via Rawhide Preview Repo. However, straightforward attempt to virt-install Windows 7 on virtio boot device fails to detect device after viostor.sys gets preloaded. It’s a known bug [1]. Actually, thread at Red Hat Bugzilla – Bug 656353 contains required patch , but doesn’t contain any explanation how to rebuild and reinstall required package python-virtinst-0.500.4-1.fc14.noarch.rpm.Detailed workaround for this issue follows bellow.

First of all setup DNJL PPA to upgrade KVM/QEMU up to Qemu 0.12.5 & Libvirt 0.8.3 on Ubuntu Lucid Server and download the most recent Fedora virtio-win drivers from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/image... as floppy and ISO image. Notice , that same virt-install will run fine on KVM Server Ubuntu 10.10 due to required versions of Libvirt & Qemu appear to be installed by default.

Create Windows KVM via virt-manager as usual. Download latest VirtIO Win drivers from Fedora. Location is http://alt.fedoraproject.org/pub/alt/virtio-win/latest/image... File virtio-win-1.1.11-0.vfd to KVM and ISO image virtio-win-1.1.11-0.iso to Fedora’s FS. Create fake qcow2 file.

Setup KVM-QEMU instance on SL 6 alpha 3 and install SL6 KVM with ISO image SL-6-x86_64-2010-12-17-boot.iso to run installation via http://ftp.scientificlinux.org/linux/scientific/6rolling/x86... source. Follow [2] with minor changes for “yum install script” in previously installed SL 6 KVM via Net Repos. Virtio drivers should be enabled during install.

KVM as a “full virtualization” is a nice feature because it allows you to run any operating system virtualized. However, it’s relatively slow because the hypervisor has to emulate actual physical devices such as RTL8139 network cards and the most recent SeaBios emulates IDE interface.This fragment from KVM guest dmesg log is fair enough

Include virtualization group during initial install. Comment out lines 343,344 in /usr/share/virt-manager/virt-manager.py to allow virt-manager to start . Set up bridged networking as follows . .

This post follows up “Howto” http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial . Install kernel-2.6.32.26-174.xendom0.fc12.src.rpm on RHEL 6 Server.

Following bellow is brief instruction of Solaris 11 Express PV Guest install via virsh and XML profiling at Xen 4.0.1 Dom0 on top of Fedora 14. Pvops kernel 2.6.32.26 has been built via Jeremy Fitzhardinge Git Repos. It also may be installed per Michael Young . View http://repos.fedorapeople.org/repos/myoung/dom0-kernel/fedor... via kernel-2.6.32.26-174.xendom0.fc12.src.rpm rebuild on F14.

Download from http://koji.fedoraproject.org/koji/taskinfo?taskID=2581021 file kernel-6.37-0.1.rc1.git0.xendom0.fc15.src.rpm been built by Michael Young and install it. In mean time following patches :- patch-2.6.37-rc1.bz2, patch-2.6.37-rc1-git5.bz2 should be downloaded from http://kernel.org and copied to /root/rpmbuild/SOURCES folder Update /root/rpmbuild/SPECS/kernel.spec correspondently

Xen Core Dom0 support features started to merge mainline Linux during 2.6.37 merge window. In particular, kernel may be loaded under Xen, daemon xend starts in Dom0. However, xen backend devices are not yet in the vanilla kernel. It’s impossible to create and start guests.

Straight forward attempt to load 2.6.34.7 kernel xenified aka Suse under Fedora’s 14 Xen 4.0.1 generates following output to console. Starting udev: udevd-work[591]: kernel-provided name 'pci_iomul' and NAME= 'xen/pci_iomul' disagree, please use SYMLINK+= or change the kernel to provide the proper name
udevd-work[539]: kernel-provided name 'evtchn' and NAME= 'xen/evtchn' disagree, please use SYMLINK+= or change the kernel to provide the proper name

Following post is a brief instruction of port 2.6.34.7 xenified aka Suse kernel to Ubuntu 10.10 desktop , to support Dom0 under Xen 4.0.1. Vanilla 2.6.34.7 gets patched via Andrew Lyon’s rebased patch set xen-patches-2.6.34-5.tar.bz2.

Following bellow is brief instruction of mentioned set up loading xen back-end, evtchn, gntdev devices separately from pvops kernel 2.6.32.24 under Xen 4.0.1 on top Ubuntu Maverick Meerkat Desktop. Due to Desktop environment we have first to disable Network Manager and restart networking manually updating /etc/network/interfaces.

This post is targeting pvops kernel 2.6.32.23 configuration close to 2.6.34.7 aka Suse 11.3 Xenified kernel. This config by some reasons allows OpenSolaris134/OpenIndiana147 PV Guest obtain IP address pretty stable on systems Xen 4.0.1 & PVOPS like it happens on OpenSuse 11.3 with Xen Hypervisor upgraded up to 4.0.1 and the most recent XenLinux 2.6.34.7 kernel.