Showing headlines posted by dba477

Blog entry "OpenSolaris 2008.11 guest domain on a Linux dom0" was written by John Levon and supposed to help community users to install OSOL 2008-11 DomU at Xen 3.1 Dom0 on top of Fedora 8. It’s core technique utilizes virsh , so is supposed to be applicable to current release of Libvirt as well. However , /usr/bin/xenstore-read fails to obtain IP address for OSOL DomU via XenStore at Xen 3.4.2 Dom0. Posting bellow fixes this issue and provide an option to build via virsh the most recent OSOL PV DomU at Xen 3.4.2 Dom0 & Libvirt 0.7.1-15 on Fedora 12.

We presume , that xen-3.4.1-5.fc12.src.rpm has been already installed on the system and Xen Host been built via mentioned “rpm” , Libvirt 0.7.1-15 and 2.6.31.6 pvops kernel is up and running at the time of upgrade. Apply following patch to /root/rpmbuild/SPECS/xen.spec

A brief description of Xen 3.4.1 and Libvirt 0.7.1-15 deployment to Fedora 12 follows bellow. Next step is install Ubuntu Karmic Koala Server in HVM DomU with ext4fs image via virt-install. Ubuntu Karmic PV DomU gets loaded via pygrub profile due to Xen Hypervisor has been built on F12 along with e2fsprogs-devel package, what allows to handle PV DomUs images (F12,Ubuntu 9.10) having ext4fs on boot partition.

Setup xvm per Sun the most recent instructions. As appears latter Virt-Manager is broken in 126 ( vs 124), but this is not the worst thing supposed to happen. Virt-install rejects to install Fedora12 PV DomU which is not yet in the dictionary in meantime. XML startup file for f12 allows to avoid this restriction mostly connected i believe with xVM version unable to handle ext4 FS for boot partition of Linux DomU

This application will use Java Server Faces 2.0 for displaying the results, Enterprise Java Beans 3.1 + Java Persistence API 2.0 for middle tier, and Oracle database server + GlassFish v3 as the backend. The most recent development bundle NetBeans 6.8 & GlassFish V3 build 68 would be good work for testing Download NetBeans IDE Build 200910170201

Posting bellow provides a workaround for failure of straight forward virt-install Debian Lenny 64-bit DomU via location http://ftp.us.debian.org/debian/dists/lenny/main/installer-a... . It doesn’t require debootstrap involvement and would work on OpenSolaris 2010-02-124 and Solaris Nevada 124 as well. Download mini installer iso image and virt-install Lenny HVM DomU

The most recent features of Jeremy Fitzhardinge kernel have been enabled and tested at Xen 3.5 Dom0 on top of Ubuntu Karmic Koala (Beta) Server. Xen host been built reboots directly into Gnome Desktop environment on the box with Core2Quad CPU, 8 GB RAM, Radeon HD 4X50 Video Card. Tuning kernel 2.6.31.1 described in details bellow with snapshots of every configuration step been taken. Deployment Xen Unstable to Ubuntu Karmic Server environment was done in same way as in [1] and is also briefly documented. Xen 3.5 Dom0 with 2.6.31.1 pvops kernel has been verified via F12 (rawhide) PV DomU install.

Brief description of Xen 3.4.1 and Libvirt 0.7.0-6 deployment to Fedora 12 Alpha (rawhide) follows bellow. F12 instance was created on the second drive. All my attempts to resize default LVM created by intaller caused installer to crash.

Due to GRUB2 doesn’t allow module entries to accept parameters via command line in meantime , creating corresponding Xen grub2 entries for xenified aka Suse kernels went a bit different from the same procedures on Jaunty and Intrepid Servers.

This post follows up Mark McLoughlin's ANNOUNCE: Rawhide virt repo for F11 users:- Another update available in http://markmc.fedorapeople.org/virt-preview It's targeting install the most recent version of Fedora's libvirt on F11 and testing virt-manager and virt-install to work properly with Xen 3.4.1 Hypervisor been installed on F11 via xen 3.4.1-1 src.rpm downloaded from http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/ PVOPS kernel 2.6.31-rc6 has been installed via Jeremy Fitzhardinge Git Repository to support Xen 3.4.1 Dom0.

PVOPS kernel been installed to run under Xen 3.4.1 was 2.6.31-rc5. To build Xen 3.4.1 Dom0 via Bug Attachments at Please merge xen-3.4 (3.4.0-2) from debian unstable installed "prevu" and performed build to obtain debian packages.

Regardless bug with failure checksum offloading was fixed in SNV_81 , i.e. a while ago. OpenSolaris 2009.06 PV DomU install at Xen 3.4.1 Linux Dom0 appears still to be affected. Wrong checksum may be easily captured via tcpdump on the LAN due to DHCPDISCOVER request issued by OSOL installer is a broadcast request. Following bellow procedure involves Solaris Kernel module debugger to patch OSOL’s (SNV_111b) kernel at booting up to succeed with dhcp lease and to be able proceed with initial install. File /etc/system gets updated via root terminal session before standard reboot to make the patch for kernel permanent. Posting is devoted first of all to Linux users , who are not aware of “kmdb” syntax and involving into boot process.

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.