Use telnet to see if you can connect to the required ports on the VC/ESX servers.
Verify you are using the proper scsi controller for your virtual disk (BusLogic or LSI Logic).
# mount /dev/sda2 /mnt # mount bind /dev /mnt/dev # cd /mnt # chroot.This article helped but additional information was required to resolve my issue.Failed: An error occurred during the conversion: GrubInstaller:InstallGrub: Failed to read grub configuration from /mnt/p2v-src-root/boot/grub/t.In this article in our series hunter x hunter episode 40 we will continue by discussing some post-conversion steps and tips for troubleshooting and resolving failed conversions.Power on the VM, wait a few minutes to let it discover all it's new hardware then reboot.Try rebooting the source server, this is a requirement for Windows NT and 2000 servers.
While VMware Converter 5 does a good job live-cloning the existing Linux servers, sometimes you have to use the Cold Clone boot CD if the physical server uses software raid (and then boot VM from the broken mirror side or sometimes the resulting VM does.
The reason for this is that the old NIC still exists as non-present hardware with an IP address.
If your source server has more then two serial (COM) ports, edit the registry and look for hklmhardwaredevicemapserialcom and remove any ports above serial port.Cloning (6-95 post-cloning (95-97 customization/Reconfig (97-99 install Tools/Power On (99-100).It is likely that udev detected the network hardware change and added eth1 to this file.You can then browse that disk and edit the i file.After you've used VMware Converter for a physical-to-virtual migration, what comes next?