Hi,
I''m trying to use pvgrub with some existing guests. It seems to me that
pygrub doesn''t read the guest''s grub-config.
Here are my config files:
# /etc/xen/testmigration.cfg
############################
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd1)/boot/grub/menu.lst"
memory = ''256''
vcpus = ''1''
disk = [ ''phy:/dev/vg0/testmigration-disk,xvda2,w'',
''phy:/dev/vg0/testmigration-swap,xvda1,w'',
]
name = ''testmigration''
dhcp = ''dhcp''
vif = [ ''mac=XX:XX:XX:XX:XX:XX'' ]
# /boot/grub/menu.lst
#####################
default 0
timeout 5
title Ubuntu 8.04.4 LTS, kernel 2.6.24-26-xen
root (hd1)
kernel /boot/vmlinuz-2.6.24-26-xen root=/dev/xvda2 ro
initrd /boot/initrd.img-2.6.24-26-xen
After creating the VM I always get to the grubdom commandline. When I
type in "configfile (hd1)/boot/grub/menu.lst" (exactly the same as the
extra line in the VM''s configfile), the machine starts to boot.
Am I missing anything?
Thanks,
Tim
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Aug 4, 2010 at 8:07 PM, Tim Bordemann <t.bordemann@web.de> wrote:> kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" > extra = "(hd1)/boot/grub/menu.lst" > disk = [ ''phy:/dev/vg0/testmigration-disk,xvda2,w'', > ''phy:/dev/vg0/testmigration-swap,xvda1,w'', > ] >> After creating the VM I always get to the grubdom commandline. When I > type in "configfile (hd1)/boot/grub/menu.lst" (exactly the same as the > extra line in the VM''s configfile), the machine starts to boot. > Am I missing anything? > >I have a suspicion that somehow your hd0 and hd1 got mixed up. What happens if you change the disk order? something like disk = [ ''phy:/dev/vg0/testmigration-swap,xvda1,w'', ''phy:/dev/vg0/testmigration-disk,xvda2,w'', ] -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Mittwoch, den 04.08.2010, 21:29 +0700 schrieb Fajar A. Nugraha:> On Wed, Aug 4, 2010 at 8:07 PM, Tim Bordemann <t.bordemann@web.de> > wrote: > kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" > extra = "(hd1)/boot/grub/menu.lst" > disk = [ ''phy:/dev/vg0/testmigration-disk,xvda2,w'', > ''phy:/dev/vg0/testmigration-swap,xvda1,w'', > ] > > After creating the VM I always get to the grubdom commandline. > When I > type in "configfile (hd1)/boot/grub/menu.lst" (exactly the > same as the > extra line in the VM''s configfile), the machine starts to > boot. > Am I missing anything? > > > > I have a suspicion that somehow your hd0 and hd1 got mixed up. What > happens if you change the disk order? something like > > > disk = [ > ''phy:/dev/vg0/testmigration-swap,xvda1,w'', > ''phy:/dev/vg0/testmigration-disk,xvda2,w'', > ]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? Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Aug 4, 2010 at 9:42 PM, Tim Bordemann <t.bordemann@web.de> 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. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@web.de> > 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=:127.0.255.255::::eth0:dhcp" "(hd1)/boot/grub/menu.lst" pcifront_watches: waiting for backend path to appear device/pci/0/backend 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. Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Aug 4, 2010 at 11:09 PM, Tim Bordemann <t.bordemann@web.de> wrote:> "main" "ip=:127.0.255.255::::eth0:dhcp" "(hd1)/boot/grub/menu.lst"where does that "ip" part comes from? You might want to try removing dhcp = ''dhcp'' line on your domU config. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Donnerstag, den 05.08.2010, 09:58 +0700 schrieb Fajar A. Nugraha:> On Wed, Aug 4, 2010 at 11:09 PM, Tim Bordemann <t.bordemann@web.de> wrote: > > "main" "ip=:127.0.255.255::::eth0:dhcp" "(hd1)/boot/grub/menu.lst" > > where does that "ip" part comes from? > You might want to try removing > > dhcp = ''dhcp'' > > line on your domU config. >You were right, after removing that line the vm is booting! Thank you, Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users