When I boot the guest in Safe mode, I see a bunch of sys files get loaded properly until it's stuck after Loaded: \Windows\system32\drivers\crcdisk.sys. I tried to use some conversion options like qemu-img convert -p -f qcow2 -O vmdk -o adapter_type=lsilogic,subformat=streamOptimized,compat6 win2008.qcow2 win2008.vmdk and tried moving between the 3 available scsi controllers (LSI Logic SAS, LSI Logic Parallel, VMware Paravirtual) to no avail. The command is mostly known for using it to manipulate virtual disks. A recent hardware or software change might be the cause. vmkfstools options target Whereby target can be either a physical disk, a virtual disk or a device. However I'm stuck with a Windows Error Recovery: Windows failed to start. Attach the newly created win2008_v2.vmdk file to a newly created guest with default settings.vmkfstools -i win2008.vmdk -d thin win2008_v2.vmdk on the VMware host.qemu-img convert -p -f qcow2 -O vmdk win2008.qcow2 win2008.vmdk using qemu v4.2.1.I tried to follow recommendations from Convert qcow2 to vmdk and make it ESXi 6.0 Compatible and steps I found on the web: I realize the Win2008 VM is old and beyond EoS but need to keep this in place for now and is in a VLAN that is not internet accessible. I'm trying to move an old Win2008 server from KVM to VMware ESXi 6.7.
0 kommentar(er)
