Hi all, we notice some problems when using the boot=on option:
-drive file=test.qcow2,if=ide,index=0,boot=on Seems that some vm don't boot anymore, get: Disk I/o error: Status = 00000001 Disk I/o error: Status = 00000001 Disk I/o error: Status = 00000001 Windows 2000 could not start because the following file is missing or corrupt: <windows 2000 root>\system32\ntoskrnl.exe. ... The VM boot correctly when run without boot=on I then added some debug infos to block.c (bdrv_read), printing the sector number, result, and a block checksum. When I compare the output it seems that both VM read the same data, but behave differently. Any ideas why? READ SECTOR: 0 0 0000a6a6 1 -INIT EXTBOOT READ SECTOR: 0 0 0000a6a6 1 READ SECTOR: 63 0 0000aaa6 1 READ SECTOR: 63 0 0000aaa6 1 -READ SECTOR: 63 0 0000aaa6 1 READ SECTOR: 64 0 000089f1 1 READ SECTOR: 65 0 0000b956 1 READ SECTOR: 66 0 0000bcc1 1 @@ -653,6 +651,144 @@ READ SECTOR: 96 0 0000009c 1 READ SECTOR: 105 0 00004449 1 READ SECTOR: 106 0 00001f18 1 +READ SECTOR: 26098279 0 00006658 1 #different behavior here! +READ SECTOR: 26098280 0 00006b42 1 +READ SECTOR: 26098281 0 0000691f 1 +READ SECTOR: 26098282 0 000063a0 1 +READ SECTOR: 26098283 0 000056f2 1 +READ SECTOR: 26098284 0 0000202b 1 + - Dietmar -- 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
