Ubuntu 10.04 currently requires groot= workaround with pvgrub
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Lucid |
Fix Released
|
High
|
Colin Watson | ||
Maverick |
Fix Released
|
High
|
Colin Watson | ||
Natty |
Fix Released
|
High
|
Colin Watson | ||
grub-installer (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Stable update justification:
Impact: Part of a set of bugs rendering it impossible to install any Ubuntu release from Lucid onwards as a Xen guest using d-i. (The others are bug 857548 and bug 857662, which affect only Natty and Oneiric.)
Development branch: Fixed in grub 0.97-29ubuntu63 in Oneiric.
Patch: http://
TEST CASE: Install in a Xen guest and watch it fail as described below, or not. You'll need to use the boot parameter 'apt-setup/
Regression potential: A limited number of people are still using GRUB Legacy anyway. I'd be pretty surprised if this broke anything other than Xen, which was already broken in this situation anyway.
Original report:
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
description: | updated |
affects: | grub2 (Ubuntu) → grub (Ubuntu) |
Changed in grub (Ubuntu): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in grub (Ubuntu Maverick): | |
status: | New → Triaged |
Changed in grub (Ubuntu Natty): | |
status: | New → Triaged |
Changed in grub-installer (Ubuntu Lucid): | |
status: | New → Invalid |
Changed in grub-installer (Ubuntu Maverick): | |
status: | New → Invalid |
Changed in grub-installer (Ubuntu Natty): | |
status: | New → Invalid |
Changed in grub (Ubuntu Lucid): | |
importance: | Undecided → High |
Changed in grub (Ubuntu Maverick): | |
importance: | Undecided → High |
Changed in grub (Ubuntu Natty): | |
importance: | Undecided → High |
Changed in grub (Ubuntu Lucid): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub (Ubuntu Maverick): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub (Ubuntu Natty): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub (Ubuntu Lucid): | |
milestone: | none → ubuntu-10.04.4 |
description: | updated |
Changed in grub (Ubuntu Lucid): | |
status: | Triaged → In Progress |
Changed in grub (Ubuntu Maverick): | |
status: | Triaged → In Progress |
Changed in grub (Ubuntu Natty): | |
status: | Triaged → In Progress |
I'm investigating this and trying to determine whether a fix in grub2 is sufficient or whether it needs a fix in grub-installer as well. I expect that the grub2 part of this is bug 623609, so I may end up marking this bug as a duplicate of that after further investigation.