Showing headlines posted by dba477

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.

Recent pulling GRUB2 supporting CSs into xen-3.4-testing.hg immediately makes sense to build xen 3.4.3-2.fc12.src.rpm to be able to set up current version of 3.4.3 Xen Hypervisor on Fedora 12 working pretty smoothly with Libvirt packages ( vs Xen 4.0) and the at same time supporting GRUB2 PV DomUs , say Ubuntu 9.10 Server or Debian Squeeze.

Due to set of CSs for GRUB 2 Support written by Ian Campbell usual sharing image devices between Ubuntu Karmic Koala Server HVM and PV Guests appears available at Xen-4.0 Linux Dom0. Fedora 12 has been selected due to presence of Libvirt 0.7.1 providing virt-install and virt-manager utilities.

This posting is actually responding recent entry in Martin's Blog OpenSolaris 2009.06 domU on opensuse 11.2 dom0 Martin states:- Then I tried out a number of current linux distributions, but except for openSuSE none had a dom0 kernel out of the box which really is a shame. Seems I need to look more closely into KVM with virtio support. Via article bellow i try to explain that due to efforts of Jan Beulich and Andy Lyon xenified aka Suse Kernel 2.6.31.8(9) may be built on any Linux and along with the most recent stable Xen Hypervisor (3.4.2 and higher) port provide Xen Environment supporting OpenSolaris PV Guests , including the most recent unstable builds like 129,130,131 ( i mean vncserver behavior on OSOL PV DomU and GDM/VNC setup ).

Recent “zypper update” on November’s openSUSE 11.2 release brought system to the most recent status. Current 2.6.31.8-xen kernel works fine. Seems like a next generation of xenified aka Suse kernels is on the go right now. However, i believe,that vm-install on recently updated 11.2 works same way as before maintenance update. So, in meantime vm-install doesn’t inderstand either HTTP or CDROM sources attempting to create PV Guest and virsh scripting appears to be the only one option to create Xen PV Guests manageable via virt-manager. Notice, that F12 PV Guest install doesn’t require HTTP or NFS share , pygrub performs install just via F12 ISO image , like OpenSolaris PV Guests get installed as usual.

Install Libvirt 0.7.0 along with KVM creates environment with default Hypervisor QEMU . Two steps in procedure bellow makes Xen default Hypervisor on Ubuntu 9.10 .

Setup bellow might seem strange unless you will become aware of some ongoing issues with VNC-Console behavior during virt-install running on the most recent OSOL build 130. View recent threads at xen-discuss forum@opensolaris.org

Following bellow is step by step instruction how to clone Sun's xvm 3.4.2 repository and build packages , required to setup xVM 3.4.2 Dom0 on top of OpenSolaris 1002-128a. View also manuals at opensolaris.org How to Build the Development gates

Set up Sun xVM 3.4.2 on top of opensolaris 1002-128a via binary packages been built by Pascal Gienger at Index of /software/xvm/3.4.2. Been performing testing bellow my major concern was ability Sun xVM 3.4.2 to handle PV DomUs with boot file systems of ext4fs type. Actually, two guests have been tested : F12 and Ubuntu Karmic Server, in both cases boot partition has been converted to ext3fs to create DomUs manageable via virsh ( virt-manager).