It was my understanding that if you have an Enterprise Plus license for ESX, the cold clone CD was available to you with Converter, but I dont see it under the Converter downloads.
We are going to be doing some P2Vs soon and I would like to have the CD on hand just in case we need it.
Can anyone point out its secret location? 
Thanks!
Hello,
since my Windows 2008 R2 (Web Server edition) installation uses 100MB System restore partition I had to use this fix for that:
VMware KB: P2V conversion of a Windows 2008 R2 machine fails at 96%
for allowing VMWare Converter (latest 5.1) to copy also this partition but I never made it because when I've changed status od this partition to Online Converter is always stopping on connecting to Powered-on machine -> This local machine with error "Unable to obtain hardware information for the selected machine.". I've noticed in Application Windows Event log error entry which contains:
Faulting application name: vmware-converter.exe, version: 8.1.0.15346, time stamp: 0x51642354
Faulting module name: converter-agent.dll, version: 8.1.0.15346, time stamp: 0x51642321
Exception code: 0xc0000005
Fault offset: 0x00084bbe
Faulting process id: 0x19d4
Faulting application start time: 0x01ce7402f38eeb43
Faulting application path: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\vmware-converter.exe
Faulting module path: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter-agent.dll
Report Id: 7d2c66a6-dff6-11e2-ab7e-000c29da83b7
There is also informational entry:
The description for Event ID 1 from source vmware-converter-worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
vmware-converter-worker service started
When I will restart system and not make system restore 100MB partition online Converter agent is not crashing and I can perform conversion without this small partition.
Any ideas?
Regards
Hi Folks,
Having an issue while importing a Win 7 machine with min disk size (28 GB) on a ESX4 host with vCenter converter 5.0.0.
vCenter version is 4.0.
Error message is-
"Import Machine
Failed to take snapshot of a source
volume. Possible causes include not
having any NTFS volumes on
Windows XP or Windows 2003
source systems, and not having
enough free disk space."
.
There is enough free disk space on the datastore where I am trying to import.
Can anyone let me know possible cause and solution to this?
Thanks
vmrockin
I recently upgraded a CentOS 5 system to 6.4 on bare metal. I've been backing up by rsync'ing the system to both a local USB drive and a remote system's USB drive. The backup is a snapshot of the live system's filesystem, which is spread across a couple of LVM mounts (plus an LVM swap).
I'm now trying my hand at VMware and have another identical server running offsite and loaded with ESXi 5.1. It seems like I should be able to take my USB image and convert that to a virtual server on this second system. I downloaded and installed Converter but don't see any options for my situation. Do I need to take this server to the site and convert from the running server? Or is there some way to turn my filesystem snapshot into something that Converter can use? It looks like Converter can convert from a virtual filesystem, so is there some tool that can turn a snapshot into a virtual filesystem?
Hello,
In trying to do a P2V conversion I am getting a very weird kernel error. I am using the 5.1 standalone converter. The error is:
FAILED: An error occurred during the conversion: ' * got kernel major revision as ERROR:
kernel version has to be in format 2.6.*, version 2.6.32-358.6.1.el6.x86_64 is not supported (return code 1)'
I have searched and found no information on this error. I have added a screenshot, any help would be appreciated.
Thanks
Hello all,
I am usind vmWare vCenter Converter Standalone 5.0 to run a P2V on a server that is running Windows 2003. I have ran two different P2V's this 2003 server with success over the past three week. I am tryng to run another P2V on this server now. On the deploying of the agent I receive the following error "Unable to complete vCenter Converter install. Error code 1,603".
Any suggestions on how to resolve this issue?
Why would this error start now after running successfully, everything I was reading was saying to check port settings, none o those have changed.
Thanks for your help..
I am trying to do a v2v conversion with the 5.1 standalone converter on a windows 2008 r2 VM. I am doing this to shrink the system partition which was wrongly thinly provisioned at 415 gigs down to 100.
It gets most of the way through and I get an error that says "An error occurred during the conversion: "Cannot change bitmap driver's start type to SERVICE_BOOT_START, context="IncrementalConversion(job-1:0)-[52 d2 11 61 2b 43 41 85-6d if 90 5d 6f c7 94 90]", error=0'
I've looked this up on the internet and there isn't anything that I can find on this. Does anyone have any ideas what I can do?
Thanks so much in advance.
Is there any way to create a script to convert a VM at a given time (let's say, during the night, to save resources...)?
Regards
marius
We are trying to convert a Windows Server 2003 x64 SP2 machine and get this error at 98 percent,
"FAILED: Unable to reconfigure the destination virtual machine."
The only reference I see in the log file is,
"2013-07-01T16:56:55.491-04:00 [03224 error 'Default'] [task,350] [LRO] Unexpected Exception: converter.fault.ReconfigurationFault
2013-07-01T16:56:55.538-04:00 [03224 info 'Default'] [task,379] [task-1] -- ERROR -- Convert: converter.fault.ReconfigurationFault
--> (converter.fault.ReconfigurationFault) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> description = "converter.fault.FileNotFound",
--> msg = "",
--> }"
I have attached the full log. Any help would be greatly appreciated.
Hi,
Running esxi 4.1 with vcenter 4.1.0. I recently converted (vmware converter 4.3.0) two Windows 2008 (not R2) 64 bit, none of them can identify the Base Device Driver.
From what I have found on google, it mostly seem to be a problem for some specific version of vmware fusion.
I tried to apply the same tricks; do an interactive vmware tools installation but that fail with error code 1935.
Googling that showed me I need some microsoft visual studio redistributional something, but that too failed with error 1935.
All windows R2 2008 went great, and I can't seem to find a bunch of other people who have the same problem.
Anyone know anything about this?
How can it be resolved?
If not solved, what impact will the lack of the base system device driver have?
Thanks,
Hi,
Is there any way to cold clone Windows 2008 R2 machine? As far as I know there is no vmware 5.1 boot cd for cold cloning. So I've tried to use latest cold clone cd (4.1.1 - 206170). Problem is that it is able to clone my machine BUT it is created as Other-32 bit machine on esxi server and when I'm trying to start this machine this operation simply ends with blue screen. I desperately need to do coldclone and not the hot clone and I need your help. Thanks.
vCenter: 5.1.0
Standalone Converter: 5.1.0
ESXi : 5.1
I am unable to complete any P2V conversions with vCenter Standalone Converter. I get the error message "Unable to obtain hardware information for the selected machine" every time I run the converter. I have used 'Run as Administrator,' rebooted source system, and rebooted vCenter server with no luck. Any ideas will be greatly appreciated.
Thanks!
hi all
I'm having the problem on the object
I've search enought for same problems but everybody get the error while trying to convert windows server 2003 - I also found that 2008 doesn't have a boot.ini ( Boot.ini in Windows Server 2008)
So, how can i solve my problem? I don't want to create a boot.ini file with the risk to impact the server funcionality
I attach the log file
thank you all
I've tried this 4 times and it's failed every time. Converting a win2003 SP2 physical to a vm on esx 5.0 host.
Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)
Dear all,
We have an organisation who desperately want to convert a Server into VMware, however the disks are dynamic, please see image.
Can anyone suggest the best route to achieve this?
Many thanks
I try to convert my laptop running linux slackware using Converter 4.0.0 Beta :-
Converter installed on SLES 10 as guest OS on top VMware-server 1.0.4
I choosed convert machine -> powered on machine
Edit Virtual Machine name, volume to select, nic & etc.
The last step (step 4) before I can click "Finish" I got an error messages as below :
"a general system error occurred coverter.fault.SysinfoQueryLinuxFault"
I knew that slackware is not supported linux distro but just wanna give a try with this converter. Anyone here having same issue and mind to share with?
Hi, I am looking for some support wrt using the converter for converting VM's created in Hyper-V to VMware. What happens to the Hyper-V tools? Will the Data be secure? Will the drives be the same? Can someone share their experience of doing this before and what are the challenges faced.
Thanks,
Nagesh
My server gets to about 94% and fails with error 209 (type 1 code 13) . Much of my research says that it is a bad block on my disk array. I ran chkdsk and it didn't come back with any problems.
The server is a 500 GB C: running Windows 2003 server. I am trying to P2V to a C:\p2v folder on the same server. Will that even work?
I recently started using the newly released Converter 5.0.0 . I had successfully done over 30 P2V's of Windows 2003 systems using version 4.3. Immediately, I noticed two problems:
1) The average transfer rate dropped from about 100 MB/s to between 0.8 and 2 MB/s.
2) The process consistently failed following completion of C: drive cloning and starting on the D: drive.
I tried this on 5 different physical servers going to 5 different VMware ESXi 4.1 host servers and the result was always the same. I assumed it was a Network or Firewall problem and sent the Network team on a "wild goose chase" for 2 days. After they were convinced that the physical machine being P2V'd was simply not sending sufficient packets, I went back and re-installed version 4.3 and restarted the P2V transfer. This time I received an average transfer rate of 100 MB/s (50x faster) and the entire process completed successfully.
Has anyone else seen a similar problem? Any possible explanations?
Hello,
I trying to copy a vm that's on an old amd processor to another system with a newer socket amd processor using the latest vm converter standalone. I get the following error "Unable to validate the destination. Error:vmodl.fault.SystemError" the esxi 5.1 versions are the same on both servers and the difference is the older is regular SATA vs SATA raid controller on the newer system. Any help will be greatly appreciated. The VM that im trying to move over is Windows 2008 R2 64 bit.
Thanks