Pygrub at Xen 3.3.1 openSUSE 11.1 RC1 Dom0 (64-bit)

November 29, 2008

Install Xen Server package and booting Dom0 went pretty smoothly, however attempt to start vm-install either via YAST command center or from command line just brought up frozen blank window :-

blankwindow

So, we got a good chance one more time to demonstrate pygrub flexibility and power and reproduce samples from
Xen 3.3.1rc1-pre port to CentOS 5.2 via http://bits.xensource.com mercurial repos and managing PV DomUs in graphical mode
at Xen 3.3.1 openSUSE 11.1 RC1 Dom0.
CentOS 5.2 ,F9,F10 PV DomUs have been successfully installed via profiles mentioned at link above. Ubuntu Intrepid Server PV DomU has been installed as usual utilizing image created by HVM Intrepid Server install.

f9_5

intr5

Installation profile for CentOS 5.2 PV DomU:-

dhcppc0:/etc/xen/vm # cat rhel52.cfg
name="RHEL52PV"
memory=2048
disk = ['file:/etc/xen/isos/rhel52.iso,xvdb:cdrom,r','phy:/dev/sda11,xvda,w' ]
vif = [ 'bridge=br1', ]
vfb = [ 'type=vnc,vncunused=1' ]
bootloader = "/usr/bin/pygrub"
kernel = "/images/xen/vmlinuz"
ramdisk = "/images/xen/initrd.img"
vcpus=1
on_reboot = 'restart'
on_crash = 'restart'

rhl2

rhl6

Runtime profile :-

dhcppc0:/etc/xen/vm # cat rhel52.py
name="RHEL52PV"
memory=2048
disk = ['phy:/dev/sda11,xvda,w' ]
vif = [ 'bridge=br1', ]
vfb = [ 'type=vnc,vncunused=1' ]


rhl7

***********************
Update 12/01/2008
***********************
# zypper install python-gtk
makes a patch required by pthyton-gtk and allows to start vm-install on RC1


Xen 3.3.1rc1-pre port to CentOS 5.2 via http://bits.xensource.com mercurial repos and managing PV DomUs in graphical mode

November 17, 2008

Failure to virt-install F10 PV DomU and repeated issue with CentOS 5.2 in stub domain after same port via
http://gitco.de, upgrading only hypervisor to keep virt-install alive at Dom0, brought me to idea just go through traditional “hg” cloning mercurial repository at http://bits.xensource.com and build local Xen 3.3.1rc1 with 2.6.18.8-xen kernel. Actually, technology based on utilizing local Apache Mirrors along with pygrub profile,referencing installation versions of kernel ( either xenified or supporting pv_ops) and corresponding ramdisk, to create bootable PV DomU image followed by switching to another standard pygrub profile to load DomU with image, been already created, is flexible enough to cancel urgent need in virt-install. Installation PV DomUs for Ubuntu and Debian doesn’t need virt-install as well. Stub domains also work much more smoothly at Xen 3.3.1rc1-pre port to CentOS 5.2 mentioned in the header. In particular, i was able to install CentOS 5.2 in stubdom pretty fast and without any problems. I’ve tested CentOS 5.2 install as PV DomU and as stub domain (view [1],[2] for details) ,F9 PV DomU and openSUSE 11 install as PV DomU (view [3] for details). All mentioned above PV DomUs would be built up with graphical interface straight away.
*********************************************************************************************************************
To port Xen 3.3.1rc1-pre to xen disabled CentOS 5.2 instance (64 bit) install the most recent version of gitco and mercurial (hg).
**********************************************************************************************************************
# cd /usr/src/
# hg clone http://xenbits.xensource.com/xen-3.3-testing.hg
# cd xen-3.3-testing.hg
# make world
# make install
Determine the name of the Xen Linux kernel version that was installed.
# ls /lib/modules
There should be a directory for the Xen Linux kernel (e.g.2.6.18.8-xen)
Generate the module dependency list and map files
# /sbin/depmod 2.6.18.8-xen
Create the Xen initial ramdisk image
# /sbin/mkinitrd /boot/initrd-2.6.18.8-xen.img 2.6.18.8-xen
Disable tls
# mv /lib64/tls /lib64/tls.disabled
Set xend service to start
# /sbin/chkconfig –add xend
# /sbin/chkconfig xend on
Install bridge-utils:-
# yum install bridge-utils
************************************************************************
Edit /boot/grub/grub.conf and copy one of the existing boot entries
to make the required changes for Xen and reboot into new kernel.
*************************************************************************
title Xen-3.3.1 CentOS 5.2 x86_64 (2.6.18.8-xen) (/dev/sdb12)
root (hd1,11)
kernel /xen-3.3.gz
module /vmlinuz-2.6.18.8-xen ro root=/dev/VolGroup01/LogVol00 rhgb quiet
module /initrd-2.6.18.8-xen.img
**********************
Verify environment:-
**********************

[root@ServerRHL ~]# xm info
host : ServerRHL
release : 2.6.18.8-xen
version : #1 SMP Mon Nov 17 14:28:27 EST 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 3005
hw_caps : bfebfbff:20100800:00000000:00000140:0008e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8191
free_memory : 4058
node_to_cpu : node0:0-1
node_to_memory : node0:4058
xen_major : 3
xen_minor : 3
xen_extra : .1-rc1-pre
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Tue Nov 04 13:13:40 2008 +0000 18486:c05a663d3b24
cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Mon Nov 17 15:02:29 EST 2008
xend_config_format : 4
[root@ServerRHL ~]# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.001e8c25cca5 no peth0

****************************************************************************
1. CentOS 5.2 in stub domain (ballooning doesn’t seem to be working)
****************************************************************************
I had to run:-
# xm mem-set Domain-0 4000
to create and run stubdom , requiring 2 GB memory.

[root@ServerCentOS52 xen]# cat rhel52hvm-stubdom
kernel = “/usr/lib/xen/boot/hvmloader”
builder=’hvm’
memory = 2048
name = “rhel52hvm”
vif = [ 'type=ioemu, bridge=eth0' ]
device_model = ‘/usr/lib/xen/bin/stubdom-dm’
boot=”d”
sdl=0
opengl=0
vnc=0
stdvga=0
[root@ServerCentOS52 xen]# cat rhel52hvm-dm
kernel = “/usr/lib/xen/boot/ioemu-stubdom.gz”
vif = [ ' ', 'bridge=eth0']
vfb = [ 'type=vnc' ]
disk = ['file:/etc/xen/isos/rhel52.iso,hdc:cdrom,r','phy:/dev/sda8,hda,w']

Per Xen 3.3 Stubdom Release Notes run:-
# mkdir -p /exports/usr/share/xen/qemu
# ln -s /usr/share/xen/qemu/keymaps /exports/usr/share/xen/qemu
# mkdir -p /exports/var/lib
# ln -s /var/lib/xen /exports/var/lib
# /usr/sbin/fs-backend &
Switch from console to another terminal session :-

# xm create rhel52hvm-stubdom
# vncviewer localhost:0


stubdom1

stubdom2

2. CentOS 5.2 PV DomU installation and run time snapshots :-

rhlpv4

rhlpv5

3. OpenSuse 11 PV DomU run time snapshot:-

suse11pv1

4. Fedora 9 PV DomU installation procedure has been run via profile :-
name=”Fedora9PV”
memory=2048
disk = ['file:/mnt/etc/xen/isos/f9.iso,xvdb:cdrom,r',
'phy:/dev/sda11,xvda,w' ]
vif = [ 'bridge=eth0', ]
vfb = [ 'type=vnc,vncunused=1' ]
bootloader = “/usr/bin/pygrub”
kernel = “/images/xen/vmlinuz”
ramdisk = “/images/xen/initrd.img”
vcpus=1
on_reboot = ‘restart’
on_crash = ‘restart’
without any prompt for HTTP Mirror or NFS share

f9pv1

Run time profile

memory = 2048
name = “Fedora9PV”
bootloader=”/usr/bin/pygrub”
vif = [ 'bridge=eth0' ]
vfb = [ 'type=vnc,vncunused=1' ]
disk = [ 'phy:/dev/sda11,xvda,w']

f9pv2

Same install at Xen 3.3.1rc1 (port via http://gitco.de) CentOS 5.2 Dom0 will prompt for either HTTP mirror or NFS shared directory with loop mounted ISO image.
Install Fedora 10 PV DomU via profile:-
[root@ServerRHL vm]# cat f10.cfg
name=”Fedora10PV”
memory=2048
disk = ['file:/etc/xen/isos/f10.iso,xvdb:cdrom,r',
'phy:/dev/sdb9,xvda,w' ]
vif = [ 'bridge=eth0', ]
vfb = [ 'type=vnc,vncunused=1' ]
bootloader = “/usr/bin/pygrub”
kernel = “/images/pxeboot/vmlinuz”
ramdisk = “/images/pxeboot/initrd.img”
vcpus=1
on_reboot = ‘restart’
on_crash = ‘restart’
referencing Preview version of DVD ISO, requested to bring VNIC in DHCP mode and went connected to the most recent version of Fedora’s Internet Repositories with no prompts options available. Installer switched to text mode and committed “Office and productivity” install in about 3 hr . VNC at DomU has been setup manually :-

f10startup

f10pvrun

f10sysinfo

References
1.Pygrub & install CentOS 5.2 PV DomU at Xen 3.2 Ubuntu Hardy Dom0 via local HTTP Server (all 64-bit)
2. Getting stubdom working on Xen 3.3 port via http://www.gitco.de/repo/xen3.3.0 to CentOS 5.2
3.Install OpenSuse 11 PV DomU at Xen 3.2 Ubuntu Hardy Dom0 via local HTTP Server (all 64-bit)


Pygrub&Loading Fedora 10 PV DomU at Xen 3.3 Ubuntu Hardy Dom0 (all 64 bit)

November 15, 2008

1.To create loadable Fedora 10 PV image we would have to manage at Xen 3.3 CentOS 5.2 Dom0 either multibooting with Hardy Dom0 or remote , then several “dd” conversions might be required due to “scp” step. To install Fedora 10 PV DomU local NFS share will be utilized. Local Apache Server simulating HTTP mirror may be used as well. Installer provides both options. Attempts to perform install on Ubuntu Hardy Dom0 failed. Looks like Hardy has problems with the most recent Fedora’s file system. ISO image mounted via losetup doesn’t work correct versus it happens on CentOS 5.2.
2. Another approach may be to install F10 HVM DomU at Xen 3.3 Hardy Dom0 and proceed exactly the same way as in case of Ubuntu Intrepid Server. Installed image would have kernel ready to support pv_ops and provide opportunity to load created image via pygrub, e.g. the way to go seems to be an exact reproducing schema been utilized to for Ubuntu Intrepid Server PV DomU install.
However, testing second option i’ve got following error at PV DomU boot up.

failure

Consider first option.
Installation profile :-
[root@ServerCentOS52 vm]# cat f10.cfg
name=”F10PV”
memory=2048
disk = ['file:/etc/xen/isos/f10.iso,xvdb:cdrom,r',
'phy:/dev/sda9,xvda,w' ]
vif = [ 'bridge=eth0', ]
vfb = [ 'type=vnc,vncunused=1' ]
bootloader = “/usr/bin/pygrub”
kernel = “/images/pxeboot/vmlinuz”
ramdisk = “/images/pxeboot/initrd.img”
vcpus=1
on_reboot = ‘restart’
on_crash = ‘restart’

# xm create f10.cfg
# vncviewer localhost:0


f10_1

f10_2

f10_3

f10_6

Runtime profile will be the same at both CentOS 5.2 and Ubuntu Hardy Dom0s ( Xen 3.3 Hypervisor)
root@boris-desktop:/etc/xen/vm# cat f10.py
memory = 2048
name = “Fedora10PV”
bootloader=”/usr/bin/pygrub”
vif = [ 'bridge=eth0' ]
vfb = [ 'type=vnc,vncunused=1' ]
disk = [ 'phy:/dev/sda9,xvda,w!']

# xm create f10.py
# vncviewer localhost:0


f101

f102

f103

f104


Backport Intrepid Xen 3.3 Hypervisor to Ubuntu Hardy Dom0 (2.6.24-21-xen)

November 13, 2008

As of November 11 Intrepid Xen 3.3 Hypervisor may be back ported to Hardy Dom0 via repositories.
Following bellow is a brief instruction for installation from scratch Ubuntu Hardy Dom0 with 2.6.24-21-xen kernel
running with Xen 3.3 hypervisor. Install Ubuntu 8.04.1 Desktop and remove network manager :-
# apt-get remove network-manager
# gedit /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

# /etc/init.d/networking restart
# apt-get install ubuntu-xen-server

When done activate backports in /etc/apt/sources.list and load Synaptic Manager.
Mark for installation ;-

libxen3-dev
xen-doc-3.3
xen-hypervisor-3.3
xen-utils-3.3

and accept suggested conflict resolution.

u4

Go through install and reboot with Xen 3.3 Hypervisor :-

root@boris-desktop:~# xm info
host : boris-desktop
release : 2.6.24-21-xen
version : #1 SMP Wed Oct 22 01:07:57 UTC 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2400
hw_caps : bfebfbff:20100800:00000000:00000140:0000e3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 4095
free_memory : 36
node_to_cpu : node0:0-1
node_to_memory : node0:36
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
cc_compile_by : buildd
cc_compile_domain : buildd
cc_compile_date : Wed Oct 29 23:39:07 UTC 2008
xend_config_format : 4
root@boris-desktop:~# brctl show
bridge name bridge id STP enabled interfaces
eth1 8000.000c76e01ec5 no peth1
vif5.0

Perform the test. Create Intrepid HVM DomU via profile :-
root@boris-desktop:/etc/xen/vm# cat *.hvm
kernel = “/usr/lib/xen/boot/hvmloader”
builder = ‘hvm’
memory = 2048
name = “IntrepidHVM”
vcpus = 1
vif = [ 'type=ioemu,bridge=eth1' ]
disk = [ 'phy:/dev/sdb5,hda,w!','phy:/dev/loop0,hdc:cdrom,r']
device_model = ‘/usr/lib/xen/bin/qemu-dm’
vnc=1
boot=’d’

To evaluate hypervisor load Interpid PV DomU utilizing same image device :-

root@boris-desktop:/etc/xen/vm# cat *.py
name = ‘IntrepidPV’
bootloader=”/usr/bin/pygrub”
memory = 2048
disk = ['phy:/dev/sdb5,hda,w']
vif = [ 'bridge=eth1' ]
vfb = ['type=vnc,vncunused=1']
on_reboot = ‘restart’
on_crash = ‘restart’

# xm create intrepid.py
# vncviewer localhost:0

pvrun1

pvrun2

References.

http://deshantm.livejournal.com/29959.html


OpenSuse 11.1 PV DomU at Xen 3.3 Ubuntu Hardy Dom0 (all 64-bit)

November 8, 2008

Release been tested as PV DomU was Beta 4. Xen’s 3.3 pygrub loads DomU via image created during install utilizing local HTTP source with no problems , compare with native Xen 3.2 Hypervisor behavior on Ubuntu Hardy Dom0 ([1]). Same procedure obviously works at Xen 3.3 CentOS 5.2 Dom0. Due to
failure install Beta 4 in Dom0 (bug submitted) names of xenified kernel and ramdisk are unknown up on image creation, even though it doesn’t cause any problem in case Xen 3.3 Hypervisor back ported from Intrepid Release.
Setup Apache at Ubuntu Hardy Dom0.
# apt-get install apache2
# losetup /dev/loop0 /etc/xen/isos/suse11.1.iso
# mkdir -p /var/www/suse
# mount -o loop /etc//xen/isos/suse11.1.iso /var/www/suse
***********************
Installation profile :-
***********************
root@boris-desktop:/etc/xen/vm# cat suse11.1.cfg
name=”OpenSuse11.1PV”
memory=2048
disk = ['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/sda10,hda,w' ]
vif = [ 'mac=00:16:3e:4a:f5:00, bridge=eth0', ]
vfb = [ 'type=vnc,vncunused=1' ]
bootloader = “/usr/bin/pygrub”
kernel = “/boot/x86_64/vmlinuz-xen”
ramdisk = “/boot/x86_64/initrd-xen”
vcpus=1
on_reboot = ‘restart’
on_crash = ‘restart’
**************
Start install:-
*************
# xm create suse11.1.cfg
# vncviewer localhost:0

suse114

********************************************
Final configuration and runtime profile
********************************************
memory = 2048
name = “openSUSE11.1PV”
bootloader=”/usr/bin/pygrub”
vif = [ 'bridge=eth0' ]
vfb = [ 'type=vnc,vncunused=1' ]
disk = [ 'phy:/dev/sda10,hda,w!']
# xm create suse11.1.load
# vncviewer localhost:0

suse115

suse116

References.
1. Install OpenSuse 11 PV DomU at Xen 3.2 Ubuntu Hardy Dom0 via local HTTP Server (all 64-bit)


Attempt of prevu Intrepid Xen 3.3 Hypervisor at Ubuntu Hardy Dom0 (2.6.24-21-xen)

November 3, 2008

Quote:-
This is potentially a more time consuming backport but with Xen 3.3 being a huge improvement over 3.2 it would definitely help Ubuntu server market share to have Xen 3.3 available in Ubuntu 8.04. Many server operators will want Xen 3.3 but will want to continue running the LTS release rather than upgrade to Intrepid.
Current status of backports per Scott Kitterman :-
Because xen-3.3 is a new package for Hardy and so it needs a manual review by the archive admins. This is normal.

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1

shows the status. It won’t be available until it no longer says ‘NEW’ in the builds section.
Proceed with “prevu” build to evaluate Intrepid Xen 3.3 Hypervisor at Hardy Dom0.

# apt-get install prevu
# DISTRO=hardy prevu-init
# wget \

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0-1ubuntu7~hardy1.diff.gz

# wget \

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0.orig.tar.gz

# wget \

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0-1ubuntu7~hardy1.dsc

Now build :-

# /usr/bin/prevu xen-3.3_3.3.0-1ubuntu7~hardy1.dsc

. . . . . . . . . .
dh_builddeb -s
dpkg-deb --build debian/xen-hypervisor-3.3 ..
dpkg-deb: building package `xen-hypervisor-3.3' in `../xen-hypervisor-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/xen-utils-3.3 ..
dpkg-deb: building package `xen-utils-3.3' in `../xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/xen-docs-3.3 ..
dpkg-deb: building package `xen-docs-3.3' in `../xen-docs-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/libxen3-dev ..
dpkg-deb: building package `libxen3-dev' in `../libxen3-dev_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/libxen3 ..
dpkg-deb: building package `libxen3' in `../libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/python-xen-3.3 ..
dpkg-deb: building package `python-xen-3.3' in `../python-xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-genchanges >../xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.changes
dpkg-genchanges: including full source code in upload
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Copying back the cached apt archive contents
-> new cache content libexpat1_2.0.1-0ubuntu1_amd64.deb added
-> new cache content libsm6_2%3a1.0.3-1_amd64.deb added
-> new cache content python-all_2.5.2-0ubuntu1_all.deb added
. . . . . . .
-> unmounting /var/cache/prevu/src/22498 filesystem
-> unmounting /var/cache/prevu/hardy-debs filesystem
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /var/cache/prevu/builds/22589 and its subdirectories
** Success!. You can find source packages and .debs at /var/cache/prevu/hardy-debs **

Build successful, attempt to install :-

root@boris-desktop:/var/cache/prevu/hardy-debs# ls -l

total 2620
-rwxr--r-- 1 root root 357 2008-11-03 03:35 install.sh
-rw-r--r-- 1 root root 147070 2008-11-03 03:29 libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 236020 2008-11-03 03:29 libxen3-dev_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rwxrwxr-x 1 root admin 4565 2008-11-03 03:29 Packages
-rw-r--r-- 1 root root 879276 2008-11-03 03:29 python-xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 13022 2008-11-03 03:29 xen-docs-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 472354 2008-11-03 03:29 xen-hypervisor-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 890692 2008-11-03 03:29 xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb

root@boris-desktop:/var/cache/prevu/hardy-debs# ./install.sh

(Reading database ... 101659 files and directories currently installed.)
Preparing to replace libxen3 3.2.0-0ubuntu10 (using libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Unpacking replacement libxen3 ...
Selecting previously deselected package libxen3-dev.
Unpacking libxen3-dev (from libxen3-dev_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Selecting previously deselected package python-xen-3.3.
Unpacking python-xen-3.3 (from python-xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Replacing files in old package python-xen-3.2 ...
Selecting previously deselected package xen-docs-3.3.
Unpacking xen-docs-3.3 (from xen-docs-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-hypervisor-3.3.
Unpacking xen-hypervisor-3.3 (from xen-hypervisor-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-utils-3.3.
dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
xen-utils-3.3 conflicts with xen-utils
xen-utils-3.2 provides xen-utils and is installed.
dpkg: error processing xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb (--install):
conflicting packages - not installing xen-utils-3.3
Setting up libxen3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up libxen3-dev (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up python-xen-3.3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up xen-docs-3.3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up xen-hypervisor-3.3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found Xen hypervisor 3.2, kernel: /boot/vmlinuz-2.6.24-21-xen
Found Xen hypervisor 3.3, kernel: /boot/vmlinuz-2.6.24-21-xen
Found kernel: /boot/vmlinuz-2.6.24-19-generic
Found kernel: /boot/memtest86+.bin
Replacing config file /var/run/grub/menu.lst with new version
Updating /boot/grub/menu.lst ... done
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb

I’ve tried to work with old package and force replacement as follows :-
root@boris-desktop:/var/cache/prevu/hardy-debs# dpkg -i –force-all xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
xen-utils-3.3 conflicts with xen-utils
xen-utils-3.2 provides xen-utils and is installed.
dpkg: warning – ignoring conflict, may proceed anyway !
dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
xen-utils-3.2 conflicts with xen-utils
xen-utils-3.3 provides xen-utils and is to be installed.
dpkg: warning – ignoring conflict, may proceed anyway !
. . . .
To get HVM able obtain IP address via bridge i had to use vif = ['bridge=eth0'] in
profiles like :-
root@boris-desktop:/etc/xen/vm# cat intrepid.hvm
kernel = “/usr/lib/xen/boot/hvmloader”
builder = ‘hvm’
memory = 1024
name = “IntrepidHVM”
vcpus = 1
vif = [ 'bridge=eth0' ]
disk = [ 'phy:/dev/sdb14,hda,w!','phy:/dev/loop0,hdc:cdrom,r' ]
device_model = ‘/usr/lib/xen/bin/qemu-dm’
vnc=1
boot=’c’
Turning virtual NIC into a paravirtualized mode instead of a fully virtualized.
When vif=['type=ioemu,bridge=eth0'] HVM fails to bring up virtual network interface.
******************
Rebooted into:-
******************
title Xen 3.3 / Ubuntu 8.04.1, kernel 2.6.24-21-xen
root (hd0,11)
kernel /boot/xen-3.3.gz
module /boot/vmlinuz-2.6.24-21-xen root=UUID=4d4bfbb3-68bd-49b4-ace3-af3d17c8612b ro console=tty0
module /boot/initrd.img-2.6.24-21-xen
quiet
*******************
System status :-
*******************
root@boris-desktop:/etc/xen/vm# xm info
host : boris-desktop
release : 2.6.24-21-xen
version : #1 SMP Mon Aug 25 18:56:44 UTC 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 3005
hw_caps : bfebfbff:20100800:00000000:00000140:0008e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8191
free_memory : 34
node_to_cpu : node0:0-1
node_to_memory : node0:34
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Mon Nov 3 08:25:32 UTC 2008
xend_config_format : 4
root@boris-desktop:/etc/xen/vm# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.001e8c25cca5 no peth0
vif6.0
vnet0 8000.000000000000 yes
********************************************
Create Intrepid Server HVM DomU via :-
********************************************
root@boris-desktop:/etc/xen/vm# cat intrepid.hvm
kernel = “/usr/lib/xen/boot/hvmloader”
builder = ‘hvm’
memory = 2048
name = “IntrepidHVM”
vcpus = 1
vif = [ 'bridge=eth0' ]
disk = [ 'phy:/dev/sdb14,hda,w!','phy:/dev/loop0,hdc:cdrom,r' ]
device_model = ‘/usr/lib/xen/bin/qemu-dm’
vnc=1
boot=’d’
*****************************************************************************************************************
The first time am image for PV DomU will be created, you won’t find active Ethernet interface at HVM
DomU. However, install “Ubuntu Desktop” via tasksel at PV DomU will make it completely functional
to manage Intrepid Server HVM DomU. Seems like PV drivers for virtual NIC get installed on the
image device via tasksel’s procedure.
******************************************************************************************************************
Load Intrepid Server PV DomU via :-
root@boris-desktop:/etc/xen/vm# cat intrepid.py
name = ‘IntrepidPV’
bootloader=”/usr/bin/pygrub”
memory = ’2048′
disk = ['phy:/dev/sdb14,xvda,w']
vif = [ 'mac=00:16:3e:00:00:00' ]
vfb = ['type=vnc,vncunused=1']
on_reboot = ‘restart’
on_crash = ‘restart’
# xm create intrepid.py
# vncviewer localhost:0
***************************
Check Intrepid PV DomU
***************************
root@boris-desktop:/etc/xen/vm# xm list -l IntrepidPV
(domain
(domid 6)
(on_crash restart)
(uuid a156eaf7-6375-f720-5a4a-03f376167b71)
(bootloader_args -q)
(vcpus 1)
(name IntrepidPV)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 2048)
(memory 2048)
(shadow_memory 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1225704559.32)
(cpu_time 4.715455935)
(online_vcpus 1)
(image
(linux
(kernel )
(device_model /usr/lib64/xen/bin/qemu-dm)
(notes
(HV_START_LOW 18446603336221196288)
(FEATURES ‘!writable_page_tables|pae_pgdir_above_4gb’)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 0)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564201984)
(LOADER generic)
(SUSPEND_CANCEL 1)
(PAE_MODE yes)
(ENTRY 18446744071569531392)
(XEN_VERSION xen-3.0)
)
)
)
(status 2)
(state -b—-)
(store_mfn 2208645)
(console_mfn 2208644)
(device
(vif
(mac 00:16:3e:00:00:00)
(script vif-bridge)
(uuid 768ba10b-4fec-2342-c49c-9aa05c62c7ca)
(backend 0)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 71ecda50-1039-4ef9-bf6e-17ef01964dee)
(dev xvda:disk)
(uname phy:/dev/sdb14)
(mode w)
(backend 0)
(bootable 1)
(VDI )
)
)
(device (vkbd (backend 0)))
(device
(vfb
(vncunused 1)
(uuid 017e4530-8d38-19aa-3d3c-ebf6832e7575)
(location localhost:5900)
(type vnc)
(display :0.0)
(xauthority /root/.Xauthority)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid d2851099-a26b-c84f-4bb1-091ba6eab1e3)
)
)
)





Run tasksel to install Ubuntu Desktop at PV DomU



Setup VNC at PV DomU and login via vncviewer from Dom0:-

vnclogin





Now we can also load Intrepid Server HVM DomU with PV driver for virtual NIC.

startintrepidhvm

Solaris Nevada (build 101) has been installed in DHCP mode as PV DomU via profile :-
root@boris-desktop:/etc/xen/vm# cat snv101.py
name = ‘SolarisPVM’
memory = ’1024′
disk = [ 'phy:/dev/loop1,6:cdrom,r', 'phy:/dev/sdb13,0,w!' ]
vif = [ 'bridge=eth0' ]
bootloader = ‘/usr/bin/pygrub’
kernel = ‘/boot/platform/i86xpv/kernel/amd64/unix’
ramdisk = ‘/boot/amd64/x86.miniroot’
extra = ‘/platform/i86xpv/kernel/amd64/unix – nowin -B install_media=cdrom’
Installation succeeded.
**********************************
Start up SNV_101 PV DomU
**********************************
root@boris-desktop:/etc/xen/vm# uname -a
Linux boris-desktop 2.6.24-21-xen #1 SMP Mon Aug 25 18:56:44 UTC 2008 x86_64 GNU/Linux
root@boris-desktop:/etc/xen/vm# xm info|grep xen_
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
xen_changeset : unavailable
root@boris-desktop:/etc/xen/vm# xm create -c snv101.pyrun
Using config file “./snv101.pyrun”.
Started domain SolarisPVM
v3.3.0 chgset ‘unavailable’
SunOS Release 5.11 Version snv_101 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: dhcppc7
/dev/rdsk/c0d0s7 is clean
Reading ZFS config: done.
syslogd: line 45: WARNING: loghost could not be resolved

dhcppc7 console login: root
Password:
Last login: Mon Nov 3 14:46:59 on console
Nov 3 14:51:56 dhcppc7 login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 snv_101 November 2008
# bash
bash-3.2# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
xnf0: flags=201004843 mtu 1500 index 2
inet 192.168.1.40 netmask ffffff00 broadcast 192.168.1.255
ether 0:16:3e:63:46:96
lo0: flags=2002000849 mtu 8252 index 1
inet6 ::1/128
bash-3.2# nslookup lxer.com
Server: 80.254.111.254
Address: 80.254.111.254#53

Non-authoritative answer:
Name: lxer.com
Address: 207.210.216.38
bash-3.2#




*******************
Update 12/11/08
*******************
Please be advised , as of November 11 Hardy Backports provide Xen 3.3 packages .
They may be installed nicely via Synaptic Manager.

synaptic1

synaptic2

synaptic3


Follow

Get every new post delivered to your Inbox.