Quantcast
Channel: VMware Communities: Message List - Converter Standalone
Viewing all 8478 articles
Browse latest View live

Re: Can't convert Server 2008 R2 Machine getting error: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).

$
0
0

Got it figured out.  My Appassure snapshots were also failing with a similar error so this is what I did to resolve it.  My servers now converted with no issues.

 

  1. Open Disk Manager.
  2. Look at the SRP partition, and see if it is 100% full.
    • If so, proceed to Step 3.
    • If not, check if there are any drives that do not have more than 300MB free (minimum requirement to use VSS).
  3. Right-click a drive, select Properties, and then select the Shadow Copy tab.
  4. Ensure all Shadow Copies are disabled, and set to no limit on all drives.
  5. Go to the SRP partition, and assign it drive letter B:.
  6. Open the B: drive via Disk Manager, and then search for the System Volume Information folder. Note: If needed, change the folder options so that you can view hidden files, folders, and drives.
  7. Right-click the System Volume Information folder, and select Properties.
  8. On the Security tab, click Edit, and then add the Everyone group with full control to the folder.
  9. Open the System Volume Information folder (you should see log files that are full), open a command prompt running as an Administrator, and then type the following commands to unload the filter driver.
    • B:
    • B:\>FLTMC UNLOAD AAFSFLT
  10. Navigate to the System Volume Information folder, and type the following commands:
    • B:\>CD System Volume Information
    • B:\System Volume Information>DEL AALOG_* (this will delete all the log files and then recreate a new one)
    • B:\System Volume Information>CD\
    • B:\>FLTMC LOAD AAFSFLT
  11. Close the command prompt window.
  12. In Windows, right-click the System Reserve folder, and remove the Everyone Group.
  13. In the Disk Manager, remove the B: drive (and click Yes when the window prompts with a warning).

Re: P>V conversion of Windows server > ESXi host 5.1 fails

$
0
0

once check your physical and virtual hard ware configuration

Re: P>V conversion of Windows server > ESXi host 5.1 fails

$
0
0

The trick is to only transfer one drive at a time. This means that if the source has a C and a D drive you'll be P2V'ing this machine twice creating to seperate VMs - one only containing the C drive including the system partition and another VM (which I just called 'servername_Ddrive') containing only the D drive. When both P2V's are done the second one is removed from inventory. For the first VM, go to Edit Settings and attach the disk from the second VM, 'servername_Ddrive'. After that, you can boot the VM now containing both drives. Be aware that the newly attached disk will deafult to drive letter D. This means that if it had another drive letter before, you'll have to change it manually. An important point to mention in this process is that when transferring the second VM only containing the D drive, the transfer will fail with an error around 98% stating something like "An error ocurred during reconfiguration...". This is ok - as long as the drive has been succesfully cloned, this is what matters

Uanble to connect other converter server (failed to connect to vmware converter standalone server at on port 443 , check your network conection and try again , internal system error (invalid response)

$
0
0

Dear team,

 

Installed VMware-converter-all-5.0.1-875114 on one server , but when i try to connect another converter server from this server i m getting attached  error, hence ndeed your asisstance to resolve the same.

 

regards

Mr VMware

Re: Uanble to connect other converter server

$
0
0

YES U R CORRECT, THE VERSION I M TRYING TO CONNECT IS A DIFFERENT VERSION i.e.

 

SOURCE VERSION: 5.0.1 875114

dESTINATION VERSION 4.0.1 161434

 

i m able to connect with same version of vmware converter i.e.

SOURCE VERSION: 4.0.1 161434

dESTINATION VERSION 4.0.1 161434

Re: Conversion failure at 99% for Redhat

$
0
0

Hi araostore

 

During cloning of powered-on Linux machines, Converter Standalone 4.0.1  preserves the following source file systems on the target: ext2, ext3,  reiserfs, and vfat. All other source file systems are converted into  ext3 file systems on the target virtual machine.

 

Yours, Abbie

Suggestions for running VMware Converter over the internet

$
0
0

Hi everyone, I'm looking for a bit of advice

 

Currently using VMware Workstation 9 and things are going great, I've P2V'd a couple of local machines on the network using the VMware vCenter Converter Standalone Client (5.1) and had no issues at all.

 

What I am currently looking to do now however is proving somewhat challenging.

 

I have a web/database server which is in a datacenter that I wish to P2V. The server is running Windows 2008 Server R2 edition and I can connect to the server using Remote Desktop. I have access to the firewall on the server (it only has the default / built in Windows firewall) and I have access to the firewall in the office here.

 

The server is limited on disk space, it has two physical drives as:

 

C: 30GB (2.7GB free space)

D: 16GB (5.1GB free space)

 

The lack of local disk space is naturally preventing me from running the P2V and storing the img locally, then downloading via FTP or similar.

 

Therefore, I'm wondering what my options are...

 

Would it be feasible to try and run the P2V from the office (bandwidth is 30Mb downstream, 3Mb upstream)?  If so, what prerequisites would be required in terms of firewall ports or maybe even VPN connections?

 

Any other suggestions on how best to P2V this machine would be welcomed

can not download vm machine from datastore

$
0
0

Hello,

I downloaded vm from local data storage, but always get the error:

Expected put message. Got: ERROR

 

I have a local data store o esx server (i have a esxi 5.2 + essential kit). No shares, no other connection to local datastore. I try to download it from the web browser data storage, but I have the same error.

 

It is possible download vm from the local datastore?


Re: can not download vm machine from datastore

$
0
0

You don't need the Converter in order to download the VM's files, just SCP/SSH/etc.

For any other other reasons you can convert the VM to Workstation format.

HTH

Re: Suggestions for running VMware Converter over the internet

$
0
0

If I recall properly the limititation is < 200ms response time... And of cource VPN is preffered solution. HTH

Re: P2V failed after 98% when converting physical RHEL 6.2 system

$
0
0

Hello Plamen,

 

Though we have converted the system successfully, We are not able to boot the system and we are getting the following error:

 

"Waiting for required block device discover..

"Waiting for two sda-like devices(s)..

 

We have tried by increasing the size of /boot by 4GB but still it fails. As you suggested by "patch the initrd image by injecting the lvm (and its libraries) from the helper, run mkinitrd, and then restore the original binaries in the image".  How we will inject lvm (and its libraries) from the helper?

 

Regards

 

Ajoy Sonowal.

Error-whileBooting.png

Re: Suggestions for running VMware Converter over the internet

$
0
0

Hi there, thanks for the reply.

 

I can get a VPN set up I guess, will need to install RRAS etc on the host but that shouldn't be too much of an issue.

 

Average ping is around 50ms so that might not be an issue. I wasn't sure what would happen though if the connection timed out. Naturally it would take hours and hours to shift that amount of data, would you happen to know if the converter has a timeout setting or will it keep going until complete.

 

Are there any other solutions or suggestions as to a better way to do this one?

Re: P2V failed after 98% when converting physical RHEL 6.2 system

$
0
0

What you have done has been successful.The good news is the conversion has succeeded. the bad news is that you have hit a different issue. Unfortunately I don't know what is wring this time.

The loading messages mention kvm, but you said it is a physical machine (btw converter doesn't convert KVM machines). Is it a KVM server by chance? Can you pls give more info on peculiarities of the source machine. Also upload the log bundle, it might be useful.

Re: P2V failed after 98% when converting physical RHEL 6.2 system

$
0
0

Hello ,

 

If we don't consider the LVMs, the converter converted P2V successfully. Though it is completed successfully but it is giving problem while booting the system which is mentioned above.

 

But if we consider LVMs for conversion, it fails after 98%.

 

So, what should we do both both the scenarios.

 

 

 

Regards

 

Ajoy Sonowal.

Re: Suggestions for running VMware Converter over the internet

$
0
0

Unfortunatly the Converter is very sensitive to network drops and there is no way to recover from failed conversion.

If it applicable it's better to transfer the machine in WS format (USB stick or similar) but you'll loose latest changes...

One more thing - the Converter needs to see ESX on port 902, see manual.

HTH


Re: can not download vm machine from datastore

$
0
0

make sure that SSH is configured on your host and use something like WinSCP to down load the file.

Re: P2V failed after 98% when converting physical RHEL 6.2 system

$
0
0

I don't understand. What do you mean by "if we don't consider the LVMs"? Does it mean you have set the volumes to basic before conversion? If yes, does it also mean that if you don't set them to basic *and* increase the /boot volume size, it still fails with the same "no space left" error?

Re: Suggestions for running VMware Converter over the internet

$
0
0

Just a quick update.

 

Yesterday I installed RRAS on the server I wished to P2V, then using a local Win7 client machine I connected via VPN to the server (ironically, the Win7 client was a VM itself ). With the VPN in place, I did a full install of the Standalone Converter on both the host server and the client machine. I then had the server connect to the Win7 machine and set the P2V process going.

 

9 hours and 58 minutes later it had finished and I now have the P2V'd machine running here on Workstation 9.

 

It seems the almost impossible was actually possible

98% FAILED: Unable to reconfigure the destination virtual machine. Win srvr 2003

$
0
0

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.

Re: 98% FAILED: Unable to reconfigure the destination virtual machine. Win srvr 2003

$
0
0

can you goto the concerned destination on the datastore and check if the vm directory is present. If yes,Try creating a new VM and point it to the vmdk file.

Viewing all 8478 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>