Showing headlines posted by dba477

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.

In other words to behave exactly as in Fedoras or CentOS environment in regards of any xenified DVD distros loop mounted as pages of local Apache Servers or remote official HTTP mirrors not only owned by Novell, but RH as well . Download from the Net virt-manager-0.8.4-5.1.1.src.rpm

Procedure bellow fixes hidden issue in recently developed xen-4.0.1_21326_01-1.1.src.rpm. It removes error “xen be core: xen be core: can’t open gnttab device” in corresponding /var/log/xen log file during attempt to run virt-install for PV Guest in VNC mode or attempt to run python installation profile referencing VFB for domains of same kind.

In meantime Xen 4.0.1 is available via rawhide repositories . Been installed along with 2.6.32.21 pvops kernel and the most recent libvirt 0.8.3 on top of F14 (rawhide) via just several yum install commands,it doesn’t require any longer to build xen rpms using corresponding xen-4.0.1-1.fc14.src.rpm. Changing preferences allows to play with Gnome 3 shell managing virt-manager and other desktop tools.

The most recent pvops kernel 2.6.32.19 allows to enable kernel modesetting (KMS) under Xen 4.0.1-rc6 on top of Ubuntu Lucid Server and Fedora 13. Actually , current setup of Xen 4.0.1&PVOPS on top of Ubuntu 10.04 Server is different from http://wiki.xen.org/xenwiki/Xen4.0 : How to install Xen 4.0 (1) and brief instructions follow bellow. Status of the problem in general along with list of video adapters been tested may be viewed at http://wiki.xensource.com/xenwiki/XenPVOPSDRM.

Install “kotd” (kernel of the day) via ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64/ kernel-xen-2.6.34.1-0.0.19.40d88ce.x86_64.rpm ( supporting udev 157). Next step supposed to be is to upgrade Xen 4.0 to support Lucid Grub2 syntax.

Well known Bugzilla Bug 1612 “Can’t start VM when vif set and udev version is greater than 151? is also affecting xenified aka Suse kernel 2.6.34-12-xen. The workaround for the issue might be udev downgrade from 157 to 151. Following bellow is step by step description of this procedure on Opensuse 11.3 successfully fixed “Hotplug scripts not working” error.

The procedure driven by virt-install (libvirt 0.8.2) has been managed via keyboard due to mouse pointer stayed frozen at center of VNC window all the time of installation and finally at Gnome Desktop came up at the end.Get access to text mode console and edit /etc/inittab to switch to initdefault 3

Due to presence CSs 21556 (blktap2: Fix tapdisk disktype issues) , 21167 (Port latest grub zfs boot code to pygrub) Xen instance been created bellow would provide an option to test NexentaStor-Community-3.0.2-xen.tar.bz2 . In meantime new service xencommons should be configured for successful xend startup and network bridge configuration has to be performed manually vs 4.0.1. Service xencommons actually starts xenstored and xenconsoled services before xend.