Pkg xen devel - Dec 2008 - pygrub and xm-debian.cfg, other notes on lenny test

I've just done a fresh lenny amd64 install, and taken the xm-debian.cfg 
example:

   
http://people.debian.org/~joeyh/d-i/images/daily/netboot/xen/xm-debian.cfg

and built a 32 bit lenny inside a 64 bit lenny dom0

  # xm create -c xm-th2.cfg install=true 
install-installer=http://people.debian.org/~joeyh/d-i/images/daily/

When I try to boot the domU:

  # xm create -c xm-debian.cfg

it complains:

Error: Bootloader isn't executable


I found that I had to edit xm-debian.cfg and insert the full bootloader 
path:

if not xm_vars.env.get('install'):
    bootloader="/usr/lib/xen-3.2-1/bin/pygrub"
else:
    import os.path
    print "Install Mirror: %s" % xm_vars.env['install-mirror']

Apart from this one issue, the process went smoothly.

The only other thing I chose to change was the disk configuration, I 
just did:

  # lvcreate  -L 4G -n domU_root volg0

and then I used this disk config line in xm-debian.cfg:

  disk = ['phy:volg0/domU_root,xvda,w']

One other issue I see, the kernel package is not cleanly installed, 
although this hasn't stopped me using it:

# apt-get -f install
Reading package lists... Done
Building dependency tree      
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up linux-image-2.6.26-1-xen-amd64 (2.6.26-11) ...
update-initramfs: Generating /boot/initrd.img-2.6.26-1-xen-amd64
Searching for GRUB installation directory ... found: /boot/grub
dpkg: error processing linux-image-2.6.26-1-xen-amd64 (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.26-1-xen-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

On Sat, 2008-12-20 at 14:44 +0000, Daniel Pocock wrote:
> 
> 
> I've just done a fresh lenny amd64 install, and taken the xm-debian.cfg
> example:
> 
>    
> http://people.debian.org/~joeyh/d-i/images/daily/netboot/xen/xm-debian.cfg
> 
> and built a 32 bit lenny inside a 64 bit lenny dom0
> 
>   # xm create -c xm-th2.cfg install=true 
> install-installer=http://people.debian.org/~joeyh/d-i/images/daily/
> 
> When I try to boot the domU:
> 
>   # xm create -c xm-debian.cfg
> 
> it complains:
> 
> Error: Bootloader isn't executable
> 
> 
> I found that I had to edit xm-debian.cfg and insert the full bootloader 
> path:
> 
> if not xm_vars.env.get('install'):
>     bootloader="/usr/lib/xen-3.2-1/bin/pygrub"
> else:
>     import os.path
>     print "Install Mirror: %s" %
xm_vars.env['install-mirror']
I think this is #481105.
> One other issue I see, the kernel package is not cleanly installed, 
> although this hasn't stopped me using it:
> 
> # apt-get -f install
> Reading package lists... Done
> Building dependency tree      
> Reading state information... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0B of additional disk space will be used.
> Setting up linux-image-2.6.26-1-xen-amd64 (2.6.26-11) ...
> update-initramfs: Generating /boot/initrd.img-2.6.26-1-xen-amd64
> Searching for GRUB installation directory ... found: /boot/grub
> dpkg: error processing linux-image-2.6.26-1-xen-amd64 (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  linux-image-2.6.26-1-xen-amd64
> E: Sub-process /usr/bin/dpkg returned an error code (1)
This is in your 32 bit guest installed via Debian Installer? That should
have installed the -686-bigmem kernel. There is no i386 arch package
providing an amd64 Xen kernel, where did it come from?

I guess update-grub is failing, can you run it by hand and see if it
produces any output, and then maybe run it again with "sh -x" to see
what goes wrong.

Ian.

-- 
Ian Campbell

I just got out of the hospital after a speed reading accident.
I hit a bookmark.
		-- Steven Wright
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url :
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20081220/398c32e8/attachment.pgp