While converting a Server 2003 server to an ESX 3.5 server I received this message after 95% Complete. Error Reconfiguration failed. With a status of: FAILED: Unable to find the system volume, reconfiguration is not possible.
I'm using VMware vCenter Converter Standalone 4.0.1
Anyone run into to this problem and find a solution?
Attached is the Log file.
what does this error mean:
Unable tp locate the required Sysprep files. Please upload them under c:\documents and settings\all users\application data\vmware\vmware vcenter converter standalone\sysprep\svr2003 on the converter server machine
I get this error when I am trying to convert a physical box which is running MS Win2K3 terminal services.
thanks for your help
I started a P2V conversion on a W2k3 SP2 Enterprise Server. It got about 23% done and failed with FAILED: An error occurred during the conversion: 'converter.fault.FileIOFault'. Attached are the logs from the vmware standalone converter. I am converting this to a ESXi 5.5.1 server. I am running a defrag on the disk and then will do a check disk once that is completed. I found another artical that referenced this error but I do not see anything in the log about bad blocks so it may not be related. Any and all help would be greatly appreciated.
The drive is a single partition with the C: drive being 837GB NTFS.
Anybody has done P2V Migration Windows 2003 server, running Documentum Indexing Server, iTRACK application
Customer claims they tried it, and if failed; reason unknown.
Hi all
i have Debian based linux pc i need to do P2V for my poc ,i need your help to complete this task .thanks in advance !
We have 3 ESXi 5.5 hosts with only about 5 VMs. One of the VMs has a Windows 2008 x86 server guest OS. The server has a C and a D drive. The C drive is 300 GB with about 125 in use. The D drive is about 600Gb total and almost half full. But for some reason this server is consuming about 1.8TB. When I start the V2V, it lets be select a minimum size of 137 or so for drive C, so I select about 200GB. But then the D volume gives me a minimum of some huge amount, much larger than the capacity of the disk. The VM was created by exporting a backup from Dell AppAssure (which I had tested previously and it had worked fine or so it seemed). I don't know why, but for some reason when I exported the server to the ESXi host, it took up 1800GB total. And whatever the issue is, it seems to only affect the D volume. Remember in the V2V, it let me pick a reasonable value to resize C to, but when I tried to resize D, (I wanted to select around 600GB), the minimum it let me select was some absurd amount like 1500 GB. I do not know if AppAssure caused it or if it had something to do with the physical server. Has anyone ever seen or heard of anything like this? I will post anything else I find out... I would be a lucky dog if someone could help bail me out on this one. Thanks in advance!
Sam
P.S. Upon further inspection, on the W 2008 guest OS, if you look in "Computer", it shows the 2 disks and their respective capacities - C - 300, D - 600 (roughly). But if you open Disk Management, it shows C (disk 0) to be 400 GB and D to be around 1.5 TB. I believe when it was a physical box it had 4 1TB SATA disks in a RAID 10 array. So it would have had a couple TB total capacity. Not sure how it got like this but it sure is wasting a ton of space. Not sure how to fix it but I might have to convert it back to Physical and then back to virtual. Again, huge thanks for any suggestions.
I need to get a OVA file onto vSphere. Using Converter would seem to be the most direct approach,
but it appears Converter Standalone 4.3 and later no longer supports OVA as a source.
Any ideas as to why support for OVA as a source was dropped from Converter Standalone?
Aside, it is nice to see Converter 5.5 now supports Microsoft VHD.
hi there,
Have been trying to p2v a win2003 sbs server but it seems to get stuck on 82% - staying there for a couple of hours.
Can anyone help me out with this?
Cheers,
Al
I have a question regarding the feasability and support (from vmware) of P2V'ing a windows 2003 box running SQL 2000. Now here is the kicker. The sql databases and much of that data lives on the SAN which is accessed via iscsi initiator software (this is not my set up).
Please tell me the dangers of doing this. I know that I would shut downt the sql services, unmount that LUN and just p2v the server itself. What issues will that present when reconnecting iscsi initiator on the virtual side?
I have tried to convert a physical disk with the program and every time I try it fails with the same error, FAILED: A general system error occurred: SQL_CANTOPEN:
unable to open database file I have tried over 10 times and always get the same error. It usually failed after a few % but has failed at other times, once at 97%. I have tried with networking turned off, rebooted the machine, ran chkdsk on both the machine and external drive. the drive is under 700gb and the disk I'm trying to install the image on is 932gb free.
any suggestions? attaching error logs.
I installed successfully vConverter v5.5.1 under 64bit Win7.
During the installation vConverter installed three services which are started automatically at startup.
I prefer to have as less services running as possible. Since I use vConverter only once in a while I want
to stop these three services, then set them to "Manual" and start them on-demand if necessary.
Can I do this?
If I need them I would call them from cmdline with the commands shown in taskmanager:
D:\vConverter\vmware-converter.exe -s "C:\ProgramData\VmWare\VmWare vCenter Converter Standalone\converter-server.xml"
D:\vConverter\vmware-converter.exe -s "C:\ProgramData\VmWare\VmWare vCenter Converter Standalone\converter-worker.xml"
D:\vConverter\vmware-converter-a.exe -s "C:\ProgramData\VMware\VmWare vCenter Converter Standalone\converter-agent.xml"
Matt
Hi all
I just checked the VM Converter to virtualise a Win2k8 Server . My problem is the physical Machine is not connected to the Network where the Hypervisor is. So I cannot create the VM on the fly.
Is there a solution to create the files of the server on a external drive connected to the server, take it with me and import the machine at the Hypervisor?
regards Ron
Hello,
after an alleged successfull (Converter Standalone finishes without errors) P2V Conversion of a Windows Small Business Server 2008 the VM will not start. The source server has two physical harddrives.
The german error message is:
Ereignisdetails:
Typ: Info
Uhrzeit: 05.05.2014 16:49:50
Aufgabendetails:
Beschreibung: Virtuelle Maschine einschalten
Fehlerstapel:
Beim ESX-Host ist ein Fehler beim Einschalten der virtuellen Maschine RCSSRV02 aufgetreten.
Das Starten der virtuellen Maschine ist fehlgeschlagen.
Einschalten des Moduls DiskEarly fehlgeschlagen.
Die Festplatte '/vmfs/volumes/52d54d75-39089066-b92d-901b0e07ec65/RCSSRV02/RCSSRV02-000003.vmdk' oder eine der Snapshot-Festplatten, auf die sie angewiesen ist, konnte nicht geöffnet werden.
Die übergeordnete virtuelle Festplatte wurde nach dem Erstellen der untergeordneten virtuellen Festplatte geändert. Die Inhalts-ID der übergeordneten virtuellen Festplatte stimmt nicht mit der Inhalts-ID für die übergeordnete virtuelle Festplatte der untergeordneten virtuellen Festplatte überein
Zusätzliche Ereignisdetails:
Typ- ID: Info
Ziel Objekttyp: ComputeResource
DataCenter Objekttyp: Datacenter
Host Objekttyp: HostSystem
Host-Build: 1331820
VirtualMachine Objekttyp: VirtualMachine
ChainId: 6985
Zusätzliche Aufgabendetails:
VC-Build: 1398495
Aufgaben-ID: Task
Abbrechbar: False
abgebrochen: False
Beschreibungs-ID: Datacenter.ExecuteVmPowerOnLRO
Ereignisketten-ID: 6985
Does anyone have a clue what may be wrong?
Thank you and best regards
Jens
Can I P2V a HP-UX server?
Hi,
I'm being stuck in a project and desperate help needed after long time of searching here and on Google... 
The Scenario
There are VMs on 2 x ESX 3.5 servers and 2 x Hyper-V servers to be migrated to 5 x new ESXi 5.5 servers. But now the new servers are installed with ESXi 5.0 as I found that VMs from ESX3.5 probably cannot migrate to ESXi5.5 directly. I installed vCenter Server 5.5 on a physical Windows 2012 server, and on the same machine I installed vCenter Converter Standalone 5.0 for the VM migration. All ESX, ESXi and Hyper-V hosts are on the same network, with old hosts having storage on a Dell MD3000 and new ESXi hosts having storage on NetApp. And plan to do in-place upgrade of ESXi 5.0 to ESXi 5.5 by Update Manager after all VM migrations successful.
Source - Hyper-V (Win 08 Server R2), ESX 3.5 Update 2
Destination - ESXi 5.0 cluster
vCenter Server - 5.5
Guest OSs : Windows 2003, Windows 2008
Requirements:
- move VMs from the source hosts to the destination cluster
- VMs preferred to be migrated online (but offline still OK if it's the only option)
- shutdown source
- bring up VMs on new hosts
The Issue
Using vCenter Converter Standalone 5.0, I can connect to the Hyper-V servers and the ESX 3.5 hosts and see the VM inventory. However when try to choose the VM to convert, an error occured :
Error : Unable to obtain hardware information for the selected machine
(as shown in attached Pic 1.jpg)
And the conversion cannot proceed further. I exported the diagnostics logs too and also attached in this thread. There is an error of "Cannot query source HW info: vmodl.fault.SystemError" in the log.
- Anyone hitted this same issue before?
- Any idea on how to solve it?
- If not, then are there any other alternatives to migrate the VMs from Hyper-V/ ESX 3.5 to ESXi 5.5?
Thanks everyone!
Calvin
As the subject notes, I'm trying to test out converting some physical systems to VMWare using Converter 5.5 Standalone. Running it on a Windows 7 system, and I'm attempting to convert a Linux system that's running CentOS6. The wizard goes through smooth, and the source information is pulls down all looks correct. The conversion starts, connects to the helper, and starts formatting the destination. Then, at 3%, the conversion fails with this error:
FAILED: A general system error occurred: connect (`192.168.8.232'): Network is unreachable connect (`192.168.8.232'): Network is unreachable connect (`192.168.8.232'):
Network is unreachable Network error. Host 192.168.8.232 key can't be retrieved. (return code 2)
192.168.8.232 in this case is the source system. It's up and running just fine, and I maintain a SSH connection the entire time, but for some reason this error keeps coming up and I'm not sure why.
The conversion prompts for the key initially when the process starts, so I'm not sure if the "key can't be retrieved" error is as result of the "network unrechable" error, or if the key error comes first before the network error. Either way, network connectivity is fine, and I'm stumped as to why it keeps failing at this point. Any thoughts?
I just noticed that the VMware download page no longer offers Converter 3.0.3
This link used to work until recently
http://download3.vmware.com/software/converter/VMware-converter-3.0.3-89816.exe
Please fix this ASAP.
At the moment the file is only available at non-vmware sites.
Thanks
Hi Support,
We have Vsphere 5.5 and trying to convert one physical machine to vm using
vmware standalone convertor 5.5 .
source server is windows 2008 r2
we are receiving following error
FAILED: An error occured while opening a virtual disk. Verify
that the Converter server and the running source machines have a network access
to the source and destination ESX/ESXi hosts
Please help me to solve the same if it’s not
the right forum to discuss this issue please guide me to the right Forum
Also find the error logs
Thanks
Anoop
Hello all,
I'm trying to run an V2V Live migration from one cluster location to another cluster location, same VCenter.
I'm using VMware Converter 5.5 Standalone client and ESX 5.5.
The job submits, but gives the error: An error occured while opening a virtual disk. Verify that the Converter Server and the running source machine have a network access to the source and destination ESX/ESXi hosts.
The conversion starts, the VM is created, but fails. I found this error in the log Unable to submit job: converter.fault.ManagedDiskOpenFault.
Anybody got any clues how to solve this?
Thanks in advance!
Best Regards,
Martijn W
I am trying to convert a Windows 2000 SP4 (SCSI attached 12GB c:\ drive, 1024MB memory) running on Microsoft Virtual Server over to VMware(Version 3.5.0 Build 123630) using VMware converter 3.0.3-89816. The conversion process completes successfully, but when I try to start the server in VMware I receive a page fault in non paged area win32k.sys BSOD. Any ideas? Thanks.