raw partition boot fails with GRUB2, OK with GRUB
Posted: 12. Apr 2011, 21:10
Computer: HP Pavilion a1742n with AMD Athlon 64x2 3800+
Host OS: Windows XP SP3 (on sda2)
VirtualBox 4.0.4 r70112
Guest OS: Ubuntu 10.04, 32-bit
Linux partitions include:
sda7 boot partition contains GRUB and kernels for unrelated Ubuntu 64-bit system
sda9 Linux swap
sda11 Ubuntu 10.04, 32 bit system including its own /boot directory
/boot contains GRUB2
kernels include 2.6.32-29
2.6.32-24
Following the directions in http://www.virtualbox.org/manual/ch09.html#id418914, the VirtualBox machine uses raw partition setup, with partitions sda7, sda9, sda11 active
In all cases, GRUB and/or GRUB2 are using UUID=473d6c...6a2c to identify the partition in which to find the kernel.
Symptoms:
1. Ordinary "stand-alone" boot using GRUB, chainlinked to GRUB2, selecting Linux 32-bit, works OK
2. VirtualBox boot GRUB, selecting Linux 32-bit (directly; no chainlink), works OK
3. VirtualBox boot GRUB, chainlinked to GRUB2, selecting Linux 2.6.32-29, gives "critical error". VBox.log and VBox.png are attached.
Other observations:
4. in GRUB2, selecting 2.6.32-29 (recovery mode) gives the same results.
5. VirtualBox boot GRUB, chainlinked to GRUB2, selecting Linux 2.6.32-24, does not popup "critical error" message, but hangs with a "_" prompt.
6. in GRUB2, selecting 2.6.32-29 and using the editor to remove the "splash" parameter results in no popup, but gives the "_" hang.
7. upgrade to 2.6.32-30 makes no difference.
8. adding guest additions makes no difference.
9. what I'm calling GRUB is probably version 0.97
10. what I'm calling GRUB2 is version 1.98-1Ubuntu9
This may be related to forum posting http://forums.virtualbox.org/viewtopic.php?f=6&p=175133
Has anyone else seen this?
Clearly there are workarounds (my use of only GRUB is one), but should I file a bug report?
Host OS: Windows XP SP3 (on sda2)
VirtualBox 4.0.4 r70112
Guest OS: Ubuntu 10.04, 32-bit
Linux partitions include:
sda7 boot partition contains GRUB and kernels for unrelated Ubuntu 64-bit system
sda9 Linux swap
sda11 Ubuntu 10.04, 32 bit system including its own /boot directory
/boot contains GRUB2
kernels include 2.6.32-29
2.6.32-24
Following the directions in http://www.virtualbox.org/manual/ch09.html#id418914, the VirtualBox machine uses raw partition setup, with partitions sda7, sda9, sda11 active
In all cases, GRUB and/or GRUB2 are using UUID=473d6c...6a2c to identify the partition in which to find the kernel.
Symptoms:
1. Ordinary "stand-alone" boot using GRUB, chainlinked to GRUB2, selecting Linux 32-bit, works OK
2. VirtualBox boot GRUB, selecting Linux 32-bit (directly; no chainlink), works OK
3. VirtualBox boot GRUB, chainlinked to GRUB2, selecting Linux 2.6.32-29, gives "critical error". VBox.log and VBox.png are attached.
Other observations:
4. in GRUB2, selecting 2.6.32-29 (recovery mode) gives the same results.
5. VirtualBox boot GRUB, chainlinked to GRUB2, selecting Linux 2.6.32-24, does not popup "critical error" message, but hangs with a "_" prompt.
6. in GRUB2, selecting 2.6.32-29 and using the editor to remove the "splash" parameter results in no popup, but gives the "_" hang.
7. upgrade to 2.6.32-30 makes no difference.
8. adding guest additions makes no difference.
9. what I'm calling GRUB is probably version 0.97
10. what I'm calling GRUB2 is version 1.98-1Ubuntu9
This may be related to forum posting http://forums.virtualbox.org/viewtopic.php?f=6&p=175133
Has anyone else seen this?
Clearly there are workarounds (my use of only GRUB is one), but should I file a bug report?