[Bug 720558] Re: Ubuntu 10.04 currently requires groot= workaround with pvgrub
Launchpad Bug Tracker
720558 at bugs.launchpad.net
Fri Sep 23 16:20:26 UTC 2011
** Branch linked: lp:~ubuntu-core-dev/grub/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub in Ubuntu.
https://bugs.launchpad.net/bugs/720558
Title:
Ubuntu 10.04 currently requires groot= workaround with pvgrub
Status in “grub” package in Ubuntu:
Triaged
Status in “grub-installer” package in Ubuntu:
Invalid
Status in “grub” source package in Lucid:
Triaged
Status in “grub-installer” source package in Lucid:
Invalid
Status in “grub” source package in Maverick:
Triaged
Status in “grub-installer” source package in Maverick:
Invalid
Status in “grub” source package in Natty:
Triaged
Status in “grub-installer” source package in Natty:
Invalid
Bug description:
Binary package hint: debian-installer
Forwarded from a kind source outside; this was found and documented
(for their customers) by a Xen-based hosting company:
Ubuntu 10.04 LTS does not install out-of-the-box with default settings
on (virtual) machine requiring pvgrub and it is necessary to manually
adjust the 'groot=' setting in order to get the machine to boot. Viz;
"Ubuntu 10.04 LTS is now on the install menu (well, it has been for some
time), however the bootloader install which works seamlessly on debian
fails under Ubuntu, the following is what you need during the install to
make it a bootable system:
=========
Ubuntu by default with guided partitioning uses ext4,
which pvgrub won't understand, so don't choose "Guided -
use entire disk", but choose "Guided - use entire disk
and set up LVM", as this will make an ext2 /boot partition.
Ubuntu will give a grub error when installing, you need to
use the following workaround during the installation:
When you get the grub error, choose continue, continue, execute a shell,
continue
chroot /target
update-grub -y
sed -i.orig 's:^# groot=.*:# groot=(hd0,0):' /boot/grub/menu.lst
update-grub
exit
exit
Continue without bootloader
=========
Some further information received:
<..> sladen: the more root cause is grub installer not populating device.map
<..> sladen: it doesn't seem to get bios devices for xvda devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/720558/+subscriptions
More information about the foundations-bugs
mailing list