Showing headlines posted by dba477

Actually, CS 19889 is in Xen 3.5 Unstable. However, attempt to install mentioned DomU at Xen 3.5 Dom0 via standard pygrub profile aborts with message cannot find kernel “/boot/platform/i86xpv/kernel/amd64/unix”. Setup bellow has been tested with 2.6.30.1 xenified (aka Suse) kernel and 2.6.31-rc1 pvops enabled kernel been built via rebase/master branch of Jeremy Fitzhardinge git repository. The root cause of the problem is ZFS v.16 utilized by SNV_117 DomU for it’s image device unsupported by Xen 3.4.1.

To build 2.6.30.1 xenified kernel via Andrew Lyon’s 2.6.30 patch set in it’s current state download patch set. Per Jan Beulich:- The fix is to change the dependency from CONFIG_SPARSE_IRQ to CONFIG_GENERIC_HARDIRQS in the 2.6.30 patch.

Udev removed the udevinfo symlink from versions higher than 123 and xens build-system could not detect if udev is in place and has the required version. In particular, Ubuntu 9.04 server has udev version 141 and appears to be affected by this issue. Straight forward Xen 3.4.1 build brings up Xen Host with hotplug scripts rejecting to work. The recent patch suggested by Marc resolves this problem.

The most impressive F11 Xen related features seem to be the nice Xen 3.4.1 build with python 2.6 coming as default with F11 and graphical installer behavior during pygrub based PV DomU installation phase. F11 is supposed to be installed without libvirt to avoid conflict during Xen 3.4.1 port to Fedora 11 instance.

Gitco is providing http://www.gitco.de/repo/src/xen-3.3.1-0.src.rpm for free download. It gives am immediate option to back port Pygrub ZFS support from Xen 3.4-testing mercurial tree. Details follow bellow.

Pygrub ZFS support for the most recent Sun Solaris Nevada and OpenSolaris images has been introduced into Xen 3.4 via change sets 19323,19322, what makes OpenSolaris 2009.06 PV DomU install pretty much straight forward vs it happened under Xen 3.3.1 Hypervisor.

The most recent 2.6.30-rc6-tip pvops enabled kernel now supports HVM DomUs, what allows to reproduce known approach for building Intrepid and Jaunty Server PV DomUs via previously created HVM images to avoid traditional but a bit complicated debootstrap procedure. CentOS 5.3, Ubuntu Jaunty Server HVM have been successfully tested after the most recent kernel upgrade.

Have Ubuntu Intrepid Server dual boot with Jaunty just to perform Xen build properly and remove afterwards . It’s needed due to issues with python setup on Ubuntu Jaunty Server. We would build Xen 3.4 from source on Ubuntu 8.10 server and perform install via “make dist and install.sh to remote instance”. I believe procedure bellow will run same way with Ubuntu Jaunty root file system mounted as NFS share on Intrepid Server.

Fedora 11 Xen hypervisor package contains pv_ops dom0 kernel support, ie. it is able to boot bzImage format dom0 kernels, and pv_ops sysfs memory ballooning support is included as well. These features/patches are backported from Xen 3.4 development/unstable version to Fedora’s Xen 3.3.x. Our current target is to add two more change sets from Xen Unstable as patches to F11 xen-3.3.1-11.fc11.src.rpm to provide Xen 3.3.1 Dom0 support for OpenSolaris and Nevada PV Guests with images utilizing the most recent Sun ZFS

Fedora 11 Xen hypervisor package contains pv_ops dom0 kernel support, ie. it is able to boot bzImage format dom0 kernels, and pv_ops sysfs memory ballooning support is included as well. These features/patches are backported from Xen 3.4 development/unstable version to Fedora’s Xen 3.3.1. Xen-3.3.1-11.fc11.src.rpm may be rebuilt on F10 with the most recent updates installed. Obtained set of RPMS allow to install Xen 3.3.1 Hypervisor on F10,having same features as on F11, what was, actually, already done by Michael Young and Pasi Kärkkäinen.

To activate this nice new feature on Ubuntu Jaunty Server PV Domu installed at Xen 3.4 Dom0 with pvops enabled kernel i still had to activate traditional VNC to get access to Gnome Destop menu option ...

In general, Xen porting goes as usual . However, attempt to create initial ramdisk for 2.6.18.8-xen kernel fails due to known bug for mkinitrd in RHEL 5.3. Undocumented option <--allow-missing> provides a workaround to succeed with mkinitrd for xen-inified kernel. To port Xen 3.4-rc3-pre to xen disabled CentOS 5.3 instance (64 bit) install the most recent version of git and mercurial (hg).

This posting follows up recent discussion at xen-users mailing list regarding functionality of virt-install and virt-manager after Gitco’s Xen 3.3.1 Hypervisor Upgrade on CentOS 5.3(2). Via the posting bellow i try to demonstrate that Gitco’s upgrade of libvirt-python, python-virtinst,qemu packages and Xen Hypervisor itself seems to be a nice job with no serious issues keeping libvirt and virt-install (virt-manager) utility pretty stable at runtime. I also state that suggestion of use xen-tools & rinse on Xen Systems with libvirt abilities doesn’t look to me right way to manage vs utilizing debootstrap on Debian and Ubuntu Xen hosts, providing libvirt for the KVM only.

Posting bellow describes building Xen Unstable Dom0 with 2.6.29-tip pvops enabled kernel on top Ubuntu Intrepid Server (64-bit) with VNC setup for remote access via Gnome Desktop to Dom0. Fedora 10,CentOS 5.2, Solaris Nevada (b106), opensolaris 2008.11 PV DomUs have been successfully tested to run VNC sessions initiated via gnome terminals running at remote Dom0 desktop.

The most recent changes to Xen Unstable now allow to load Solaris Nevada and opensolaris 2008.11 PV DomUs with ZFS image via pygrub. Actually, Xen Unstable Dom0 with Suse’s 2.6.27 xen-ified kernel or standard 2.6.18 kernel will behave the same way.Moreover, install xen-ified kernel seems to be a preferable option due to 2.6.29-rc7 is under heavy development in meantime. My choice of pvops kernel for Dom0 is targeting test purposes first of all.

Due to recent migration Mercurial Repository for XenParavirtOps to Git Repository at kernel.org procedure of obtaining source code from from the Net has been changed. Base platform to start the test was Ubuntu Intrepid Server (64-bit) with Ubuntu Desktop installed via tasksel. Packages required by installation procedure have been installed: openssl,x11(xorg-dev),gettext,python-devel,gitk,git-core.

This posting is targeting install stubdom binaries at Xen-Unstable Dom0 with pv_ops enabled kernel and testing pv-grub and virtual frame buffer functionality in mentioned environment. Setup VNC at Dom0 exactly as on Ubuntu Intrepid Server with Ubuntu Desktop installed via “tasksel” to manage Dom0 remotely via Gnome Desktop interface.

Seems like 2.6.29 will be the first vanilla kernel supporting “pv_ops” in Dom0. Base platform to start the test was Ubuntu Intrepid Server (64-bit) with Ubuntu Desktop installed via tasksel. Packages required by Xen have been installed: openssl,x11,gettext,python-devel.

The root cause for port mentioned above to run 64-bit Solaris 10U6 HVM on SMP box with several vcpus. Install openssl,x11,gettext,python-devel packages required by Xen and bcc&libc6-dev-i386 via Synaptic Manager.The last two packages are needed to compile “hvmloader” and related binaries.

My experience with F10 PV DomU installs via profiles,described in details at recent post Xen 3.3.1rc1-pre port to CentOS 5.2 via http://bits.xensource.com mercurial repos and managing PV DomUs in graphical mode was negative, in regards of not providing an option to utilize local HTTP Mirror (NFS Share).Installer above just activated Xen Ethernet Interface at DomU and with no prompts addressed to Fedora's Internet Repositories,