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

[Daniel Pocock]

>> 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.
>
>   

Agreed - same bug.  I have also seen the hvmloader issue on another test 
system, putting the full path fixes it for me.

>> 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?
>   
No, it's a dom0 issue
> 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.
>   
grub installed fine in the domU

My only other concern with the domU is that it has partitioned an LVM 
volume, and grub installed to the MBR.  That makes it more awkward to 
mount the LVM volume from dom0 (although not impossible).  Should I have 
used

disk = ['phy:vg00/th2_root,xvda1,w']

instead of

disk = ['phy:vg00/th2_root,xvda,w']  ?

Would the grub install work with the latter approach?

Is there any `best practice' about LVM and partition tables within LVs, 
particularly when used with Xen?  I've also worked with LVs over SRP, 
and encountered a similar dilemma, as the LV shows up on the initiator 
as a /dev/sdX device.

Regards,

Daniel