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

Problem importing a Win7 machine onto ESX4 host

$
0
0

Hi Folks,

 

Having an issue while importing a Win 7 machine with min disk size (28 GB) on a ESX4 host with vCenter converter 5.0.0.

vCenter version is 4.0.

 

Error message is-

"Import Machine

Failed to take snapshot of a source

volume. Possible causes include not

having any NTFS volumes on

Windows XP or Windows 2003

source systems, and not having

enough free disk space."

.

 

There is enough free disk space on the datastore where I am trying to import.

 

Can anyone let me know possible cause and solution to this?

 

Thanks

vmrockin


Re: Problem importing a Win7 machine onto ESX4 host

$
0
0

Can you goto the source machine and check if you are using FAT32 volume or does the drive has enough free space

Re: Problem importing a Win7 machine onto ESX4 host

$
0
0

VSS needs space on the source disk for the snapshot, it also requires the source machine to have at least one NTFS volume, hence this message. However this is a general message and the error could have been something else. If you want more precise error, look at the worker's log.

If you know these requirements are met, you may just try restarting the VSS service and attempt the conversion again.

 

HTH

Plamen

Re: Problem importing a Win7 machine onto ESX4 host

$
0
0

Hey Akash,

 

This is a Win 7 machine and FAT32 is not used, also there is enough free space on the PC as well as datastore.

 

What I have suspectd is that there is a space issue on the vCenter server itself where the VMware converter is installed.

I guess it needs free space on the vCenter server to temporarily save files. I will check that.

 

Thanks

Re: Converting from rsync'd backup of RHEL/CentOS 6.4 system

$
0
0

That manual process looks pretty reasonable to do. I think I can boot the VM from the rescue CD and then populate new LVM partitions from my remote image on my USB drive, using a tar pipeline (or rsync if it's on the rescue CD). Knowing what reconfiguration needs to be done is the hard part, and that doesn't sound too bad. I'll follow up here once I see how it goes.

Re: Unable to obtain hardware information for the selected machine - Standalone Converter 5.1

$
0
0

Thanks for the help on this. I am just going to move forward with installing the converter on the local host and completing the P2V from the local system. I only have a 2 systems left to P2V so it is not a big deal. Thanks again!

Re: Conversion fails with kernel error.

$
0
0

For your information..

 

My source is

[root@localhost ~]# uname -a

Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[root@localhost ~]# cat /etc/issue

CentOS release 6.4 (Final)

Kernel \r on an \m

 

by using converter standalone 5.1, it fail with the

FAILED: An error occurred during the conversion: ' * got kernel major revision as ERROR:

kernel version has to be in format 2.6.*, version 2.6.32-358.6.1.el6.x86_64 is not supported (return code 1)'


Then i downgrade the converter to 5.0.1, it success without error.

There is no need to do any rpm remove.


Re: Poor transfer rate using Converter 5.0 Standalone compared to 4.3

$
0
0

I know this is an old thread but Converter 5.0.1 b875114 still has the same issue.  By default, SSL is enabled on the Converter in the "converter-worker.xml" file.  When I turned off SSL and restarted the VMware converter worker service, my rate went from 140KB/sec to 45MB/sec.  I wish that VMware would fix this issue (it wasn't like this in previous versions, i.e., 3.5, 4.x).  Even for secure transfers needing SSL, 140KB/sec is unacceptable.

 

Thanks for the help!!!


Re: Converting from rsync'd backup of RHEL/CentOS 6.4 system

$
0
0

Converter doesn't support restoring backup images (except some legacy old versions of Symantec, Acronis, StorageCraft). There is one more bad news - you won't be able to do convert the running machine easily. There is a bug in Converter 5.1 that fails the reconfiguration step when the source is a 'different' distro, i.e. not one of the supported RHEL, SLES, and Ubuntu. 5.0 won't do either because it can't reconfigure RHEL 6 (and almost certainly CentOS 6 too).

That said, I see the following options for workaround:

  - you do a P2V from the remote location. Converter usually requires to work in a LAN but this is limitation of the underlying network protocol. For Linux P2V however, it uses tar over SSH, so it should work. The conversion will fail during reconfiguration (e.g. at 98%) but all the data would be transferred. Then you should proceed with manual reconfig.

  - create a new VM, boot it from a live CD, and copy the backup image in it, e.g. using dd. Then proceed with manual reconfig.

 

You can have a look here about what manual reconfig includes: Re: Conversion fails with the error:FAILED: An error occurred during the conversion:'root is not found'

 

HTH

Plamen

Re: Unable to obtain hardware information for the selected machine - Standalone Converter 5.1

$
0
0

Do you connect with 'administrator' account (not another account in the administrators group) to the source machine?

If what POCEH wrote didn't help, pls post the agent's log. It can be found on the source machine in %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs.

Service_Boot_Start error on v2v conversion

$
0
0

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.

Re: Service_Boot_Start error on v2v conversion

$
0
0

It seems like the problem is because of the startup / device drivers. Try enabling the ATAPI SERVICE_BOOT_START and see it that works.,

Re: Service_Boot_Start error on v2v conversion

$
0
0

The Bitmap driver is used only when incremental conversion is used. Do you really want a incremental conversion?

I recommend you to reinstall the converter, this should fix the problem with driver.

The V2V means that you convert powered-off VM, the P2V means that you convert powered-on machine (physical or virtual). If you can do V2V on your server, I've recommend you.

Re: Vcenter Converter 5.0 Error 1603

$
0
0

For help:

I met the same problem, the website said the restart can be, but after I restart is not working, I don't know you is how to solve?

Thank you very much!

 

 

-------error 29142.could not start service vstor mntapi 1.0 driver(shared)

Re: Vcenter Converter 5.0 Error 1603

$
0
0

I suggest to install and use Converter 5.1


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

$
0
0

OK, so I setup the ESXi server, copied the vmdk file to the datastore and converted it using the "vmkfstools -i" command.

I am able to turn the machine on, but It blue screens during boot up.

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

$
0
0

After confirming the target virtual machine has an "LSILogic" disk controller with the virtual disk connected as SCSI0:0, try to run the Converter again for this VM - using the "Configure Machine" option - to see whether the final reconfiguration works this way!?

 

André

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

$
0
0

I no longer have access to the original machine. All I have is the vmdm. I assume what you are referring to would take place on the machine to be imaged?

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

$
0
0

The "Configure Machine" runs on the virtual machine itself and basically tries to re-configure the existing VM by e.g. injecting the appropriate drivers.

 

André

Re: Service_Boot_Start error on v2v conversion

$
0
0

You taught me much. Thank you. I didn't realize that v2v means I needed to shut down. This worked with no troubles. Thanks again.

Viewing all 8478 articles
Browse latest View live


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