Re: Failure to boot CDROM with -drive arg

["Daniel P. Berrange" <berrange@redhat.com>]

On Tue, Jul 08, 2008 at 11:17:24AM +0200, Soren Hansen wrote:
> On Tue, Jul 08, 2008 at 09:37:30AM +0100, Daniel P. Berrange wrote:
> > The following two command lines should be identical from the user's
> > point of view:
> > 
> > # qemu-kvm -cdrom /home/berrange/boot.iso -boot d -m 500
> > 
> > # qemu-kvm -drive file=/home/berrange/boot.iso,if=ide,media=cdrom,index=2,boot=on -m 500
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=1977971&group_id=180599&atid=893831

Ok, so basically this is saying that boot=on only works for media=disk.
I really don't like the fact that we now have 2 different ways of flagging
bootable disks, depending on whether want to use BIOS boot or extboot.

The management apps shouldn't have to make such a decision - QEMU should
be picking the most appropriate choice for us. ie, if we have boot=on
with an IDE cdrom, then QEMU should automatically do a BIOS boot instead
of extboot. This way if extboot gets improved, QEMU can update its logic
to correspond without needing to change all the management apps using
QEMU.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|