On 12/29/12 15:57, Michael Tokarev wrote:
Control: tags -1 + moreinfo unreproducible
04.11.2012 08:49, Gianluigi Tiesi wrote:
Package: qemu-kvm
Severity: minor
Hi, I've noticed my kvm warns about using boot=on so I've decided to
find some documentation,
as I found boot=on enables extboot option rom removed upstream because
seabios can boot directly
from sata. References in #652447, perhaps I was able to boot as linux
vm from a scsi disk using
latest seabios code without using lsi proprietary rom (maybe they
implemented scsi boot).
if I run:
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.
kvm complains about deprecated boot=on, grub loads and it can boot
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
But at any rate, you forgot one more parameter: it is bootindex.
Try this:
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,bootindex=0
This works here just fine.
Unfortunately bootindex options changes nothing
Does it answer your question/issue?
sda4 is ext4, and I'm trying to boot my windows from my linux
maybe seabios it's unable to correcly map whole drive?
Nope, it is completely unrelated. For any virtual disk drive
given by qemu to the guest - no matter at all which it is on
the host - the guest (including the bios) sees it just like
a regular disk drive. It is up to qemu to make the host
representation of it completely transparent, and qemu does a
good job in there.
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.
while it works fine with boot=on
Grub2 files are in my currently mounted root partition
Regards
--
Gianluigi Tiesi <sher...@netfarm.it>
EDP Project Leader
Netfarm S.r.l. - http://www.netfarm.it/
Free Software: http://oss.netfarm.it/
Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
