Hello - during install of standalone converter on a Windows 7 Pro workstation I get the following error; install rolls back, does not complete. What is causing this?

Hi guys,

Really going a little desperate here.

I have here 1 Server 2003R2 EN edition running SQL 2005 instance (1 database).

Trying to convert to VM running on ESXi 5.5.0 1623387 using 5.5 standalone converter and also the 5,1 converter.

Hardware raid, normal basic disks (C: 60GB / D: 140GB).

stopped the SQL database, ran as local administrator, used SSL and no-SSL during copy (for speed).

Made sure I had LSI logical controller.

The convertion fails at 98% with "error: Cannot open the destination virtual machine for reconfiguration"

After that I can run the task "reconfiguration" seperately and it will tell me it has succeeded on the VM.

But in both cases I only get a black screen with a solid cursor.

Weird thing is, I dont even get the BIOS when I tell ESXi that I would like to see the BIOS after the next reboot. I go straight to black screen with cursor.

I also tried ONLY converting the C: but that resulted in the same issue,

Enclosed are the 2 log files from trying to convert (using 5.5 and 5.1).

I dont really know how to read them since I see a lot of "failed" and "error" remarks.

Appreciate the help.

Hi All,

I am having issues importing any physical machines using the VMware standalone converter.  I have previously converter multiple physical machines without issues, but now the convert fails on the source system specification tab with the error "Unable to obtain hardware information for the selected machine."  I had administrator rights on all machines (Source, my machine where the converter is install and on vCenter).  When I look in the vmware-converter-worker.log I see the following. I have removed the IP's and Machine names for security reasons.

2015-01-29T08:48:39.111-06:00 [05368 warning 'Default'] Failed to connect socket; <io_obj p:0x014bc328, h:588, <TCP '0.0.0.0:0'>, <TCP '99.99.99.99:9089'>>, e: system:10061(No connection could be made because the target machine actively refused it)

2015-01-29T08:48:39.111-06:00 [05368 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:00e3b098, TCP:<machine_name>:9089>; cnx: (null), error: class Vmacore::SystemException(No connection could be made because the target machine actively refused it)

2015-01-29T08:48:39.112-06:00 [09084 info 'vmomi.soapStub[6]'] Resetting stub adapter for server <cs p:00e3b098, TCP:<machine_name>:9089> : Closed

2015-01-29T08:48:41.001-06:00 [09084 info 'Default'] [AgentManager] Install Agent on <machine_name>

2015-01-29T08:48:41.001-06:00 [09084 info 'Default'] [ufaUtilsWin32,208] Connecting to ADMIN$ on <machine_name> as <domain\user>

2015-01-29T08:48:41.032-06:00 [09084 info 'Default'] [ufaUtilsWin32,211] Successfully connected to ADMIN$ on <machine_name>

2015-01-29T08:48:42.416-06:00 [09084 warning 'Default'] [AgentDeployment] Wait install process to complete

2015-01-29T08:48:48.460-06:00 [09084 warning 'Default'] [AgentDeployment] Cannot match line Time=01/29/15 08:49:14

I can connect to the source system using RDP and the firewall is off and the UAC is off.  Not sure what else to check

Thanks in advance

I'm converting a physical Linux machine and receive the following error

{

-->    dynamicType = <unset>,

-->    faultCause = (vmodl.MethodFault) null,

-->    description = "Failed to find matching disk device for VMODL Param Disk #0, 1447909153, controller: scsi, bus ID: 0, and unit ID: 0",

-->    msg = "",

--> }

Does anyone know how I can resolve this please?

Hello,

I am trying to convert 3 very large physical fileservers into 3 virtual servers. I am using VMware Converter 5.5 and have installed it locally on each server. I am converting directly into an ESXi 5.5 host without vCenter.

Each server is about 15 TB total disk space ( >10TB consumed), but they have different disk setup.

• Server 1 has 1 C: drive, and 2 large volumes on 7,5 TB each.
• Server 2 has 1 C: drive and 8x1,9TB volumes
• Server 3 has 1 C: drive and 1 large volume on 7,5TB and 4x1,9TB

If I choose to run this with default setting (block size level copy, maintain disk size, all volumes on the same datastore) it creates the virtual machine on the ESX server and Converter reports the following task: "Task: Convert physical machnie". After a couple of minutes the newly created virtual machine on the ESX is deleted and after a few more minutes VMware Converter times out and reports the following error message:

• 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.

You would think that this is network related, but as it turns out, everything on the network/DNS side is OK:

If I choose to run the same job, but change the volume size and shrink it below 10 TB, the job runs fine! (Are there any limitations to this in Converter?) The only problem is that by doing this, it changes the copy type from "block level" to "file level". With file level copy you are not able to run synchronization afterwards, which we really need to do since this conversion will take several days and there will be a lot of changes left out if we don't synchronize in the end.

Does anyone have an idea how I could work around this?

Can anyone help with my particular issue. I am trying to convert form a running VM to another ESX server in the same vCenter. It looks like it completely copies and then gets to 91% stalled timing out on something. Below is the vmconverter logs

Task: Convert physical machine.

Starting block-level cloning for volume 'C:

Completed cloning volume 'C:'

Creating a snapshot of the source system

I have to add, the original running VM is originally from VirtualBox, but we have it running on the ESX box but using a NFS share to a storage area (Datto - Backup appliance). The VM spins up with no issues, so we ultimately want to get the NFS share converted to another ESX server, but this has to be done live as the client can not be down for more than a few minutes.

2015-11-20T01:45:32.918-05:00 info vmware-converter-worker[04212] [Originator@6876 sub=task-2] CloneTask: Agent task moid=task-4

2015-11-20T01:45:32.918-05:00 info vmware-converter-worker[04212] [Originator@6876 sub=task-2] Worker InitialSyncCatchUpTask updates, state: 1, percentage: 0, xfer rate (Bps): <unknown>

2015-11-20T01:48:07.189-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T02:15:34.844-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T02:18:07.179-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T02:45:34.827-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T02:48:07.173-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T03:15:34.808-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T03:18:07.161-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T03:45:34.799-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T03:48:07.166-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T04:15:34.792-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T04:18:07.155-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T04:45:34.784-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T04:48:07.151-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T05:15:34.766-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T05:18:07.144-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T05:45:34.765-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T05:48:07.143-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T06:15:34.753-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T06:18:07.128-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T06:45:34.742-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T06:48:07.121-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T07:15:34.732-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T07:18:07.101-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T07:45:34.737-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T07:48:07.097-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T08:15:34.723-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T08:18:07.087-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T08:45:34.719-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T08:48:07.090-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T09:15:34.716-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T09:18:07.095-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T09:45:34.707-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T09:48:07.075-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T10:15:34.700-05:00 warning vmware-converter-worker[04212] [Originator@6876 sub=task-2] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

2015-11-20T10:18:07.064-05:00 warning vmware-converter-worker[06256] [Originator@6876 sub=task-1] [WaitUntilComplete] WaitForUpdates timed out: Operation timed out

I need to convert a physical RH Enterprise Linux 5.11 physical server, using Standalone Converter 5.5. I will run the converter from a Win2008 R2 machine, pointing it at my Linux box. Here are my questions:

I have found references that say I should edit the storage of the destination VM if I am using LVM (and I am). See Kernel Panic Using VMware vCenter Converter Standalone - Uptime Through Simplicity. I don't know if this is still applicable to converter 5.5, since it supports RHEL 5.x.

- Do I need to change the destination storage to "thin" and "Basic storage", or is this unnecessary with this version of Converter? That page is from Sep 2013, which is probably an earlier version of Converter.

When converting Windows, one of the post-conversion steps is to remove "hidden" devices, which includes hidden NICs, before you can assign a static IP to the VM.

Does this apply to Linux? (I don't think so) If not, I should be able to just boot up the resulting VM; assign my static IP to eth0 (that's what it is now), and I should be good to go?

Thanks

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 used Converter to convert a Windows 7 64-bit box but am getting a 0x0000007E BSOD when trying to boot it in Player on Lubuntu 14.04. Strangely, it booted a couple of times to a login screen, though the keyboard didn't work. Shortly after booting to the login screen, it would blue screen with 0x0000007E though. Now it doesn't even get to the login screen and just blue screens with 0x0000007E immediately.

Things I have tried:

• Deleted unsigned drivers in windows\system32\drivers
• Changed HKLM\system\controlset001\services\lsa_sas\start to 0
• Verified windows\system32\drivers\lsi_sas.sys exists

Specs:

• Source/guest: Windows 7 Professional 64-bit
• VMware vCenter Converter Standalone 6.1.1 build-3533064 (Disk controller = SCSI LSI Logic SAS)
• VMware Workstation 12 Player (free) 12.1.0 build-3272444
• Host: Lubuntu 14.04 64-bit
• BSOD: 0x0000007E

I've been doing a lot of research for quite a while and have reached the end of my rope. Can anyone help?

I would like to install VMware Converter on an external USB hard disc or USB Stick and run it in various computers.

This seems to be not possible because during installation a service is installed as well.

Is there a way to (only) re-install this service on other computers as well?

or to use VmWare Converter WITHOUT this service?

or to installVmware Converter in a portable way?

Peter

Hi,

I have worked out that this must be possible because of the inclusion of converter-cli.exe with Converter 5.0.1 Build 875114, plus I've got very close but not quite close enough!  I have vCenter 5.0 and ESXi 5.0.0 hosts.

I am using the following XML and it's submitting the job to Converter with what looks like to be the correct details but fails straight away with the error:

FAILED: The source configuration file is invalid, corrupted or not recognized.

I've checked logs in the following locations but nothing gives me any clues as to what isn't quite right:

C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs

C:\Users\All Users\VMware\VMware vCenter Converter Standalone\logs

C:\Users\XXAdmin\AppData\Local\VMware\VMware vCenter Converter Standalone Client\Logs

Anywhere else I can look?

My XML file (p2v.xml):

<p2v version="2.2" xmlns="http://www.vmware.com/v2/sysimage/p2v" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.vmware.com/v2/sysimage/p2v p2vJob.xsd" xsi:type="P2VJob">
  <source>
    <hostedSpec networkPassword="domainpassword" networkUsername="domain\username" path="PHYSICALSERVER"/>
  </source>
  <dest>
    <managedSpec datastore="Datastore XXXX" folder="Temp" host="HOST1" resourcePool="" vmName="NEWVM">
      <creds host="VCENTER" port="0" type="sessionId" username="domain\username" password="domainpassword" />
    </managedSpec>
  </dest>
  <importParams diskType="VMFS" preserveHWInfo="true" removeSystemRestore="false" targetProductVersion="PRODUCT_MANAGED">
    <nicMappings/>
    <diskLocations/>
  </importParams>
  <postProcessingParams/>
</p2v>

I'm running the command: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone>converter-cli -s C:\Temp\p2v.xml

I feel sure that this is just a minor issue with the xml input configuration file and if I knew the correct syntax or had an example file I could get it working. I can't find one anywhere. Should the datastore be the name vSphere/ESXi knows it as rather than the name I see in the vSphere Client?

Please help!

Thanks

I am planning to virtualize five (5) Windows servers using Vmware Converter Enterprise.   I found out today that these servers are running an OEM build of Windows Server 2003 from IBM.  When I did a test P2V today on a server running this same OEM build of Windows after starting the VM, a warning was displayed by Windows related to the need to re-activate Windows due to hardware changes, and that the server would fail to operate after three days unless the reactivation was done.  I have done some research and found that basically there were two options to fix this issue with virtualizing OEM builds of Windows.  The first being to add the following parameter to the .vmx file on the VM:  "SMBIOS.reflectHost = TRUE"     If that doesn't work the other option being to boot the vm using a volume license cd and doing a repair of Windows.  This was a helpful post in regards to this issue:  https://ohconowa.advizex.com/OWA/redir.aspx?URL=http%3a%2f%2fcommunities.vmware.com%2fthread%2f88633%3ftstart%3d0      Has anybody else seen this before and know of a better solution?

I've got two physical servers running Oracle Linux Server release 6.3 64-bit.  They each have a /boot partition that is ext4 and the rest on an LVM partition:

/dev/mapper/vg_cleveland-lv_root /                       ext4    defaults        1 1
UUID=3d37688e-305a-4974-9bb7-f02232b78790 /boot                   ext4    defaults        1 2
/dev/mapper/vg_cleveland-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0

vCenter Converter is only recognizing the /boot partition in the "Data to copy" section "Select volumes to copy".

If I go forward the conversion fails when trying to reconfigure the VM.  I've looked through the user guide and googled a bit but I can't seem to find why the ext4 LVM partition is not being recognized by Converter 5.

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.

Hi,

I have been reading a few documents online about P2V of SCO UnixWare 7, but they all seem a bit old now. The post I always seem to come back to is from 2009, and Cold Clone 3.0.3 from circa 2012, which had it's issues in ESXi5 and we are using ESXi6. Is there an "updated" way to P2V (cold clone) a SCO UnixWare 7 server to ESXi6?

Thanks in anticipation!

Kevin

Thought I would post some of my notes up for others.

PROBLEM:

If you migrate a Windows 2000 server and it finishes fine, but during boot up you get a BSOD;

STOP: 0x0000001E (0xC0000005, 0x8045D9BF, 0x0000000, 0x001A0018)

KMODE_EXCEPTION_NOT_HANDLED

• Address 8045D9BF base at 80400000, Datestamp 45069e6e - ntoskrnl.exe

SOLUTION:

• You need to power off the VM, add a CD-ROM and a Floppy virtual device (assuming it's not already there)

• Download this:

http://www.microsoft.com/downloads/details.aspx?FamilyId=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en&displaylang=en

• Extract it, and pull the scsiport.sys file out (should be version 5.0.2195.7059) and make it into a virtual floppy file, mount it to the virtual floppy along with a Windows 2000 iso.

• Boot the VM into recovery mode from the Windows 2000 ISO

• Copy the file off the floppy (scsiport.sys) to the %systemroot%\system32\drivers folder

• Reboot

Hi.
Users of mine wants to import virtual machine into our vCenter controlled environment.
I have limited users rights to access only their resources and everyday work seems to work fine for them.
The problem is when the tried to import machines they get the error seen on the image "You cannot use a disconnected inventory object for a destination.".
Even if I allow read-only rights on top-level, they end up with a permission denied at the end even if everything looks correct from a client view pointing out the resources they have the right to use.

I see the same problem regardless if standalone or vCenter converter plugin is used.

It works fine for me, but the I'm running as a admin so it doesn't count.

And I wouldn't like to change any permissions (if possible) for the users as we want to keep the regular users at minimum rights.

Obviously its a permissions problem, but I can't find what I need to change, especially as everything works for the users in every other case except when importing machines.

Anyone seen this behaviour before?

vCenter 4.1 and Vmware Converter 4.0.3 are used in this case

Hi All,

Is it possible to perform p2v/v2v migration over WAN? Any best practice or recommendations?

Thanks in advance...

Hi,

I have several VM's on 2 locations, one datacenter that is managed by us on our site and several VM's hosted on external hosting company datacenter.

Our own platform runs for now version 4.3 and the remote location run 5.1

I need to import few VM's from the remote location to our own location and trying to do that using Converter 5.1 hot-cloning.

The converter is installed on dedicated VM with external NIC that is reachable from the remote location and internal NIC that is connected to the vcenter and the ESXi hosts.

The converter is able to connect to the remote VM and get all settings done, but when I'm trying to run it, it fails at 1% with the error "Platform specific error 2338"

I checked the logs and so far was able to find out only those errors:

warning 'Default'] Disk number 1 has been skipped because of errors while reading partition table

warning 'Default'] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted

warning 'Default'] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176

warning 'Default'] Partition:Invalid sector magic number

warning 'Default'] [PopulateCapabilities] Volume-based cloning was disabled due to: <no volumes are recognized>

Any idea what can be the problem here and how it can be resolved?

I saw that those errors are mentioned with Converter 4.3, but I'm using Converter 5.1

The source VM is Windows 7SP1

Attaching the log for more information.

Any help will be highly appreciated.

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"