I have two filesystem images that I built: root and /mnt and with a guest menu.lst that uses UUID I am able to create a running xen domain using either a normal 'xm' config or a 'pygrub' bootloader config.

I am unable to create a working config using 'pv-grub' however using UUID.

The guest menu.lst uses 'uuid' rather than 'root' and whenever I try to create the domain using 'pv-grub' it always drops me to a 'grubdom' prompt.  In grubdom if I just add a line 'root=/dev/xvda1' then it will boot fine.  I cannot test 'uuid' in grubdom because it does not recognize the 'uuid' command.

Here are details:

host: pv_ops dom0  kernel 2.6.32.13
guest: ubuntu  kernel 2.6.32-22-server

========================================
pv-grub configfile:
========================================
name = "test"

maxmem = 4096
memory = 1024
vcpus = 4

uuid = "b59e45e2-3137-4685-a31c-a8c87a65c4fc"
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd0)/boot/grub/menu.lst"

disk = [
  "tap:aio:/root/ubuntu-xen/root.img,xvda1,w",
  "tap:aio:/root/ubuntu-xen/____.img,xvdb,w"
 ]

vif = [ "mac=00:16:1a:2a:ef:56,bridge=br0" ]

on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"

========================================
guest /boot/grub/menu.lst:
========================================
default        0
timeout        3
hiddenmenu

title        Ubuntu 10.04 LTS, kernel 2.6.32-22-server
uuid        b59e45e2-3137-4685-a31c-a8c87a65c4fc
kernel        /boot/vmlinuz-2.6.32-22-server root=UUID=b59e45e2-3137-4685-a31c-a8c87a65c4fc ro console=hvc0 splash
initrd        /boot/initrd.img-2.6.32-22-server

title        Ubuntu 10.04 LTS, kernel 2.6.32-22-server (recovery mode)
uuid        b59e45e2-3137-4685-a31c-a8c87a65c4fc
kernel        /boot/vmlinuz-2.6.32-22-server root=UUID=b59e45e2-3137-4685-a31c-a8c87a65c4fc ro  single
initrd        /boot/initrd.img-2.6.32-22-server

========================================
tune2fs -l /dev/loop0  # root fs
========================================
tune2fs 1.41.11 (14-Mar-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          b59e45e2-3137-4685-a31c-a8c87a65c4fc
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              655360
Block count:              2621440
Reserved block count:     131072
Free blocks:              2413274
Free inodes:              632869
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      639
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Wed Jun 16 03:46:23 2010
Last mount time:          Wed Jun 16 13:15:24 2010
Last write time:          Wed Jun 16 13:15:24 2010
Mount count:              5
Maximum mount count:      31
Last checked:             Wed Jun 16 03:46:23 2010
Check interval:           15552000 (6 months)
Next check after:         Mon Dec 13 02:46:23 2010
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      afd06bb1-27d7-4921-a8fc-693df864acf5
Journal backup:           inode blocks

========================================
========================================

Can anyone see what is missing?  I thought UUID should work with pv-grub but it is failing for me.

-Gerry