When you move the disk image, the installed OS is not aware of that, and it tries to boot with the drivers for the controllers of the previously used virtualization platform. Windows, when it cannot find the driver for the currently installed disk controller, BSOD's and reboots.
This is pretty much the same as moving a windows hard drive between different hardware platforms.
There can be two solutions - either use a v2v converter that can convert from KVM to VBox (I don't know of any, but if you do, please share), or inject the drivers into the VM's image before you start it in a new environment. The easiest way to do that would be to do the follwoing:
- Before the conversion, in KVM, run
mergeide.reg (you can find it on
MS website and pretty much all over the internets)
- Switch the boot disk under KVM to IDE, and start the VM up
- If everything works, convert the image with
qemu-img to a
- Create a VM in VBox, with the first boot disk as IDE (not SATA
- Attach the converted disk - the system should boot
- Install the Vbox disk drivers (might have to attach a secondary
small disk for them to take effect)
- Switch the boot disk's interface to the desired controller type,
and start the VM up again