Ján ONDREJ (SAL) wrote:
I had problems during the update for that as well, when the beta came out it run for a few weeks and then an upgrade broke it. Not an install issue, I just broke things so badly I couldn't update any further to fix them.On Wed, Apr 29, 2009 at 02:25:05PM +0200, Emre Erenoglu wrote:2009/4/29 Ján ONDREJ (SAL) <ondrejj salstar sk>after my rawhide installation was corrupted, I planned to install a fresh Fedora11-Preview in virt-manager. Everything worked well, just GRUB has been not installed. I can't fix this by running some commands in rescue mode. My attempts are here: sh-4.0# df /boot Filesystem 1K-blocks Used Available Use% Mounted on /dev/vda1 198337 13573 174524 8% /boot My root partition is /dev/vda1, so my root disk is /dev/vda (paravirtualized disk). sh-4.0# grub-install /dev/vda expr: non-numeric argument /dev/vda1 does not have any corresponding BIOS drive.Hi, I have the same problem even though my host and guest are not Fedora but Pardus. It seems somehow that GRUB does not play well with vda disks. As a workaround, I added the same disk image as hda, installed GRUB, then reverted it back to vda. It works.Thanks for reply. Another workaround is installation of Fedora 11-Beta and then update to current rawhide. :)
My current machines were built on the "snapshot" CD, install, update. As of this morning it's good. I'm running a snapshot machine for some development, since it will need to use the latest gcc.
Curious, that this problem occured in preview release and not in any Beta. This is same bug or not? Bug 479760 - [PATCH] add support for virtio_blk devices to grub-install https://bugzilla.redhat.com/show_bug.cgi?id=479760
-- bill davidsen <davidsen tmr com> CTO TMR Associates, Inc "You are disgraced professional losers. And by the way, give us our money back." - Representative Earl Pomeroy, Democrat of North Dakota on the A.I.G. executives who were paid bonuses after a federal bailout.