VMware Communities : Document List - Converter

IBM BladeCenter HS21 P2V Conveter can't search HHD

Tue, 08 Sep 2009 03:29:54 GMT

Hotplugging coldclone support to a running bootcd

Wed, 15 Apr 2009 14:19:44 GMT

We all know version 4 is out of beta and has several improvements over version 3.x. But version 4 is entirely hotclone based. Although it works great most of the time, there are cases that preferably need to be coldcloned. Building custom coldclone bootcd’s is not really science and was described already several years ago. That is just a matter of adding the files from the free standalone version and applying some registry patches.
This little tool is not science either, but merely a different approach towards a custom bootcd. This is a handy little app that will let you attach and load converter version 3.0.3 (the last version supporting coldclone) to any (almost) running windows preinstallation livecd. No need to have a custom buildt coldclone cd, no need for pebuilder plugins, no need for winbuilder scripts, or any similar strategy for that sake. You can grab a standard minimal recovery cd for vista or 2008, or an older bartpe bootcd of either xpsp2/xpsp3 or w2k3, and it will work in hotplugged coldclone mode.

What does it do?
There are 2 batch scripts included that collects the required files from an installation or extracts the files from the installer. It saves the files in a directory named “VMware-Converter-3.0.3”. Copy this directory to the root of a disk that will be accessible from the running bootcd. Also put the file “Converter303_Coldclone_Loader.exe” into the same directory and execute it from there.
The loader will patch the registry with all necessary entries as well as installing the 2 required services on the running preinstallation system. The loader works in such a “portable” way because of a registry-patching routine that assumes one known top-directory and patches according to varying driveletters for that disk.
The tool will generate desktop and startmenu shortcuts in your PE shell. There are two options; coldclone and hotclone mode. The hotclone mode was merely added just for the sake of having the “Configure Machine” as an option (which is disabled in coldclone mode). It has buildt-in protection against accidental execution in non-PE environments.

Supported OS’s:
32-bit xpsp2 and up to server 2008. Note, this is for the loader and not for converter itself.

Requirements:
Have the collected files on a writeable storage medium with correct directory structure.

Coldclone over wireless, all hotplugged.
It is not a problem to transfer it over a wireless even if you don’t have the stack buildt onto your bootcd. Yes it will be slooow, but possible. What we do is hotplug vmware player or workstation, just as we added converter. Here is a link to the needed tool with explanation; http://www.boot-land.net/forums/index.php?showtopic=6924
This way we have hotplugged vmware support to a running Preinstallation Environments. So how would you be able to connect over wireless from a bootcd when the system does not support it?

Explanation;
Attach a wireless usb adapter to the computer. In my case the guest vm was xpsp3. Disconnect it from the host and connect to the guest system. Create a host-only connection between the host and guest. You will now have 2 network adapters in the guest (1 usb wireless and 1 ethernet) and 1virtual network interface in the host. So on the host, all you need is 1 virtual network adapter, vmnet1 in my case. Inside the guest we must make a network bridge with the wired and wireless. Preferably connect to the access point with the usb adapter first. Important to set compatibility mode for the wired nic with "netsh bridge set adapter 2 ForceCompatibilityMode=enable" . Check the correct nic with “netsh bridge show adapter”. This is done to let the traffic be forwarded onto and over the wireless. In the host we must stop the virtual nat and dhcp services with “vnetlib – stop nat” and “vnetlib – stop dhcp”. We must also configure vmnet1 to automatically assigned IP address. When done with all configuration, issue “vnetlib – disable adapter vmnet1” and “vnetlib – enable adapter vmnet1” to have new IP and dns settings received from your access point. We can now happily surf the net over a wireless helper vm, with only one virtual network adapter on the host. So this is a bridge made the other way around.
And because of the slow speed, you better start the conversion before you go on a holiday.

Some screenshots of converter attached to different bootcds;
http://i402.photobucket.com/albums/pp106/jokke49/coldclone_bartpe_xpe.jpg
http://i402.photobucket.com/albums/pp106/jokke49/coldclone_storagecraft.jpg
http://i402.photobucket.com/albums/pp106/jokke49/coldclone_vistape_wireless.png
http://i402.photobucket.com/albums/pp106/jokke49/coldclone_windows_2008.jpg

Joakim Schicht

Physical Machine with disk LUN

Wed, 25 Mar 2009 01:49:44 GMT

Hi,

I have a physical machine that have one local disk and a
disk that is a LUN. Do I need to do anything special when doing import?

Thanks

Ray

Using Putty to forward VMware Converter's required ports to an inaccessible ESX Host

Tue, 03 Mar 2009 18:55:49 GMT

This is the schematic workaround (PortForwardingMap.png) with ports that need to be opened for VMware Converter. If there is an error in this, please comment on this document.

To create the tunnel using a Windows converter host, use putty. (If you run a real OS like Linux, use "ssh -L 443:esxhost:443 -L 902:esxhost:902 username@esxhost")

SSH to the ESX host and create 2 local tunnels for ports 443 and 902. (Putty.png)

Make sure you click ADD before starting the session!

Then, using the standalone converter, instead of typing the vCenter address or the ESXhost address, just use the address of the Converter host (Where you ran putty and the converter).

All requests from the source server to the ESX host will go via the Converter host that can reach the ESX server.

If there are any questions, or update requests, please post a comment to this document.

Author: Ger Apeldoorn

Steps to Install Vmware standalone converter and create a physical machine to virtual machine

Fri, 27 Feb 2009 07:31:06 GMT

Click the link given below to view the web site link whcih explains about the Steps to Install Vmware standalone converter and create a physical machine to virtual machine

http://www.petri.co.il/virtual_convert_physical_machines_to_virtual_machines_with_vmware_converter.htm

http://www.petri.co.il/virtual_convert_physical_machines_to_virtual_machines_with_vmware_converter_2.htm

Converter stopping task due to an "untrusted certificate"

Sat, 06 Dec 2008 23:50:25 GMT

I am just conducting some tests with ESXi and Converer. I tried to migrate an existing VM from my VMWare Workstation to the ESXi U3. The conversion run for about 20 minutes and then errored out with an "Unkown Error" and hinting me, where I can find the logs. Looking into the logs I found out, that it did drop the connection due to an untrusted certificate - which I think is pretty usual for a) a testinstallation and b) even for a smal productive installation, so I think, this should not break the conversion, but rather ask, if one likes to continue nevertheless

Import a Physical Microsoft 2003 Cluster ( MSCS ) to ESX 3i Server

Fri, 05 Dec 2008 18:26:29 GMT

I did a lot of searching through the forums for importing an existing MSCS physical cluster into VMWare and did not come across too many detailed posts. My dev systems had MSDTC clustered so I probably experienced more issues than what most people would have gone through. This general walkthrough imports the systems into a single VMWare ESX 3i host server. The process is fairly straight forward, but success stems on having the right tools on hand with the right details in accomplishing the task. I hope someone else finds this useful.

GENERAL OUTLINE FOR IMPORTING MSCS NODE TO VMs
Based on VMWare KB 1002661

IMPORT PHYSICAL SERVER INTO VMWARE
(These were steps used for a MSDTC cluster in which VSS of VMWare Tools would fail to install)
1. Import OS partition and any non-shared (non-Quorum) drives, do not install VMWare tools at this time.
2. Turn on VMs but disconnect from the network
a. Install VMWare Tools without VSS option
b. Clean up old IP entries in the registry, but leave the old IPs under the cluster related keys.
c. Assign old IP addresses to VM

CREATE THE SHARED DRIVE (QUORUM DISKS) VIA REMOTE CL
See Chapter 2 of VMWare doc called Setup for Microsoft Cluster Service Update 1 Release for ESX Server 3.5… (vi3_35_25_u1_mscs.pdf)
1. For path reference, get the path of an existing VM

general command:
vmware-cmd.pl --server --username –password –l

outputs:
/vmfs/volumes/48f7xxxx-06c8xxxx-xxxx-001ec9b7xxxx/VM01/VM01.vmx

2. Create the Shared drive via Remote CLI using the path as reference,

general command:
vmkfstools.pl --server --username --password -c 1g -d eagerzeroedthick -a lsilogic "/vmfs/volumes/48f7xxxx-06c8xxxx-xxxx-001ec9b7xxxx / QUORUMS/Qourum_E.vmdk"

ADD QUOROM TO VMs
See Chapter 2 of VMWare doc called Setup for Microsoft Cluster Service Update 1 Release for ESX Server 3.5… (vi3_35_25_u1_mscs.pdf)
1. With the VMs off, add HD to VM, but choose SCSI (1:0) which will create a new SCSI Controller
2. On SCSI (1:0), change to LSI logic, and set to virtual

SWAP OUT PHYSICALS WITH VMs
Steps are similar to restoring a failed cluster disk as laid out in MS kb280425
1. Failover cluster to Physical Node1
2. Turn off Physical Node2
3. Bring on-line Node2 VM
4. If needed, in the Windows OS MMC, rescan the disks to see the Quorum shared drive. Then format the drive and assign the same drive letter as the old Quorum drive.
5. Use Robocopy (with the /SEC trigger) to copy QUOROM drives from Physical Node1 to Node2 VM.
6. From Windows 2000 resource kit, use DUMPCFG to get the disk signature of the physical Quorum drive from one of the physical nodes
7. From the VM, overwrite the signature with dumpcfg command –
a. dumpcfg -s <signature ID> <disk number>
ex:
dumpcfg -s DD9C59B4 2

8. Shutdown Physical Node1
9. Restart cluster services or the Node2 VM… if all goes well the cluster should come up
10. Bring online the Node1 VM.
11. Test failover to Node1 VM.
12. Install VMWare Tools VSS if desired on boxes, but snapshots are not possible on VMs with SCSI adapters set to virtual

TROUBLESHOOTING AND ISSUES EXPERIENCED
VMWare Tools VSS install fail.
Since part of the cluster involved MSDTC, the VSS option would fail. Part of the fix was to relaunch Add/Remove Programs à Install Windows Components and just run through the Wizard without making any changes. This forced to VM to reset the COM+ and MSDTC configuration. When I installed the VSS component, I did it on the machine that the cluster was running on. (+Search VMWare Communities for _Error: 1722 for VMWare Tools Installation_)+. Installing VSS is moot since snapshot will not work with SCSI controller set to Virtual.

Cluster Services still fails to start properly and quorum drives are unavailable for access.

Through trial and error and dealing with multiple quorum drives… one would work, the other would have data disappear so not all cluster services would come up properly. It was necessary to reformat a quorum drive and recopy the contents, which required turning off the cluster service and the usually hidden cluster disk device. This process is laid out in the last section of the MS KB article 280425.

Where the heck do I get DUMPCFG?!?!!

Looks like it is no longer part of the Windows 2000 resource kit. You can grab it from www.dumpcfg.com

nice work. I'll convert to document so it comes up higher in search results.

This document was generated from the following thread: Import a Physical Microsoft 2003 Cluster ( MSCS ) to ESX 3i Server

VMware Converter 4.0 Standalone Public Beta Announcement

Fri, 14 Nov 2008 02:44:38 GMT

Copied below is the email that is going out to announce the public beta for Converter 4.0.
Follow the instructions to register for the beta and participate.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

VMware Converter 4.0 Standalone Beta Invitation

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hello,

Thank you for your interest in VMware(R) beta programs. Our upcoming release
of VMware Converter 4.0 Standalone product includes many exciting
enhancements that our customers have been requesting including P2V support
for Linux and Win 2K8 sources, hot cloning enhancements as well as workflow
automation enhancements. We are certain you will find participation in this beta
program a valuable experience. We are looking forward to working closely with
you during this beta program.

As part of this beta, we request you to extensively test several areas of feature
enhancements including P2V support for Linux and Win 2K8 sources, hot
cloning enhancements as well as workflow automation enhancements. Your
active participation in this beta program is critical. We appreciate and value
your efforts to install upon downloading the software and actively provide us
with your valuable product feedback.

~~ Getting Started ~~
If you already have a VMware store account, please follow the link below to
gain access to Converter 4.0 beta software, documentation and join the
Converter 4.0 beta community.

http://www.vmware.com/publicbeta/conv4-beta

If you don’t have a VMware store account, please follow the link below to create
a VMware store account, gain access to Converter 4.0 beta software,
documentation and join Converter 4.0 beta community.

http://www.vmware.com/publicbetanew/conv4-beta

~~ How to Provide Feedback ~~
Your active feedback is much appreciated. Please provide your feedback through
the Converter 4.0 beta community by:

Filing Support Requests (SRs)
Participating in Converter 4.0 Beta Forum Discussions on VMware communities site
Responding to surveys on Converter 4.0 Beta Forum

~~ Support Requests (SRs) ~~
File all issues that you find as Support Requests (SRs), even if you report them to
VMware by other means. SRs should include log files wherever applicable.

Thank you for your participation.

Sincerely,
The VMware Beta Program Team

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This document was generated from the following thread: VMware Converter 4.0 Standalone Public Beta Announcement

Import VMC file -> "VPC Config file could not be parsed"

Thu, 09 Oct 2008 12:35:36 GMT

If you are getting the error ("VPC Config file could not be parsed") while trying to convert the Microsoft Virtual PC Image VMware Converter.

Relevant log errors will look like this:

(2008-05-21 16:24:25.250 'P2V' 536 error) (task,295) Task failed: P2VError IMPORT_SOURCE_VPC_CONFIG_FILE_PARSE_ERROR()
(2008-05-21 16:24:25.250 'P2V' 536 verbose) (task,339) Transition from InProgress to Failure requested
(2008-05-21 16:24:25.250 'P2V' 536 verbose) (task,388) Transition succeeded

Resolution:

Install MSXML 4 and attempt the conversion again. You should be able to parse the file with this version of MSXML.

Success Stories:

Wow! Installing MSXML 4 solved my problem! Thanks guys!

MSXML4 worked for me too. Thanks guys!
BSV

MSXML 4 fixed the issue for me as well. Thanks!

MSXML 4 fixed it for me too, but would have been nice if vmware reported a more user-friendly/precise error message. Installing MSXML4 is not the first thing end-users think about when seeing "VPC Config file could not be parsed"...

This document was generated from the following thread: Import VMC file -> "VPC Config file could not be parsed"

Task failed: P2VError UFAD_SYSTEM_ERROR(unknown internal error)

no_replies@vmware.com — Fri, 26 Sep 2008 21:05:30 GMT

I've tried like mad convert a win2k server to virtual and I'm getting nowhere. I've defragged, chkdsk'd, disabled services, etc. I'm still getting this error. Finally, I thought I would ask the experts. So, what do you say guys. Can you help the helpless?

VMware Converter - NFC Errors and Specific Fixes

Wed, 10 Sep 2008 16:17:28 GMT

thread:id=167534 - Getting some "NFC ERROR" messages when converting a VMWare Server VM to ESX3i (Dell PowerEdge 2900)

[NFC ERROR] NfcNetTcpWrite: bWritten: -1
[NFC ERROR] NfcNet_Send: requested 272, sent only 4294967295 bytes
[NFC ERROR] NfcFileSendMessage: hdr send failed:
[NFC ERROR] Network error -- Failed to send header message
[imageProcessingTaskStep,194] BlockLevelCloning::task{11} step "copy local->remote" destroyed

1. Disabled all TOE options on the Broadcom NIC on the Dell PowerEdge 2900 that was the host vmware server. (TOE has caused me sooo many problems in the past, I believe this is what fixed it.)
2. Setup second VMFS Volume to hold larger file sizes (2mb = 512GB max file size in this case)

How to disable TOE for Broadcom cards on Dell servers here: http://support.dell.com/support/topics/global.aspx/support/dsn/en/document?c=ca&dl=false&l=en&s=gen&docid=395096AA3480EFFFE040A68F5B28437E&doclang=en (These seems to be the most problematic cards of all with respect to TOE)

Step-by-Step Explaintion of a X2V with VMware Converter

Fri, 15 Aug 2008 12:22:25 GMT

I have a P2V guide that I've wrote for my client and handed over to them using same methods listed on http://www.vmware-land.com/ site which is very precise. Basically follow the standards and you should be fine, just document and do screenshots of each step and put it in a technical form than you're solid with complete P2V guide.

You can follow steps below or read more details on VMware P2V Guide can be download on http://www.vmware.com/ site.

Converter Best Practices

Found this in the recently posted "Server Migrations with VMware Converter" presentation from VMware TSX and modified it based on my experiences http://www.vmware-tsx.com/download.php?asset_id=48

1. Agent Installation Location

Locally: Install Converter and agent directly on source machine if converting directly into ESX Server
Remotely: Connect to source machine over network to install agent

2. Agent Installation

Use local administrator account
Avoid domain accounts that have restrictive policies
Allow reboot for Windows NT 4.0 and 2000 sources

3. Machine Preparation

Do not deactivate services or harden security

Workstation service
Server service
TCP/IP NetBIOS Helper service
Volume Shadow Copy service (Windows 2003 or XP)

Ensure sufficient free disk space (at least 200MB)
Mirrored or striped volumes across multiple disks should be broken
Dynamic disks with utility partitions should use cold cloning
Disable Windows Simple File Sharing (Windows XP only)
Disable anti-virus software
Defrag hard disks
Shutdown any un-needed Windows Services
Clean-up any temporary files and un-needed data
Run chkdsk
Keep users off if possible
Power off VM if not using hot cloning
VCB VM exports need editing prior to import

Edit virtual disk filenames inside .vmx
Rename filenames for .vmdk files to match those listed in .vmx
Edit index .vmdk file to change references to span files

4. Network Preparation

Open TCP/UDP ports 139, 445, and 902 (Converter 3.0.0) or 443 (Converter 3.0.1)
Open network ports between source and destination

Alternative is to create a VM visible to source, copy VM files to location visible to destination, and import VM

Use FQDN to connect to both source and VI3

5. Converter Preparation

Run on OS greater than or equal to source if source is

VM and powered off, or
Symantec Livestate System Image

6. Cloning

Starter edition limitations and workarounds

Cannot remote hot clone directly into VI3

- Workaround 1: install Converter on source machine
- Workaround 2: select standalone VM as destination, and then import VM to VI3 using two steps

Cannot run multiple tasks concurrently

- Workaround: run multiple copies of Converter

Cannot cold clone

- Workaround: create new VM, use third-party cloning application such as Ghost, and run Converter configure

Do not resize volume for fastest clone speed (block-level copying)
Resize volumes if source disks have inefficient utilization (resorts to file-level copying)
Use cold-cloning disk-based cloning (not volume-based) for non-Windows systems
Use hot cloning for Windows NT 4.0 systems to avoid NTFS upgrade
Destination needs to be writeable

7. Configure

Avoid cloning utility partitions
Check partition numbers in boot.ini
Automatic "Install VMware Tools" option is only available for ESX Server VMs

8. Clean-Up Prior to Power On

Edit VM settings according to desired goal

Number of vCPUs
Add/Delete USB devices
Add/Delete Serial and parallel devices
Remove Floppy drive if not needed
SCSI controller type (BusLogic vs. LSI Logic)

OEM source may require license activation

SMBIOS.reflectHost = "TRUE" in .vmx may avoid reactivation
Requires destination host to have same hardware

9. Clean-Up After Power On

Detect hardware

VMware Tools installation may hang if hardware not detected

Allow reboots to occur

Detect hardware and VMware Tools installation

Verify HAL and change if necessary
Remove non-present old hardware

CMD prompt type set DEVMGR_SHOW_NONPRESENT_DEVICES=1
Next type DEVMGMT.MSC and select Show Hidden Devices
Delete any old grayed out non-present hardware

10. Guest Troubleshooting

Blue screen after powering on

Start Windows in Safe Mode and uninstall hardware-specific applications or services
Attach VM to "Helper VM" to remove hardware-specific drivers or to correct the boot.ini

No keyboard/mouse

Select Workstation/Server VM instead of ESX Server, then import VM to ESX Server
Use PS/2 keyboard/mouse on source

Display problems

Uninstall PC Anywhere prior to installing VMware Tools

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant

Converted Solaris image panics "cannot mount root path"

Thu, 14 Aug 2008 12:14:51 GMT

This document was generated from the following thread: Converted Solaris image panics "cannot mount root path"

Please see the attached picture, as it explains the repair process after a cold migration of a Solaris 10 system to a SCSI based virtual machine.

VMware Converter - Summary of Snapshot Errors and Fixes

Wed, 06 Aug 2008 20:18:14 GMT

For Any Conversion:

Disable any diagnostic partitions partitions
Partition is FAT instead of NTFS (upgrade to NTFS)

For VSS Based Conversions (XP/2003):

Converter not installed/run as admin (reinstall)
Converter not installed to C:\ (reinstall)
"MS Software Shadow Copy Provider" from Service.msc (in the case of XP) is disabled or replaced (by another VSS backup software) ... remove other software and enable the service
"Volume Shadow Copy" ensure that it is enabled
Check for VSS errors in the System's Event Log (eventvwr) - troubleshoot these, and you should fix it (example: http://support.microsoft.com/kb/941956 )

For stcbasic.sys Based Conversions (2000/NT4):

Converter not installed/run as Local Admin (reinstall)
Converter not directly installed to C:\ (reinstall)
chkdsk the drive for errors on a reboot

VMware Converter and Acronis True Image Server 9.1

Thu, 19 Jun 2008 13:59:46 GMT

When attempting to utilize Converter, 3.0.3 Build 89816, I get the following error when attempting to read the Acronis .tib file: "Unable to determine Guest Operating System".

Any assistance would be highly appreciated.

VMware Converter and Acronis TrueImage Echo 9.5

Wed, 18 Jun 2008 17:12:59 GMT

Update:

Converter 4.0 Beta does support newer versions of Acronis

Release Notes:
http://communities.vmware.com/viewwebdoc.jspa?documentID=DOC-7860&communityID=2807#interop

Acronis True Image Echo 9.1, 9.5, and Acronis True Image 10, 11 (Home product)

Beta Site:
http://communities.vmware.com/community/beta/converter/

Any problems with the TIB conversion process should be posted in the Beta Forum specifically.

##########################################################################################

Acronis True Image Echo 9.5 is not supported in the current releases of VMware Converter. This is listed as a feature request for a future release of the Converter product. Acronis TrueImage 9.1 is supported as of the 3.0.2 release.

In the mean time; the following steps are possible with some versions of Acronis Echo, and will be able to create a new VM from a TIB file:

1 - In Acronis, browse existing backups
2 - Export it as a VMware (ESX Server) VMDK file to a temporary location
3 - Upload/Move the .vmdk files to their final storage destination
4 - Create a new VM, and use this existing VMDK as the disk
5 - Attempt to power on the new VM.

NOTE: If the power on fails with any errors, run the 'Configure Machine' option of Converter against the virtual machine, and try to power it on afterwards. If errors still persist, screen capture the failure message to attach to a forum post or VMware Support Request.

Successful Physical to Virtual P2V conversion of Linux boxes with VMware Converter

Fri, 06 Jun 2008 13:18:45 GMT

For those you who are looking for the comprehensive details steps of how to P2V a linux box with VMware Converter.

Pre-requisites: Have the Linux installation Boot CD1 handy. You should purchase VMware Converter Enterprise license.

1. Download VMware Converter Enterprise latest version and burn it to the CD. I used version 3.0.2 update 1.
2. Boot up with the above VMware Converter CD on the physical Linux box.
3. Let the WinPE load up and watch for the Network adaptor settings screen. Make necessary changes such as IP addressing.
4. Finally you should see the VMware Converter screen where you can import the machine.
5. Click on Import machine button and follow the steps.
6. Important Make sure you select all disks and no resizing during the import process.
7. If all the information is entered correctly, it should start importing to ESX/VC.
8. It will create a VM on the selected ESX server.
9. In my case it failed at 97% where the error occurs at customization steps (which I did not configure for) but after successful copy of the local disks.
10. Go to the ESX server where the imported VM resides. Edit the settings.
11. In the VM's settings, check any irregular settings which might appears. In my case, I had to change the OS type of VM from other 32bit to REHL 4.
12. When the VM is powered up for the first time as soon as P2V has finished, kernel panic will occur and it is just as expected.
Steps to fix the kernel panic on the Linux VM
13. Boot up with the bootable Linux installation CD 1. If it doesn't boot from the CD, you may have to change the VM's setting to go to the BIOS setting on the next boot so that you can change the boot sequence.
14. At the boot: prompt type Linux rescue and hit enter.
15. It will search for the Linux partition. In my case, it could not find the hard disks. So, I had to go back to VM's setting to change the BusLogic SCSI controller to LsiLogic.
16. After changing to LsiLogic controller, Linux installation image was able to find the Linux partitions on the VM.
17. The system will give you opportunity to mount the root file system. At the linux prompt, type: chroot /mnt/sysimage and hit enter.
18. It will get you back to the prompt. Now at the prompt type: kudzu and hit enter.
19. It will ask you to remove old hardware and detect and install new hardware. Follow the instructions.
20. After exiting from Kudzu, at the prompt type: ls /lib/modules and take note of the version/image. For instance, your active linux version is 2.6.9-5.ELsmp. Take note of it.
21. After that you will need to make new RAM disk as follows.
22. Type /sbin/mkinitrd -v -f /boot/initrd-2.6.9-5.ELsmp.img 2.6.9-5.ELsmp
23. Reboot.
24. After the reboot, it should successfully boot up without any kernel panic.
25. If you still see the kernel panic, then go back to step 20 and find the correct module and repeat the steps 22 & 23.
26. After you have booted the system successfully, determine if it is working as expected.
27. Install VMware Tools.

The steps from 13 to 24 should take about 20-30 minutes. This procedure should be the same for most Linux distributions. Hope it will help on your P2V of Linux boxes.

VM Converter

Wed, 28 May 2008 23:06:42 GMT

BaseLibs' 130821040 info] NFC DEBUG

Converter and Windows activation

Fri, 08 Feb 2008 13:15:52 GMT

Hi,

I'm running my ESX 3.5 during the 60 days trial mode, and during this period I need to test our main servers in VM mode. For this reason I donloaded VMWare Converter 3.0.2u1 and converted two Win2003 server. But at the en of the job I was unable to login onto the new VMs because windows "must be activated". Is there a way to perform the conversion by exactly cloning the two systems, without asking for activation ? This conversion is for test only, so I cannot dismiss the real server by now. What I would like to do is convert the real server comlletely, keeping the same names, IP, etc, then switch off the real servers, power on the VMs and see if all goes ok. So, I will not run the real and virtual machine at the same time, but I need to keep the real servers ready and activated.

Is there a solution for this issue ? Thanks and bye, Stefano

i bet your physical OS is an OEM license. If so, boot the vm with the OS disc, then run a repair on the os and enter a volume license key

Use the customization option to invoke Sysprep. This will allow you to enter in a different license.

If your original license was an OEM license, then you're stuck. You can't swap in a volume license key when the original installation used OEM media.

yes you can swap an oem license for a volume license. i have done it at least 10 times. once you get the oem server converted, boot the vm with the volume license cd, run a repair on the OS and change the key there. it has worked everytime for me

That's good to clarify that you mean going through a repair process. What I meant was when Windows requires a reactivation, you can't put in just any license key-- if it was originally an OEM license the dialog won't take a volume license. Doing a repair, or in an extreme case, a reinstall, can lead to some items potentially changing on the system, unlike a standard conversion using Converter.

Hi,

please can you explain me wich command to give once I enter the recovery console ? I didn't find any in the help list.

Thanks, Stefano

dont go to the recovery console.

just do it like a fresh install it will find the previous OS install and run a repair

Hi,

but if I perform a fresh install and choose the same partition/folder of the present win installation, the installer warns me that the present installation will be deleted, together with "My Document" folder. I tried to go on pressing the "L" key (accepting the deletion) and in fact I got a completely new VM, with the old OS destroyed, wich was not what I was looking for. Fortunately I had a shapshot.

Maybe I'm missing something... please can you explain me step by step your procedure ? Thanks.

oh yeah u missing something

boot to the OS cd

welcolme to setup press enter

press f8 at license agreement

then at the next screen hit r and just let it do its thing to windows starts to load.

so thats all it is

Umhhh... that's the issue: after F8 (license agreement) I have no "hit R" choice, instead I have a screen where to choose which partition to install in. Then I select C: (where is the old Win2003) and in the nwxt screen I'm warned about another system installed being overwritten. I can only select Continue (C) or Cancel (ESC). If I go on, I'm propted how to format the C: partition ! I do NOT format it, then the last screen asks whether delete the content of C:\WINDOWS directory, or choose another dir. If I select Delete (L) I get the old installation destroyed.

I'm using a Windows Server 2003 Enterprise Edition disk.

i do too use w23k ent

This document was generated from the following thread: Converter and Windows activation

App' 6756 error client,164 Rethrowing MethodFault sysimage.fault.OsVersionNotFound

Mon, 10 Dec 2007 11:15:57 GMT

5 --2007-12-08 13:01:47.117 'App' 6756 error-- client,164 Rethrowing MethodFault sysimage.fault.OsVersionNotFound:
5 --2007-12-08 13:01:47.117 'App' 6492 error-- importSource,357 Unable to read OS info from system disk: sysimage.fault.OsVersionNotFound
5 --2007-12-08 13:01:47.117 'App' 6492 error-- imageProcessingTaskImpl,552 VmiQuerySourceInfoTask::task{4}: Image processing task has failed with MethodFault::Exception: sysimage.fault.UnableToDetermineGuestOs
5 --2007-12-08 13:01:47.117 'App' 6492 verbose-- imageProcessingTaskImpl,154 VmiQuerySourceInfoTask::task{4}: SetState to error
5 --2007-12-08 13:01:47.164 'App' 6492 verbose-- disposable,122 object explicitly disposed: VmiQuerySourceInfoTask::task{4}
5 --2007-12-08 13:01:47.164 'App' 6492 verbose-- imageProcessingTaskImpl,123 VmiQuerySourceInfoTask::task{4} being destroyed
--2007-12-08 13:02:08.868 'App' 3756 verbose-- CloseSession called for session id=BD1E2F94-B2A8-475A-B9A0-A53748C37F51
--2007-12-08 13:02:08.868 'VmdbAdapter' 3756 verbose-- Removed vmdb connection /db/connection/#5/

convert VMware Server VM to ESX 3.0.1 VM

Sun, 18 Nov 2007 23:23:53 GMT

Method 1 Vmware Converter running directly on Vmware Server (Cold clone)

* Install Vmware Converter on to the Vmware Server and reboot if prompted

Shutdown the VM to be converted
Run Converter and select Import Machine
Click Next at the Welcome screen and Next again at the Source screen
Select Standalone virtual machine, backup or disk image as your source and click Next
Browse to your VMs vmx file and click Next
Select either Import all disks and maintain size or Select volumes and resize to save or add space, select your volumes and enter a new disk size if necessary and click Next
Click Next at the Destination screen
Select VMware ESX Server or VirtualCenter virtual machine as your destination and click Next
At the destination login screen enter your VC/ESX server name and login credentials and click Next
Enter a Virtual Machine name and folder and click Next
Select a Host/Cluster and click Next then select a Datastore and click Next
Enter your NIC information and click Next then click Next again at the customization screen
Click Finish when it completes
Edit your new VMs settings and remove any extra hardware if not needed, ie. USB devices, serial and parallel devices, Floppy drive and change the SCSI adapter to LSI Logic if needed
Power on your new VM and uninstall VMware tools (VMware server version)
Restart server
Remove old virtual machine hardware
o Open CMD prompt and type SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and then DEVMGMT.MSC
o Select Show Hidden Devices from top menu
o Remove old greyed-out non-present hardware, ie. old processor, disk drives, IDE/SCSI controllers, storage volumes, etc.
Reboot and install VMware tools (ESX version) and you are finished

Method 2- Vmware Converter running directly on Virtual Machine (Hot clone)

Install Vmware Converter on to the Virtual Machine and reboot if prompted
Run Converter and select Import Machine
Click Next at the Welcome screen and Next again at the Source screen
Select Physical Computer as your source and click Next
Select This local machine and click Next
Select either Import all disks and maintain size or Select volumes and resize to save or add space, select your volumes and enter a new disk size if necessary and click Next
Click Next at the Destination screen
Select VMware ESX Server or VirtualCenter virtual machine as your destination and click Next
At the destination login screen enter your VC/ESX server name and login credentials and click Next
Enter a Virtual Machine name and folder and click Next
Select a Host/Cluster and click Next then select a Datastore and click Next
Enter your NIC information and click Next then click Next again at the customization screen
Click Finish when it completes
Edit your new VMs settings and remove any extra hardware if not needed, ie. USB devices, serial and parallel devices, Floppy drive and change the SCSI adapter to LSI Logic if needed
Power on your new VM and uninstall VMware tools (VMware server version)
Restart server
Remove old virtual machine hardware
1. Open CMD prompt and type SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and then DEVMGMT.MSC
2. Select Show Hidden Devices from top menu
3. Remove old greyed-out non-present hardware, ie. old processor, disk drives, IDE/SCSI controllers, storage volumes, etc.
Reboot and install VMware tools (ESX version) and you are finished

This document was generated from the following thread: convert VMware Server VM to ESX 3.0.1 VM