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
