Dapper images fail to boot
Bug #285093 reported by
Nick Barcet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VMBuilder |
Fix Released
|
Undecided
|
Unassigned | ||
vm-builder (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
sudo vmbuilder kvm ubuntu --suite dapper
Resulting image fails to boot with grub error 2
I have fixed a couple issues in the way device.map and menu.lst were generated for dapper in rev 239 (trunk), and entire /boot/* seems now identical to what is generated by ubuntu-vm-builder (which boots), but this does no seem to be enough.
Related branches
Changed in vm-builder: | |
assignee: | nobody → soren |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in vmbuilder: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Recently I had the grub error 2 when I wanted to move my system from an old hard-disk to a new one.
It turned out recent mkfs will create the filesystem with inode size 256. This is only supported by grub since hardy (grub 0.97-29ubuntu19).
ubuntu-vm-builder on hardy uses inode size 128 both for a hardy and dapper vm.
vmbuilder on intrepid uses inode size 256 for a hardy vm.
My guess is vmbuilder on intrepid will also use inode size 256, which is not supported by dapper's grub. I guess you need to pass -I 128 to mkfs.ext2 to make it work. Unfortunately I couldn't find the right place to do that, so I could not test this yet.