31.12.2012 00:43, Gianluigi Tiesi wrote:
On 12/29/12 15:57, Michael Tokarev wrote:
[]
vm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive
file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw,boot=on -device
ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0
This is not scsi, this is ahci, FWIW.
Yes true, but boot=on option was made for scsi, so why it makes work my ahci
setup that instead would not work? I mean it should be unrelated but instead
looks like related.
Well. boot=on was made for general usage, it works (or worked) for
any bootable device, including scsi and ahci and network and other
stuff. It was a quick hack to allow booting from devices not
directly supported by seabios, and is not supported by upstream
anymore.
but if I run:
kvm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive
file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw -device
ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0
grub loads but it's unable to identify the filesystem
Well. Which version of seabios is that? I'm asking because
this does not boot at all with current seabios+qemu-kvm from
wheezy: guest bios does not find any boot device. If in your
case guest bios finds the boot device and loads grub, it must
be some other version of either qemu-kvm or seabios.
I'm on sid, and the just updated seabios 1.7.1-1 exposes same behavior
qemu-kvm is 1.1.2+dfsg-3
Interesting. Okay. So I need some way to reproduce this.
Can you please tell us what do you use as the guest? What
is it, how it was setup, etc? Maybe it is enough to do a
fresh install of some distribution to expose this issue?
[]
Unfortunately bootindex options changes nothing
Ok.
here grub2 without boot=on
Booting from Hard Disk...
GRUB loading.
Welcome to GRUB!
error: unknown filesystem.
Entering rescue mode...
grub rescue> ls
(hd0) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1) (fd0)
grub rescue> ls (hd0,msdos4)
error: unknown filesystem.
Oh well. It looks like grub is unable to _read_ the drive.
I need a way to reproduce this :)
I'll try doing some installing/booting here when time permits.
Maybe you can provide some instructions or maybe a guest image
to speed things up... ;)
while it works fine with boot=on
Ok. So it appears to be some grub+seabios issue with the
correct/modern way of booting things, while old/legacy boot
option works fine.
Thank you!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
