Posts tagged p2v
After a very long P2V process, I booted up the new VM and was greeted with the following error:
The parent virtual disk has been modified since the child was created.
Upon which, the VM would not power on. After waiting on a 12 hour conversion, this is a depressing error to receive. Luckily, it is fixable. Using KB 1007969, the vmdks can be edited to fix the mismatch.
Essentially, you have to rebuild the parent-child chain within the VMDKs. The KB does a very detailed job of explaining what to do, but I will note to make sure you’re changing the parentCID of the file once you modify and not the CID itself, and I’d recommend commenting what you change in case you need to revert. After getting the VM to power on, be sure that the VM behaves in an expected state.
VMware has done a wonderful job making converting your existing infrastructure as painless as possible, but there are still issues that pop up every now and then. I find these issues occur much more often on Windows 2000 due to its age. We’ve ran into two issues recently on a couple of conversions of machines that now fall under our division’s management, and the worst part of these is that you only know about them after the conversion is done and you try to boot up your new VM. Fortunately, they are easy fixes:
VM boots with Blue Screen stating STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
This occurs because the newly converted VM does not have the necessary drivers to boot, and it is an easy fix (KB Article: 1005208).
- Power on the source for the conversion. The source can be physical or virtual.
- Download the VMware SCSI Disk Controller driver diskette at http://download3.vmware.com/software/vmscsi-126.96.36.199.flp.
- Extract the disk image into files and copy them to the source.
- Attach the diskette to a virtual machine and copy the files from the virtual diskette drive to the physical source.
- Write contents of the image onto a floppy diskette and insert the diskette into the physical source. Image extraction software is required to do this.
- Access the floppy diskette or files on the source from My Computer.
- Right-click vmscsi.inf and click Install. The VMware SCSI drivers are installed.
- Restart the source to complete installation.
- Perform another conversion with VMware Converter
Converted machine fails to power on with the error: Stop:0X0000001 KMODE_EXCEPTION_NOT_HANDLED
This is actually Microsoft’s fault. The resolution is covered in Microsoft’s KB 904374.
They provide the resolution on the basis that someone received this problem on their machine and then rebooted and now they can’t boot any longer. You can proceed with their instructions exactly, and repair the VM that you’ve already converted. Or, if you prefer an easier method, you can request the Hotfix download from Microsoft and install it on the Physical source then simply retry the conversion and it should work properly.