On 08/15/12 02:48, Jordan Justen wrote: > Laszlo, > > Should qemu's -boot option impact this? Or, is there another qemu > command line option that will?
I found some hints in "docs/bootindex.txt" in the qemu source tree. FWIW I only tested the patch with virt-manager. virt-manager constructs a quite complex qemu command line. Simplified, the relevant options seem to be (for a boot order of Floppy B / Hard Disk / CDROM): (a) first define drives with id's: -drive file=/path/image.img,id=HDD \ -drive file=/path/image2.iso,media=cdrom,id=CDROM,readonly=on \ -drive id=FLOPPY_A \ -drive id=FLOPPY_B \ (b) floppies take additional setup: -global isa-fdc.driveA=FLOPPY_A \ -global isa-fdc.driveB=FLOPPY_B \ (c) then the bootindex is tacked on to the following options: -global isa-fdc.bootindexB=1 \ -device ide-drive,bus=ide.0,unit=0,drive=HDD,bootindex=2 \ -device ide-drive,bus=ide.1,unit=0,drive=CDROM,bootindex=3 \ (d) The qemu debug console can be redirected to a file like this (in order to capture the debug output from the patch -- DEBUG_VERBOSE must be enabled via gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel in the dsc file): -debugcon file:/tmp/debug.txt \ -global isa-debugcon.iobase=0x402 Thanks, Laszlo ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
