Showing headlines posted by dba477

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.

Following bellow is attempt to debianize Xen 4.0.1-rc3,in other words to build debian packages been installed on recent Ubuntu 10.04 (9.10) servers set corresponding version of Hypervisor up. We follow closely recent blog entry of "User Virtual" , attempting to fix errors in patching of current version of /etc/init.d/xend.

Add two lines to /etc/apt/sources list
deb http://ppa.launchpad.net/dnjl/virtualization/ubuntu lucid main
deb-src http://ppa.launchpad.net/dnjl/virtualization/ubuntu lucid main
Running “add-apt-repository ppa:/gwibber-daily/ppa” didn’t work for me due to “apt-get update” complaining absence key with different value, that’s why i imported requested key via command bellow and succeeded with “apt-get update”

Posting bellow follows recent submission of Stefano Stabelinni to xen-devel mailing list. Add to /root/rpmbuild/SOURCES new patch callback_4.0.patch to implement event channel for HVM DomUs at Xen 4.0 Dom0. Rebuild xen rpms, udating xen.spec correspondently and reinstall rpms performing hot upgrade of Xen 4.0 Hypervisor. Then reboot. Create for instance Ubuntu Lucid HVM and build 2.6.34 kernel on DomU per Stefano

Install Xen 4.0 and Libvirt like on F12 ( [1] ). Via my experience xend will hang for 5-7 min at startup and xen managed bridging will fail as well. At the same time PV guests won’t be able to obtain IP via interface virbr0. Workaround for the issue follows bellow.

Due to ongoing issue with virsh compiled against libvirt 0.7.5 when working with Xen 4.0 Hypervisor. I attempted to downgrade libvirt and related stuff to Ubuntu Karmic’s ( well tested version with Xen). Proceed as follows

Schema worked so nicely on Ubuntu Karmic Koala doesn’t help any longer.Virt-install crashes right away attempting to launch VNC console. Set up Xen 4.0 Dom0 with pvops kernel 2.6.32.12 on top of Ubuntu 10.04 Server . Install just two packages virtinst and python-virtinst.

The procedure bellow in general follows Thiago’s Martins submission to xen-devel mailing list. However,sequence of steps has been changed, /dev/xen/evtchn device hard linked with with pvops kernel, git checkout procedure is more straight forward and one Change-set from xen-4.0-testing.hg back ported to Xen 4.0 to support grub2 notation ‘(hd0,1)’ specific for Ubuntu 10.04 aka Lucid Lynx. The way as Xen 4.0 Dom0 set up worked on Ubuntu 9.10 (04) Servers doesn’t work any longer.

Finally Mark Jonson submitted to xen-devel mailing list patch for ZFS 24 support at Xen 4.0. Patch mentioned bellow was successfully tested at Xen 4.0 Dom0 with pvops kernel 2.6.32.11 on top of Fedora 12 via modifying Michael’s Young xen-4.0.0.7.fc12.src.rpm and direct patching xen 4.0 official tarball on Ubuntu Karmic Koala Server.

Due to absence in meantime pygrub support for ZFS 24 in Xen 4.0 unix kernel and boot_archive have to be copied off the disk to Dom0. In my case OSOL 134 PV DomU was able to obtain IP address just once after first boot up configuring SMF . Afterwards it required restarting ( or reenabling) service svc:/network/physical:nwam, what finally brought me to accomplish this procedure as OSOL service , because no analog of /etc/rc.local exists on OSOL.

The final target of this post is to demonstrate how flexible is Ubuntu Karmic Koala Server environment. Build Xen 4.0-rc8 and the most recent stable pvops kernel 2.6.32.10 ( with DRM support). Loading Xen Instance followed by install Ubuntu’s Libvirt environment, providing utility virt-install for creating PV and HVM DomUs, virt-manager completely functional to manage any DomU been built via virt-install

Michael Young wrote xen-4.0.0-0.2.rc4.fc12.src.rpm for Xen-4-rc4 for Fedora 12 to install Hypervisor (changeset 20950). Schema bellow modifying content of mentioned src.rpm allows to build set of RPMS upgrading Xen Hypersor 4.0 matching current tip CS of http://xenbits.xensource.com/xen-unstable.hg,no matter of rc4 in fact, via hot upgrade without rebuilding development Xen System on top of F12 with recent PVOps kernel 2.6.32.9. Directory gemu-xen.git is only determined by value of QEMU_TAG in Config.mk file under xen-unstable tree clone.

This is the best book i’ve ever read in my life about architecture of Xen Hypervisor, concepts of paravirtualization, dom0,domU, performance advantages of PV guests. I would say that core theoretical background of Xen Hypervisor is written pretty clear. It brings comprehension of Xen to persons, which even wouldn’t be willing to work on this topic too much. The last is very important from my standpoint.