Failure to boot CDROM with -drive arg
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 With the 2nd though, the initial CDROM syslinux loads, but fails to load the graphical menu, and also fails to boot in text mode fallback: 'vesamenu.c32: attempted DOS system call (See screenshot: https://bugzilla.redhat.com/attachment.cgi?id=311221 ) I've reproduced this with both KVM 65 and 70, on a Fedora 9 host. The CDROM boot.iso image I'm using here is the Fedora 9 $URL/images/boot.iso from any standard Fedora install tree. I can only imagine there's something different in the way extboot sets up the CPU/pagetables during cdrom boot, but its rather beyond my skills This was originally reported by a Fedora user here https://bugzilla.redhat.com/show_bug.cgi?id=452355 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 :| -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
Le mardi 08 juillet 2008 à 09:37 +0100, Daniel P. Berrange a écrit : 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 -cdrom /home/berrange/boot.iso is identical to -drive file=/home/berrange/boot.iso,index=1,media=cdrom with if=ide by default. Could you try you command line without boot=on ? With the 2nd though, the initial CDROM syslinux loads, but fails to load the graphical menu, and also fails to boot in text mode fallback: 'vesamenu.c32: attempted DOS system call (See screenshot: https://bugzilla.redhat.com/attachment.cgi?id=311221 ) I've reproduced this with both KVM 65 and 70, on a Fedora 9 host. The CDROM boot.iso image I'm using here is the Fedora 9 $URL/images/boot.iso from any standard Fedora install tree. I can only imagine there's something different in the way extboot sets up the CPU/pagetables during cdrom boot, but its rather beyond my skills This was originally reported by a Fedora user here https://bugzilla.redhat.com/show_bug.cgi?id=452355 Daniel -- - [EMAIL PROTECTED] -- L'avenir ne se prévoit pas, il se prépare. - Maurice Blondel -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
On Tue, Jul 08, 2008 at 10:48:18AM +0200, Laurent Vivier wrote: Le mardi 08 juillet 2008 à 09:37 +0100, Daniel P. Berrange a écrit : 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 -cdrom /home/berrange/boot.iso is identical to -drive file=/home/berrange/boot.iso,index=1,media=cdrom with if=ide by default. Could you try you command line without boot=on ? Yep, that works - so its clearly something todo with the extboot support 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 :| -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
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=detailaid=1977971group_id=180599atid=893831 -- Soren Hansen | Virtualisation specialist | Ubuntu Server Team Canonical Ltd. | http://www.ubuntu.com/ signature.asc Description: Digital signature
Re: Failure to boot CDROM with -drive arg
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=detailaid=1977971group_id=180599atid=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 :| -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
Le mardi 08 juillet 2008 à 11:17 +0200, Soren Hansen a écrit : 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=detailaid=1977971group_id=180599atid=893831 yes, in fact media=cdrom,boot=on is not equal to -cdrom ... -boot d. boot=on means use bios extension extboot with this drive, and using extboot allows the bios to manage this device and to boot from it. Laurent -- - [EMAIL PROTECTED] -- L'avenir ne se prévoit pas, il se prépare. - Maurice Blondel -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
Le mardi 08 juillet 2008 à 10:21 +0100, Daniel P. Berrange a écrit : 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=detailaid=1977971group_id=180599atid=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. I agree. Laurent -- - [EMAIL PROTECTED] -- L'avenir ne se prévoit pas, il se prépare. - Maurice Blondel -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
Daniel P. Berrange wrote: 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=detailaid=1977971group_id=180599atid=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. Semantically, boot=on means make this the first bootable hard disk. That's not to say that there shouldn't be a check. If you did: qemu-system-x86 -drive file=foo.img,boot=on -boot d You would still boot from the cdrom. Regards, Anthony Liguori 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 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
Le mardi 08 juillet 2008 à 08:01 -0500, Anthony Liguori a écrit : Daniel P. Berrange wrote: 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=detailaid=1977971group_id=180599atid=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. Semantically, boot=on means make this the first bootable hard disk. That's not to say that there shouldn't be a check. If you did: qemu-system-x86 -drive file=foo.img,boot=on -boot d You would still boot from the cdrom. So, boot=on means in fact bootable=true Regards, Laurent -- - [EMAIL PROTECTED] -- L'avenir ne se prévoit pas, il se prépare. - Maurice Blondel -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failure to boot CDROM with -drive arg
Laurent Vivier wrote: So, boot=on means in fact bootable=true I guess. I don't know that the later is more clear. I think the source of the confusion is the entire concept of first bootable harddisk which is what -boot c really means. FWIW, the reason media=cdrom,boot=on doesn't work, is that a CDROM's boot record is in el torito format instead of the traditional BIOS boot sector. media=cdrom,boot=on would work if the image was a disk image instead of an ISO. In fact, I'm inclined to think that media=cdrom,boot=on should not be explicitly prohibited because of this fact. Regards, Anthony Liguori Regards, Laurent -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
