Hi all,

I just downloaded Converter last night as I want to make a VM of my XP installation to run within Windows 7 Home Premium, but it's not working.

Tried about 3 times but each time it fails at 98% with the following error:

FAILED: Unable to find the system volume, reconfiguration is not possible.

Please can someone tell me how to fix this? I've attached the log files produced.

Thanks in advance

Steven

Hi,

I'm trying to p2v a physical RHEL 5 physical server using Standalone Converter 5.0. The conversion would work fine until it reaches 95% and it bomb out with errors below. I tried this several times already and it always failed at 95% with the same errors.

=======

FAILED: An error occurred during the conversion: ''/usr/lib/vmware-converter/copyFileSystem.sh --sshClient /usr/lib/vmware-converter/ssh --user root --host 10.0.0.64 --port 22 --sourceMountPoint / --targetMountPoint /mnt/p2v-src-root/ --sshConfigFile /usr/lib/vmware-converter/ssh.conf --sourceTarOption --sparse' failed. Return code: 2; message: /usr/lib/vmware-converter/ssh -z -F /usr/lib/vmware-converter/ssh.conf root@10.0.0.64 -p 22 " tar --one-file-system --sparse -C / -cf - ." | tar --numeric-owner -C /mnt/p2v-src-root/ -y -xf - tar: ./tmp/.font-unix/fs7100: socket ignored tar: ./tmp/keyring-YYWlLJ/socket: socket ignored tar: ./tmp/keyring-9UZ5dZ/socket: socket ignored tar: ./tmp/mapping-root: socket ignored tar: ./tmp/mapping-chris: socket ignored tar: ./var/log/memcached.log: invalid sparse archive member tar: ./var/log/memcached.log: file changed as we read it tar: ./var/lib/log_daemon: socket ignored tar: ./var/named/chroot/var/run/dbus/system_bus_socket: socket ignored tar: ./var/run/dbus/system_bus_socket: socket ignored tar: ./var/run/heartbeat/register: socket ignored tar: ./var/run/cman_admin: socket ignored tar: ./var/run/audispd_events: socket ignored tar: ./var/run/acpid.socket: socket ignored tar: ./var/run/clumond.sock: socket ignored tar: ./var/run/pcscd.comm: socket ignored tar: ./var/run/sdp: socket ignored tar: ./var/run/cman_client: socket ignored tar: ./var/run/avahi-daemon/socket: socket ignored tar: ./var/run/saslauthd/mux: socket ignored tar: ./var/run/cluster/rgmanager.sk: socket ignored tar: ./var/run/cluster/ccsd.sock: socket ignored tar: ./var/run/cups/cups.sock: socket ignored tar:
Error exit delayed from previous errors

===========

10.0.0.64 is the source IP of the physical machine. I have other physical servers on the network with same/similar configuration, i have no issue with converting them.

Does anyone know whats going on here? i have checked the source machine sshd config, it all looks ok using protocol 2 only.

I have attached the Converter helper log with more info.

Thanks,

S

Hi All,

When I use Vcentrer conversion standalone to convert windows 7 PC I am getting the following error.

"Unable to find the system volume, reconfiguration is not possible"

I am using Windows 7 64 bit PC with PGP encryption.

Please help me to resolve this error.

Cheers

kumar R

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

Hello everyone,

I am trying to hot-P2V a Win8 64bit OS which came pre-installed on my new notebook (it's an OEM license so I don't have the OS installation discs and thus cannot create a VM from scratch).

Unfortunately, like many people before me, I experienced this error while reconfiguring the newly-created virtual hard disk.

I read that the cause of this problem is an inaccurate BCD configuration: VMware KB: P2V conversion using VMware Converter fails with the error: Unable to find the system volume, reconfigura…

This post states that I'm supposed to import the virtual machine to vCenter Server and repair the VM's BCD from there.

Unfortunately I do not own this software and tried to import the VM in VMware Converter and run "Configure Machine" to fix the BCD data but no, I get the same error.

I should also mention that I did NOT install VMware Tools on this VM.

I spent some time reading articles about what BCD actually is and I more or less understood WHAT to do but still need a hand on HOW to do it.

Comparing my BCD with my Control Panel --> Disk Management it looks like the partitions are laid out correctly:

the first is a Win rec. partition (400Mb), then you have the boot partition (260Mb) and then the OS partition (drive C:).

The Z: volume is merely a data partition where I put music and movies and was not included in the VM.

Finally, the D: volume is a Hewlett Packard rec. partition. - this was not included in the VM either.

The BCD says the {bootmgr} is '\Device\HarddiskVolume2', so it seems to mirror the Disk Management structure.

But I'm no expert at all so here I am, asking for help.

I am attaching VMware Converter's logs and screenshots of my Win8 BCD and Disk Management.

Apart from solving my issue I'm especially interested in understanding WHY this problem occurs so I can learn and be better prepared for the next time.

Thanks a lot for your help,

Regards.

Stef

Hi all,

I restored an image into am empty virtual machine with VMware Workstation 10. In order to make it bootable I used the VMware Converter Standalone (5.1.2, with the latest version I get same error message). I used configure machine to do it but I get an error message during execution: FAILED: Fault.ReconfigurationFault.summary.

Does anyone knows how to fix this problem?

Thanks in advance.

Vincenzo

What's the best way to remove the team after the conversion?  You can't open the Broadcom utility because no adapters exist.  If you try to remove the BASP Virtual Adapter from the device manager it says "failed to uninstall the device.  The device may be required to boot up the computer"

Hello everybody!

I wanted to shrink my DC partitions (from 2Tb used only ~150gb) with help of Standalone Converter, but when i select "source machine" (my turned off DC) and click next, i get error "unable to obtain hardware information for selected machine" (running converter as admin doesnt help). Also I'v tried to convert other machines on this host and succeed.

Can't understand what's wrong with my DC.

ESXi 5.1.0

Converter 5.5.3

Logs from my 3 attempts in attachment.

Converter 5.5.3, ESXI 6.0, P2V.  "An error occurred during the conversion: 'converter.fault.FileIOFault'"

The Job failed at 35%.  When I looked up the error it says that a HD error occurred and that I need to do a defrag.  Before I do this I want to check and make sure that 5.5.3 converter is compatible with ESXi 6.  I can't seem to find anything on this.

This is my environment:

Physical Box: IBM, Intel Dual 8c processors, 16 GB Ram, Raid 10

Virtual environment: (host)Dell r620, Intel Dual 8c processors, 64 GB Ram.  (san) Equallogic 6100, Raid 10

Thanks all, I just dont want to waste my time doing a defrag if the converter is not compatible.

Hi,

I'm having problem when converting local machine which is Windows 7 x64.

I have two disk that labelled C and D (C= System, D=Backup) and I only convert C disk.. But I got same error. I've just researched but couldnt find useful information.

Please help me.!

Error: An error occurred during reconfiguration.

Processing the reconfiguration datastore.

Updating drive letters for the destination volume layout.

Updating BCD on the destination machine's system volume.

Updating the boot sectors on the destination machine.

Completed cloning volume '\\?\Volume{df051e9e-b51d-11e5-9006-fc3fdba4269a}\'.

Starting block-level cloning for volume '\\?\Volume{df051e9e-b51d-11e5-9006-fc3fdba4269a}\'.

Completed cloning volume 'C:'.

Starting file-level cloning for volume 'C:'.

A snapshot of the source system was created successfully.

Creating a snapshot of the source system.

Task: Convert physical machine.

Hi,

I just got a new Asus laptop. I want to "virtualize" the preinstalled Windows 7 64bit OS and install linux as the primary OS.  The HD has a hidden recovery partition, then followed by the Win7 partition (and then a couple empty partition that I have been playing around with).  I tried using v4.3 as well as the v5.0.0 beta to convert it but I always get "Unable to find the system volume, reconfiguration is not possible." at 96%. The laptop didn't come with any Windows 7 disks. Does anyone have any idea what the problem is? The logs are attached.

Thanks in advance,

Mike

Hello,

I have a physical Debian 7.0 Linux system which I am trying to P2V using Converter 5.5.3.  When I select my target ESXi server, I get told:

The destination does not support EFI firmware.

How do I confirm/deny this, and/or enable EFI support on my ESXi node?

I have a server with windows server 2000 OS.I want to converter  this server become a VM in the vmware platform.How can I do this?

Hello there,

I'm trying to run a live P2V using vmware converter standalone 6.0.0 running on the actually physical machine to be converted and after selecting the ESXi 5.5 destination I get "The destination does not support EFI firmware". The physical machine is running Windows 2008 R2 standard x64 and is a System x3550 M2. Ive searched the internet but cant seem to find anyone with the same issue.

Does anyone know if there is a workaround for this issue?

Many thanks

My converter fails on 3% with the following error

Error: Unable to clone the volume mounted on '/boot' from IP

FAILED: An error occurred during the conversion: '/usr/lib/vmware-converter/copyFileSystem.sh: eval: line 125: syntax error near unexpected token `(' /usr/lib/vmware-converter/copyFileSystem.sh: eval: line 125: `echo 'z(\28*'dcn.#Z8n(' | /usr/lib/vmware-converter/bin/ssh -z -F /usr/lib/vmware-converter/ssh.conf root@IP -p 22 " tar --one-file-system --sparse -C '/boot' -cf - ." | /bin/tar_1.28 --numeric-owner --delay-directory-restore -C '/mnt/p2v-src-root/boot' -y -xf -' /usr/lib/vmware-converter/copyFileSystem.sh: line 125: warning:

syntax errors in . or eval will cause future versions of the shell to abort as Posix requires /usr/lib/vmware-converter/bin/ssh -z -F /usr/lib/vmware-converter/ssh.conf root@IP -p 22 " tar --one-file-system --sparse -C '/boot' -cf - ." | /bin/tar_1.28 --numeric-owner --delay-directory-restore -C '/mnt/p2v-src-root/boot' -y -xf - (return code 1)'

i tried the hostname fix etc but it keeps failing.

no idea what to do

I'm trying to convert a RHEL4 server and am getting 'Unable to query the live linux source machine' after I push Next on the credentials screen.

I can use putty from this server to logon as the root account.  Any Ideas ?

The following is in the log files:

Testing client connection to agent

Reusing existing agent connection

Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

Testing client connection to agent

Reusing existing agent connection

Testing client connection to agent

Reusing existing agent connection

Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

Cached agent connection is for a different source, recreating connection

Creating SOAP stub adapter over pipe:
.\pipe\vmware-converter-agent-soap

Impersonating hitsar

Testing client connection to agent

Reusing existing agent connection

Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

Cached agent connection is for a different source, recreating connection

Creating SOAP stub adapter over pipe:
.\pipe\vmware-converter-agent-soap

Impersonating hitsar

Testing client connection to agent

Reusing existing agent connection

Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

I'm trying to do a really simple conversion from Windows Server 2008 R2 SP1 to ESXi machine version 8. It seems to copy okay, but on the first VM boot it does an NTFS disk check and finds a bunch of errors.

All major services are stopped (APC Powerchute, Windows Deployment Services, Backup Exec Agent) and the antivirus uninstalled. chkdsk has been run on the source hardware and found no problems.

And yet after the migration I see this on first boot:

Checking file system on C:

The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue.

Windows will now check the disk.                       

CHKDSK is verifying files (stage 1 of 3)...

The attribute of type 0x80 and instance tag 0x3 in file 0xe08c has allocated length of 0x1fec00000 instead of 0x1fecc0000.

Deleting corrupt attribute record (128, $J) from file record segment 57484.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x11a for possibly 0x1 clusters.

Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xe120 is already in use.

Deleting corrupt attribute record (128, "") from file record segment 57632.

  199936 file records processed.

File verification completed.

  885 large file records processed.

  0 bad file records processed.

  0 EA records processed.

  104 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...

  262480 index entries processed.

  Index verification completed.

  0 unindexed files scanned.

  0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...

  199936 file SDs/SIDs processed.

Cleaning up 8 unused index entries from index $SII of file 0x9.

Cleaning up 8 unused index entries from index $SDH of file 0x9.

Cleaning up 8 unused security descriptors.

Security descriptor verification completed.

Inserting data attribute into file 57632.

  31274 data files processed.

CHKDSK is verifying Usn Journal...

Creating Usn Journal $J data stream

Usn Journal verification completed.

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.

  70936575 KB total disk space.

  50582732 KB in 152611 files.

    97136 KB in 31274 indexes.

        0 KB in bad sectors.

    269927 KB in use by the system.

    65536 KB occupied by the log file.

  19986780 KB available on disk.

      4096 bytes in each allocation unit.

  17734143 total allocation units on disk.

  4996695 allocation units available on disk.

Internal Info:

00 0d 03 00 59 ce 02 00 ac 1e 05 00 00 00 00 00  ....Y...........

d1 00 00 00 68 00 00 00 00 00 00 00 00 00 00 00  ....h...........

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.

Please wait while your computer restarts.

There is absolutely NO WAY that I am going to use this resulting conversion as our primary organization file server. Such corruption of the NTFS partition data is completely unacceptable. I have no way of knowing what "file record 57484 / 57632" are and if they are critical to the operation of the server.

Though I expect I already know what the problem is, and I cannot solve it by using VMWare Converter running on the Windows I'm trying to migrate.

Trying to copy a file system while it is in use is just inviting disaster because as you're copying data, something before or after wherever the copy is occurring may change so that the final copy result ends up being corrupted.

The only way to really prevent this mid-copy data corruption is to copy the partitions when they are not in use.

I have been working all day on a single machine standard and clean MS Windows 7 64bit enterprise.

This OS is not uncommon but spells a world of trouble for VMWare Converter standalone 6.0.0.

To the point that makes me wonder if this production software. I'm just posting in the many many error messages I have seen throughout the day.

I managed to find workarounds for most of the issues untill I hit

FAILED: Unable to create '\\.\vstor2-mntapi20-shared-C37ABC700000F015000000000C00

This turns out to be a show stopper. There is no way of fixing this.

Which made me wonder. What OS is VMWare Converter supposed to support? It is not MS WIndows 7 for sure.

Is this maybe only for server OS software? Not desktop OS.

Insufficient permissions to connect to '192.168.1.142\ADMIN$'

A specified parameter was not correct. spec.synchronizeImmediately

A general system error occurred: Unexpected element tag "converterManager" seen while parsing serialized DataObject of type converter.AgentInstanceContent at line 7, column 63 while parsing return value of type converter.ServiceInstanceContent, version converter.version.version3 at line 7, column 0 while parsing SOAP body at line 6, column 0 while parsing SOAP envelope at line 2, column 0 while parsing HTTP response for method retrieveContent on object of type converter.ServiceInstance at line 1, column 0

FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume Disk#1_Partition#5. Error: 209 (type: 1, code:

13)'

FAILED: Unable to create '\\.\vstor2-mntapi20-shared-C37ABC700000F015000000000C00

Unable to obtain hardware information for the selected machine.

Hello,

Could someone tell me how to solve this error?

Now I'm trying to convert a remote Windows XP to a virtual machine on ESXi.

The source system  type is Powerd-on machine　(remote) and its operating system is Windows XP. The destination host system is  ESXi 5.5, and the target virtual machine version is 10.

When I start to my conversion, the error "fault.ManagedDiskOpenFault.summary" occur.

I can find message below, in gui.log.

YYYY-MM-20T15:34:17.329+09:00 [06344 verbose 'Default'] Getting VIM connection to "vmhost IP address"...

YYYY-MM-20T15:34:17.329+09:00 [06344 info 'Default'] Connecting to host "vmhost IP address" on port 443

YYYY-MM-20T15:34:17.329+09:00 [06344 info 'Default'] localVersion is: vim.version.version9

YYYY-MM-20T15:34:17.344+09:00 [06344 info 'Default'] Remote version is: vim.version.version9

YYYY-MM-20T15:34:17.344+09:00 [06344 verbose 'Default'] [VimApi] Local and Remote Version are the same. Talking with version vim.version.version9

YYYY-MM-20T15:34:17.360+09:00 [06344 info 'Default'] Authenticating user root

YYYY-MM-20T15:34:17.360+09:00 [06344 verbose 'HttpConnectionPool-000011'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0

YYYY-MM-20T15:34:17.391+09:00 [06344 verbose 'Default'] VimConnectionStore stopping keepalive

YYYY-MM-20T15:34:17.391+09:00 [06344 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds

YYYY-MM-20T15:34:17.391+09:00 [06344 info 'vmomi.soapStub[11]'] Resetting stub adapter for server <cs p:066679e8, TCP:"vmhost IP address":443> : Closed

YYYY-MM-20T15:34:17.391+09:00 [06344 info 'wizardController'] FillPage()

YYYY-MM-20T15:35:51.414+09:00 [09208 error 'wizardController'] Unable to submit job: converter.fault.ManagedDiskOpenFault

YYYY-MM-20T15:35:51.414+09:00 [09208 verbose 'Locale'] Default resource used for 'ManagedDiskOpenFault.summary' expected in module 'fault'.

YYYY-MM-20T15:35:51.414+09:00 [10152 error 'ConversionState'] Submit job failed: fault.ManagedDiskOpenFault.summary

YYYY-MM-20T15:35:51.414+09:00 [10152 error 'ConverterWizardWindow'] Next/Finish failed: fault.ManagedDiskOpenFault.summary

YYYY-MM-20T15:44:48.625+09:00 [01572 verbose 'HttpConnectionPool-000003'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x03f872f0, h:-1, <TCP '0.0.0.0:0'>, <TCP '"vmhost IP address":443'>>)>; pooled: 0

YYYY-MM-20T15:47:31.361+09:00 [09800 verbose 'ConverterDataProviderImpl'] Converter::Client::Gui::Wizard::ConverterDataProviderImpl::PropertyCollectorThread: TimeoutException

YYYY-MM-20T15:50:54.196+09:00 [08832 verbose 'HttpConnectionPool-000002'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x042de330, h:-1, <TCP '0.0.0.0:0'>, <TCP '[::1]:443'>>)>; pooled: 0

Hi

Could  someone guide me on what the best methodology would be for converting  VM's from a Citrix production environment to a VMware production  environment.

Ive used the vmware converter 5 for p2v's and have  also read that it could be used for the same v2v from citrix, some  people have also advised converting the citric vm in OVF format and  importing the same onto the Vsphere environment..

Kindly advise .