converter

I’ve run into the issue lately where P2Ving a Windows 2000 machine will result in a blue screen when the new virtual machine boots. [A google search shows many others with this problem](communities.vmware.com windows 2000 blue screen p2v). The root cause of the issue is related to Update 1 of Service Pack 4. Luckily, with vCenter Converter, not VMware Converter Standalone, VMware delivers a nice fix for this issue. Follow normal steps in vCenter Converter - import a machine, setup your source, and as the Converter Agent is installed you’ll be prompted for a location to the VMware SCSI Disk Driver (scsiport....

It’s been a while since I’ve had time to post, but I couldn’t keep this to myself: From the VMware vCenter Converter 4.2 for vCenter Server 4.1 Release Notes: What’s New The VMware vCenter Converter 4.2 is a substantial upgrade from vCenter Converter 4.1 and includes the following new functionality (previously found only in vCenter Converter Standalone 4.0.x): Physical to virtual machine conversion support for Linux sources including: Red Hat Enterprise Linux 2....

Most of this was taken from this site: http://conshell.net/wiki/index.php/Linux_P2V Up front work Determine exactly what you’re doing, and the resources you’ll need on the VMware side. as root: sfdisk -s /dev/hda: 39070080 total: 39070080 blocks To find the size in GB, divide by 1024 twice. 39070080/1024/1024 = 37.260 GB Partition layout - know exactly the partitions, sizes and FS types. This can be gleaned from the output of `fdisk -l /dev/sda` and the content of /etc/fstab....