Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 302755 - sys-boot/grub-0.97-r9 not working with KVM's virtio devices (/dev/vda)
Summary: sys-boot/grub-0.97-r9 not working with KVM's virtio devices (/dev/vda)
Status: RESOLVED DUPLICATE of bug 259613
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: Highest major (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2010-01-29 14:28 UTC by Kyle Gonzales
Modified: 2010-01-29 21:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Kyle Gonzales 2010-01-29 14:28:01 UTC
I just installed Gentoo in a VM on KVM, using a virtio-based disk image.  I am having the same issue with GRUB as seen in bug 259613, except the update did not fix my issue.  I am using the updated version of grub:


I booted the VM using the most recent AMD64 install CD and stage 3 tarball:


I added the same information the original reporter did:

# cat /boot/grub/ 
(hd0)   /dev/vda

 # fdisk -l

Disk /dev/vda: 10.5 GB, 10485760000 bytes
16 heads, 63 sectors/track, 20317 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Disk identifier: 0x6f03db3f

   Device Boot      Start         End      Blocks   Id  System
/dev/vda1   *           1         407      205096+  83  Linux
/dev/vda2             408        1448      524664   82  Linux swap / Solaris
/dev/vda3            1449       20317     9509976   83  Linux

# grub-install /dev/vda
expr: non-numeric argument
/dev/vda1 does not have any corresponding BIOS drive.

 # grub
Probing devices to guess BIOS drives. This may take a long time.

grub> root (hd0,0)

Error 21: Selected disk does not exist

Because I cannot get grub to install the configuration, I am still in the chroot'd environment.
Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-01-29 21:44:43 UTC

*** This bug has been marked as a duplicate of bug 259613 ***