Will be there also the version of the new GRUB package for amd64?

I have the error with the similar message, but I do not know, if it is the same problem, so I would like to try the new grub if it could have some influence... 

My problem is related to Xen - I get this error if booting the Xen over Ubuntu 7.04 server as Dom0. Maybe it could be also some problem of Xen, but the problem occurs first, if the boot of the Xen part is already done and the Ubunt boot runs. Below is my error description, whcih I posted to Xen users conference. 
Do You think, this can be the error of GRUB in Ubuntu, is it the same error like here described, or is it some other error or is it no problem of Ubuntu? Should I open the new thread here?
  Thank You, Archie.
*************************
Hello,

             I have problems with booting with the new Xen (used the binary tarball) v. 3.1.0.

I have installed following system:
One small raid partition with Ext3 fs with the boot directory and grub installed
Two large and one small mirrored raid1 partitions managed by mdadm and used as 3 physical volumes for LVM, all 3 joined into one volume group.
Planned dom0 system is installed on the logical volume, which is striped over md1 and md3 raid phzsical volumes. It is Ubuntu server 7.04.

The Ubuntu system self boots ad behaves normally.

If booting Xen, the boot process comes to the point where the raid arrays are beeing initialized. The RAID arrays itself are initialized and activated correctly. After it happens, the system hangs for some minutes and then the message comes:
 
Check root= bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 does not exist. Dropping to shell!

... and the sh is invoked, the tty cannot be accessed, so the job control is turned off.

I looked into /dev/mapper and really, thre is no VG_HIGHLAND_SYSTEM volume group, which appears there if booting the Ubuntu server.

I am not very skilled in the work with LVM, so the only thing what came into my mind  was - it looks like if the default binary tarball of Xen 3.1.0 has not turned on the LVM support in the kernel, but I think this is not possible, because LVM is normally used.

Or would it be the solution to configure and compile the xen kernel from source?

Does somebody some other idea, why the volume group is not recogized and cannot be found in /dev/mapper ? 
The logical partitions also are invisible in the result of cat /proc/partitions

                        Thank You very much in advance for any advice or help...

                                   With best regards, Archie
 
            P.S. In http://groups.google.cz/group/linux.debian.bugs.dist/browse_thread/thread/eafa7a66782c206e/630c5180caa580dd?lnk=st&q=ALERT!+%2Fdev%2Fmapper%2FVG+does+not+exist.+Dropping+to+shell!&rnum=1&hl=cs#630c5180caa580dd

I found the idea this is some error in GRUB script, but I do not know if it is my case - GRUB configuration file „menu.lst“ looks like:

title     Xen 3.1.0, kernel 2.6.18-xen /dev/sda1
root      (hd0,0)
kernel    /xen-3.1.0.gz dom0_mem=192M 
module    /vmlinuz-2.6.18-xen root=/dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 ro max_loop=255 console=tty0
module    /initrd.img-2.6.18-xen

and the working Ubuntu server boot-configuration looks like

title     Ubuntu 7.04 server, kernel 2.6.20-15-server /dev/sda1
root      (hd0,0)
kernel    /vmlinuz-2.6.20-15-server root=/dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 ro console=tty0
initrd    /initrd.img-2.6.20-15-server ro splash

Unfortunatelly I cannot get to the log because there is nothing written to the logfiles because the system partition cannot be mounted... etc.
*************************