I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Sector size (logical/physical): 512 bytes / 512 bytes This is Ubuntu 15.10, running: QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9.3), Copyright (c) 2003-2008 Fabrice Bellard Sometimes there are dependencies between enlightenments, QEMU is supposed to check that the supplied configuration is sane. In QEMU, individual enlightenments can be enabled through CPU flags, e.g: qemu-system-x8664 -enable-kvm -cpu host,hvrelaxed,hvvpindex,hvtime. How do I properly boot such a raw image in QEMU? No Hyper-V enlightenments are enabled by default by either KVM or QEMU. The bus=9 argument that -drive should accept is either interpreted as a filename, or completely ignored. $ qemu-system-x86_64 -drive format=raw file=x86-64.img bus=9 Qemu-system-x86_64: -drive bus=9: Could not open 'format=raw': No such file or directory That fails (I think) because my boot device is on /dev/sda, bus 0, so one of the following should work according to QEMU's man page (but doesn't): $ qemu-system-x86_64 -drive bus=9 format=raw file=x86-64.img Qemu-system-x86_64: -drive format=raw: drive with bus=0, unit=0 (index=0) exists The raw command line argument is, as far as I can tell, meant to be passed like this: $ qemu-system-x86_64 -drive format=raw file=x86-64.img (probably because PilOS wants to write to block 0 but can't) The emulator loads, but PilOS crashes, which means I did something wrong: Specify the 'raw' format explicitly to remove the restrictions. That gives a message: WARNING: Image format was not specified for 'x86-64.img' and probing guessed raw.Īutomatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. I have a disk image file from here that page says I can boot this image with QEMU and the following command: $ qemu-system-x86_64 -m 4096 -ctrl-grab -no-reboot x86-64.img
0 Comments
Leave a Reply. |