Quantcast
Channel: VMware Communities : All Content - Converter Standalone
Viewing all 5725 articles
Browse latest View live

Standalone Converter for ESXI 5.5

$
0
0

Hi,

 

When is there going to be a converter that is compatible with ESXI 5.5?

 

I need to convert a Server 2003 over but the converter doesn't work, and having looked at the matrix there isn't a compatible version available.


Error: A general system error occurred: Platform-specific error 1

$
0
0

I use vCenter 5.5 and ESXi 5.5.

In the process of converting Windows 2008 R2 server an error «A general system error occurred: Platform-specific error 1». I would be grateful for information about this error.

Log bundle are atteched.

Thanks.

P2V windows 2000 fails

$
0
0

I have had a hell of a time trying to convert a old windows 2000 physical to a virtual I installed the converter standalone 3.0 on the box it gets to 97% and fails out. Anyone have any advice on how I can get this to convert?

P2V-BL460 C G1 completed and stuck on BSOD

$
0
0

Hi,

 

I just recently converted one HP BL460 C G1  physical to virtual using converter 5.1. The conversion action got completed successfully. after the power on the VM while installing the device driver it fails to install all other drivers including SCSI controller, also in device manager it is not showing any disk, successfully install vmtools as well, but after restart. OS version: windows 2008 R2.

looking forward some helpful tips on that.

Thanks Abhay.

Conversion failed with error message "FAILED: The VSS snapshots cannot be stored because there is not enough space"

$
0
0

Hi All,

 

I have a Laptop with

     6 GB RAM,

     300 GB HDD, 

     2 CPU (1 socket and 2 cores)

     Windows 7 64 bit OS.

I am having external HDD (2TB capacity with 460 GB free space) which will have the destination folder for the VM.

 

When I try to convert this using  VMware converter standalone I am getting this following error.

"FAILED: 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)."

 

I have attached the error log for your reference.

 

 

Thanks in advance to all for helping to overcome this issue.

 

Cheers

Kumar RAMASAMY

Noob: Converting server that has iSCSI volumes?

$
0
0

Hi,

 

I have an ESXi 4.1 host and I'd like to virtualize a Windows 2003 Server that has several large iSCSI volumes attached that are already on a SAN. What's the best way to handle the iSCSI storage? Do I detach the iSCSI volumes, p2v the server, then attach the volumes to the new VM? Or is the converter smart enough to do that for me? Pointers to a best practices document or example would be great.

 

Thanks

Help or pointers on how to convert a windows 2012 domain controller. Best practice

$
0
0

Hello can anyone please tell me what the best practice is for converting on of the companies windows 2012 domain controllers and how to do it?

Thanks

Unable to obtain hardware information for the selected machine.

$
0
0

Hello,

I am using VMware vCenter Converter Standalone 5.1 in order to convert an old VMware Server 2 machine for ESXi 5.5

 

I clicked the "Convert machine" button, selected "VMware Workstation or other VMware machine" as source type.

As virtual machine file I selected the VMX file.

Clicking next, I get the "Unable to obtain hardware information for the selected machine" error.

 

I am using 7SP1 64bit, no firewall nor antivirus.

 

Thank you,

Francesco


Converter SDK: virtualization from backup image

$
0
0

In a disaster recovery tests environment, I need to convert images backup supported by VMware Converter (with 'Convert machine' ), or virtual machines with virtual disk on which a backup has been restored (with 'Configure machine'), with the automation of Converter SDK.

Converter Standalone already works well in this way.

I need, however, the automation of SDK.

VMware's samples show only the virtualization from physical resources, which parameters are configured in the '.properties' file.

I think there's a list of statements to add to the '.properties' file that regards the source image/virtual machine or type of convertion ('convert' or 'configure'), as shown during the Converter Standalone wizard.

Does anyone already follow this way of virtualization?

VMware converter 5.1 very slow (ssl already disabled)

$
0
0

Hello,

 

I need help very quickly! I have to do a v2v migration of a server.

But the speed of converting is about 6 mb/s which is very slow... (about 1000 GB of Data)

 

Network-Speed is normal - no issues detected. When try to convert a physical machine, it is much faster!

 

I already disabled ssl encryption, but still no improvement!

 

The server must be running on Monday. Do you have any other ideas I can try?

 

What about using Converter 4.3 (which I read is more performant)

 

br

beistrich!

Conversion fails at 1%

$
0
0

My conversion attempts fail at 1% over and over.

 

Here's my setup:

 

Source: Windows 2008 R2 x64 "physical" machine (Running on Proxmox on a server). I chose physical machine because Proxmox VMs are not in the supported list for virtual machine importing.

Destination: Local disk on my Windows 7 Machine for use in Workstation 10.0.

 

Upon conversion fail, Converter pops an error dialog with this text:

 

Virtualization of [xxx.xxx.xxx.xxx] failed: an error occurred during the conversion: 'converter.fault.NetworkShareConnectFault'

 

Standalone converter displays this message: "Error: Unable to parse the configuration file of the destination virtual machine."

 

Logs attached.

 

After digging through the community and knowledgebase (and a bit of googling), I tried the following to remedy:

 

1. Disabled UAC on source machine

2. Disabled firewall on source and destination machines

3. Disabled real-time antivirus protection on source and dest machines

4. Turned off simple file sharing on dest machine

5. Enabling file and printer sharing on dest machine

 

I've been at this all day long and am ready to throw in the towel. Please help??

Failed:unable to obtain the IP address of the helper Virtual machine

$
0
0

I am trying to convert the Linux based VM that is  hosed on hyper-V 2012 host machine, using VMware converter standalone utility, option  "Power on" but it failed at 1 % and prompt error message that is attached with this post for reference.

 

Please help out...

Automating Converter Standalone using Converter-cli.exe

$
0
0

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

Cannot access (MAC) Host shared file system from within VMware vCenter Converter Standalone Client when desiring to create a VMware image (Windows 7 running in Parallels VM on a MAC) for the Powered-On machine option.

$
0
0

The HOST (Mac) file system is currently shared into the Parallels VM and is accessible via Windows Explorer and works correctly in the Virtual Machine environment, however, after installing the vCenter Converter application on the Windows virtual machine these shared folders are not accessible from within the Converter tool when selecting the target destination of the VMware file (s). I Cannot select an existing folder on the "C:" drive to write the image to as there is not enough space available for the VMware image and it needs to be written to another file system while the image is being created.

 

Does anyone know a way around this in order to point the target to write the image to the Host (MAC OS) file system or is this a bug?

Error converting an image

$
0
0

I'm using Symantec System Recovery to create images (.sv2i).  I need to convert those images to VM.  Three out of four servers converted without problem.  The last one is giving me the "Unable to obtain hardware information for the selected machine."

The images for all servers are stored in the same place so I can't imagine there is some permission issue.  All are Windows 2008.  I've tried using converter 5.1 and 5.5  Converter is running on Windows 7 Pro 64-bit.


converter 5.1 windows 2003 SP2 support

$
0
0

is it possible to migrate p2v windows 2003 SP2 with sql with the vmware converter 5.1

in the support list i only see windows 2003 SP2 R2  does did meen both windows OS

error "the source parameters are invalid" when trying to convert Shadowprotect image

$
0
0

Hello

I am hoping that someone can point me in the right direction.

I am running Converter 5.5.0 build 1362012.

The image files were created by Shadowprotect 3.5.2.

When trying to convert the backup image I get error "the source parameters are invalid".

I have attached the diagnostics files.

 

I have done conversions before, and am rather puzzled.

Many thanks.

Converter traffic

$
0
0

I'm in a discussion with some of my coworkers. We have a split datacenter with one vCenter server managing both facilities. The vCenter server lives at Facility A(on a different vLAN) while the server that I'm trying to P2V and the Host I'm attempting to put it on live in Facility B (on the same vLAN). The P2V process ran all weekend and only managed to get to 6%.

 

A my coworkers believe that if we hook a cable up directly between the server we are trying to P2V and the new Host, the process will be lightning fast.

 

However, I seem to recall that all P2V traffic routed through the vCenter server before going to the host. My suggested solution is to move the host to Facility B during the P2V process.

 

Who is correct or is anyone right?

scheduled task for converter 5.5

$
0
0

how can i schedule a vmware converter 5.5 job?

Getting error, a general system error occurred: unknown internal error

Viewing all 5725 articles
Browse latest View live


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