Release Engineering

Tasklist

FS#19514 - [aif, virtio, grub] Grub fails on virtio-disks

Attached to Project: Release Engineering
Opened by frederick_metzengerstein (metzengerstein) - Tuesday, 18 May 2010, 19:54 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 25 August 2012, 13:08 GMT
Task Type Feature Request
Category AIF
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 2010.05
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Though current aif (2010.05 release) now can handle virtio block devices, grub doesn't.
The installation works fine until setting up grub, when it fails finding the correct device.

The solution is by manualy creating /boot/grub/device.map (in the installation-environment: /mnt/boot/grub/device.map) with the correct drive-mapping like "(hd0) /dev/vda".

I've added a virtio-section in the wiki, which also mentions this problem:
http://wiki.archlinux.org/index.php/KVM#Paravirtualized_guests_.28virtio.29


Request: It would be nice if aif could be modified accordingly.


Additional info:
* package version(s)
aif 2010.04.18-1
* config and/or log files etc.
none

Steps to reproduce:
See above.
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 25 August 2012, 13:08 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Grub-legacy has been removed from official repos.
Comment by Thomas Bächler (brain0) - Saturday, 29 May 2010, 09:12 GMT
I noticed the same when installing on a virtio disk. Grub is VERY stupid this way - note that any automatic generation of device.map is pure guessing, so I am unsure what to do here.
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 12 December 2010, 15:51 GMT
is this one of those things that warrants switching to extlinux/grub2/.. ?
Comment by Dieter Plaetinck (Dieter_be) - Friday, 23 December 2011, 18:48 GMT
so grub can be installed on virtio just fine, except it device map generation is stupid and needs some assistance?
i wonder if we should either:
1) tell users (if we detect a virtio disk) that grub doesn't work well on virtio and they should choose syslinux. (since last update of this ticket we have syslinux)
2) do some hackery in AIF to fix up the device map.

Loading...