grub does not install properly to a virtio disk in kvm (/dev/vda)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub (Debian) |
Fix Released
|
Unknown
|
|||
grub (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
grub-installer (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: grub
This bug is related to Bug #279754, which was recently fixed. Installations to virtio hard disks would not complete. They complete now, but the installed system is not bootable.
This looks to me to be a problem with grub-install.
I tested this as follows:
1) install system A using
* kvm -m 256 -hda A.img -cdrom intrepid-
2) install system B using:
* kvm -m 256 -drive file=B.
Both installs complete. However, only system A will boot. System B will not boot, hanging with a line that says:
* Booting from Hard Disk...
Next, I take system A, and boot it with its disk as a virtio device, with:
* kvm -m 256 -drive file=A.
This boots fine. The root filesystem is mounted and functional as /dev/vda
Next I take system B, and try to boot it with the disk as a standard disk, with:
* kvm -m 256 -hda B.img
This is not bootable either. Same error message as above.
Finally, I take system A, boot it with its disk as a virtio device, and re-run grub-install /dev/vda (after updating /boot/grub/
:-Dustin
Changed in grub: | |
status: | Unknown → Fix Released |
Can confirm this. Tried to install latest ubuntu- 8.10-beta- server- amd64.iso (20081013) and the system is not bootable. Workaround is as described by Dustin. First installing into simple hda drive and then switch to vda (virtio) after installation.
Hardy works both ways without problem. The goal is of course to make intrepid work as well.