This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] pvgrub doesn't read grub-config

Am Mittwoch, den 04.08.2010, 22:28 +0700 schrieb Fajar A. Nugraha:
> On Wed, Aug 4, 2010 at 9:42 PM, Tim Bordemann <t.bordemann@xxxxxx>
> wrote:
>         Unfortunalety the problem persists. There is no (visible)
>         change, I see
>         the grubdom again and the vm boots up after giving grub the
>         location of
>         the configfile.
>         Is there a logfile I haven't found yet which could help fixing
>         this?
> it should be visible as part of console output if you start it using
> "xm create -c". Something like this:
>                                        Xen Minimal OS!
>   start_info: 0xa9c000(VA)
>     nr_pages: 0x20000
>   shared_inf: 0xcfbfe000(MA)
> ...
> Thread "main": pointer: 0x2020002fb0, stack: 0xcd0000
> Thread "pcifront": pointer: 0x2020003760, stack: 0xce0000
> "main" "(hd0,0)/grub/menu.lst" 
> pcifront_watches: waiting for backend path to appear
> device/pci/0/backend
> vbd 51712 is hd0
> ******************* BLKFRONT for device/vbd/51712 **********
> from that snippet you see that on my setup pv-grub gets the
> parameter "(hd0,0)/grub/menu.lst", and vbd 51712 (which is xvda) is
> recognized as hd0. 

"main" "ip=:" "(hd1)/boot/grub/menu.lst" 
pcifront_watches: waiting for backend path to appear
vbd 51713 is hd0
******************* BLKFRONT for device/vbd/51713 **********

backend at /local/domain/0/backend/vbd/52/51713
Failed to read /local/domain/0/backend/vbd/52/51713/feature-flush-cache.
1048576 sectors of 512 bytes
vbd 51714 is hd1
******************* BLKFRONT for device/vbd/51714 **********

backend at /local/domain/0/backend/vbd/52/51714
Failed to read /local/domain/0/backend/vbd/52/51714/feature-flush-cache.
6291456 sectors of 512 bytes

Unfortunately nothing suspicious in there...
The odd thing is that the the grub-screen is showing up after manually
specifying the configfile ((hd1)/boot/grub/menu.lst) in grubdom. hd1
seems to be correct.


Xen-users mailing list