On Jun 28, 2013, at 3:39 AM, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > Il 28/06/2013 03:01, Ken Roberts ha scritto: >>>> More details on "not bootable" would be nice. Do you get a blue screen? Seabios screen? You may need to prep the image before you convert it (google mergeide). >> >> Not sure if you support screenshots on the list, so I'm typing it below the post. >> >> The only configured device is the hard disk, it is INSTANTLY showing Boot failed: not a bootable disk. > > If you attach one of your Windows images to one of the Linux VMs and run > the Linux VM on Parallels, what does "file -s" say if you pass it the > Windows disk? # fdisk -l /dev/sdb Disk /dev/sdb: 68.7 GB, 68719730688 bytes 255 heads, 63 sectors/track, 8354 cylinders, total 134218224 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00010001 Device Boot Start End Blocks Id System /dev/sdb1 * 63 134190944 67095441 7 HPFS/NTFS/exFAT # file -s /dev/sdb /dev/sdb: x86 boot sector, Microsoft Windows XP MBR, Serial 0x10001; partition 1: ID=0x7, active, starthead 1, startsector 63, 134190882 sectors, code offset 0xc0 # file -s /dev/sdb1 /dev/sdb1: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80) > And what does "file" say (on the host) about the same Windows image > after conversion to raw? $file -s popeye-c-raw.img popeye-c-raw.img: data > Also, can you do > > dd if=/path/to/windows-image.raw bs=512 count=1 | od -tx1 > > (of course you have to replace /path/to/windows-image.raw) and include > the output? $dd if=popeye-c-raw.img bs=512 count=1 | od -tx1 1+0 records in 1+0 records out 512 bytes (512 B) copied, 0.000139388 s, 3.7 MB/s 0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0001000 > Paolo Thanks for the help. -- 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