Libvirt parses qemu-kvm -help output for boot=on. Without this it's not possible to boot from a virtio block device.
--- kvm-85rc3/qemu/qemu-options.hx.org
+++ kvm-85rc3/qemu/qemu-options.hx
@@ -77,6 +77,7 @@
"-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]\n"
" [,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]\n"
" [,cache=writethrough|writeback|none][,format=f][,serial=s]\n"
+ " [,boot=on|off]\n"
" use 'file' as a drive image\n")
STEXI
@item -drive @var{option}[,@var{option}[,@var{option}[,...]]]
@@ -111,6 +112,9 @@
an untrusted format header.
@item serial=@var{serial}
This option specifies the serial number to assign to the device.
+@item boot=@var{boot}
+@var{boot} if "on" enables extboot for a given drive so it can be used
+as a boot drive.
@end table
By default, writethrough caching is used for all block device. This means that
@@ -163,6 +167,11 @@
qemu -drive file=file,if=scsi,bus=0,unit=6
@end example
+To boot from as SCSI disk, one would use:
+@example
+qemu -drive file=file,if=scsi,boot=on
+@end example
+
Instead of @option{-fda}, @option{-fdb}, you can use:
@example
qemu -drive file=file,index=0,if=floppy
--
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
