On Sun, Jan 15, 2012 at 05:27:39PM +0400, Michael Tokarev wrote: > On 15.01.2012 17:18, Avi Kivity wrote: > > On 01/15/2012 03:10 PM, Michael Tokarev wrote: > [] > >> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because > >> of lack of boot support from scsi (and no alternative), and because > >> many people's scripts who used boot= broke. I thought it is better > >> to let users to have a chance to perform a smoother transition than > >> to break their stuff. > > > > It's really sad that people have to use lsi scsi. Luckily qemu 1.1 will > > feature virtio-scsi, though of course that doesn't help already > > installed guests or non Windows/Linux guests. Do you know what the use > > cases requiring scsi boot are? > > I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447 > and a few private messages asking me for ways to restore booting from scsi, > all talking about older/custom systems which worked for years in kvm. > As you can see in the bugreport mentioned, I know that scsi is broken > and should not be used and so on, and suggested switching from it on > every chance. > > >> Now, I've a question: what seabios implementation of extboot we're > >> talking about? -option-rom which is impossible to select as a first > >> boot device? > > > > seabios has native support for booting from virtio-blk, and will > > natively support virtio-scsi as well. > > Ah. Well, I thought especially about lsi emulated scsi. I wasn't > able to boot from it even with their bios -- once there's at least > one other bootable device present (including the NIC) it refuses > to boot from lsi emulated scsi drive. > Kevin is going to include a patch to Seabios to fix that. Meanwhile you can use bootindex to specify boot order. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
