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

Re: Can I rerun a V2V Job in Converter ?

September 18, 2015, 12:16 am
$
0
0

Event when you filter for jobs in "all history"?

A job can be deleted from history but in this case the tasks also get deleted.

Occasionally there can be some error reading the job from the database and it won't appear; you could check that in the server logs. If that's the case - sorry, you'll need to enter it manually again.

 

If you really badly need to see that job - here are some hackerish steps you might try:
  - first try to find out its id. Both task and job ids go incrementing, so you can guess by looking the task id and neighbor tasks job ids.

  - eventually check in server log whether it is really in the database

  - stop converter server service

  - if it's in the db, use some toll like sqlite studio to open it directly

If it is not in the db then it has gone for good.

 

Regards,

Plamen

↧
Search

Unable to find supported boot loader

September 21, 2015, 9:29 am
$
0
0

or boot loader configuration file. Error: Windows VM Converter Standalone 6 trying to p2v powered on remote linux machine.

 

Here is my grub.conf.

 

#

# GRUB configuration file

#

# General configuration

background ffffff

color black/cyan black/light-gray

default 0

foreground 000000

hiddenmenu

splashimage (hd0,3)/boot/grub/3comSplash.xpm.gz

timeout 10

# Serial configuration

serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1

terminal serial

# OS Installation 'A'

title VCX Linux

        root (hd0,1)

        kernel /boot/vmlinuz ro root=LABEL=/A quiet console=ttyS0,9600n8

        initrd /boot/initrd.img

 

Is there anything that I can edit to make this work?

 

Thanks!

↧
↧

Re: Unable to find supported boot loader

September 23, 2015, 4:14 am
$
0
0

The error means Converter could not find the path to grub.conf.

Give some more info - distro and version, grub version. Best - post the logs.

 

Regards

↧

Converter Standard - vmk

September 24, 2015, 4:46 am
$
0
0

Hi,

We are in the process of identifying our networking troughtput and firewall requirements for a V2V / P2V conversion between two vSphere clusters.

The clusters belongs to two different companies in the same building and we have multiple 10Gbit connections between us.

 

But I want to make sure we do the right VLAN and firewall config and to do that I need to understand how the converter actually moves the traffic.

 

When it comes to P2V (ie virtual machine is on) the virtual machine needs to have connectivity from its production VLAN towards the new ESX hosts management interface?

For a V2V would that be done from the source hosts management interface towards the new hosts management interface?

The VMotion vmk would not be used at all as far as I can understand?

 

Both hosts and vSphere are at 5.5U2.

↧

Re: Converter Standard - vmk

September 24, 2015, 7:24 am
↧
↧

Re: Converter Standard - vmk

September 24, 2015, 10:37 am
$
0
0

Hi

 

For Windows P2V you are correct.

In case of Linux P2V, the destination machine connect to the source, the destination machine's virtual network (not the management one) needs to have connectivity to the source machine's virtual network.

In case of V2V (both Windows and Linux), the traffic passes through Converter server, which means Converter's machine needs to connect to management interface of both source and destination ESX.

I haven't actually used environment with VLANs, so better check it than trust me blindly :-)

 

HTH,

Plamen

↧

Re: Converter Standard - vmk

September 24, 2015, 11:52 am
$
0
0

Good point on the Linux VM's.  I haven't done one in so long, I forgot about the whole "helper IP" piece of the conversion.  Thanks for pointing that out.

↧

FAILED: An error occurred during the conversion: Cannot format volume

September 26, 2015, 4:44 am
$
0
0

Searching I couldn't find anything related to "Cannot format volume"

 

Tried converting Windows 2008R2 server from one vSphere 5.1 server to a new vSphere 6.0 using vCenter Converter Standalone 6.

The source VM was fully powered off.

4 partitions on the server, 3 were successful but the last failed almost immediately.

One partition was increased from 100GB to 200GB, that was successful.

Second and third partition was 220GB and left alone, successful

The fourth partition failed we were trying to increase the size from 500GB to 2TB.

↧
Search

Re: FAILED: An error occurred during the conversion: Cannot format volume

September 27, 2015, 5:20 pm
$
0
0

You're trying make the P2V and resize the disk at the same time ? If yes, why not just make the P2V first to move the virtual machine to the new host and then resize the disk ?

 

Not 100% sure, but I think the problem is related to the 2TB disk, since vSphere 5.1 does not support vmdk with 2TB size (maximum supported is 2TB minus 512 bytes).

↧
↧

Re: FAILED: An error occurred during the conversion: Cannot format volume

September 28, 2015, 2:39 am
$
0
0

What Windows version is Converter running on? It needs to recognize the NTFS version of the source machine.

Also ReFS cannot be resized but shouldn't be available on Win 2008R2.

↧

98% FAILED: A general system error occurred: Unknown exception. Win Svr 2003 SP2

September 28, 2015, 5:39 am
$
0
0

We are trying to convert a Windows Server 2003 x64 SP2 machine and get this error at 98 percent

FAILED: A general system error occurred: Unknown exception.

 

The only reference I see in the log file is,

 

2015-09-25T18:07:50.032+08:00 warning vmware-converter-worker[04980] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1

2015-09-25T18:07:50.032+08:00 warning vmware-converter-worker[04980] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR

2015-09-25T18:07:50.032+08:00 warning vmware-converter-worker[04980] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_IO: failed to send io message

2015-09-25T18:07:50.032+08:00 info vmware-converter-worker[04980] [Originator@6876 sub=Default] Sysimgbase_DiskLib_Write failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)

2015-09-25T18:07:50.032+08:00 warning vmware-converter-worker[03140] [Originator@6876 sub=Default] ERROR: Vmount library: Error 2338 while while writing to device

 

 

All log attached. Any help would be greatly appreciated.

↧

Re: FAILED: An error occurred during the conversion: Cannot format volume

September 28, 2015, 6:19 am
$
0
0

Correction, ReFS can be resized with Converter 6.0.

OTOH if the datastore is VMFS-3 formatted, it wouldn't support 2TB+ vmdks, even if accessed by ESXi 6.0.

↧

not enough space on the source volumes... Error code: 2147754783 (0x8004231F).

September 28, 2015, 6:46 am
$
0
0

VMWare team, please instead of showing the error and cancelling conversion of the physical machine, offer "Do you want to continue conversion anyway?" option.

 

I'm trying to converta physical desktop to NAS using network path (\\bnas4\vms), and getting the error. The volume has 6TB of free space but the Converted cannot determine the free space.

 

Please fix this!

↧
↧

Re: not enough space on the source volumes... Error code: 2147754783 (0x8004231F).

September 28, 2015, 7:13 am
$
0
0

Hello Phoenicyan,

 

Please don't be so trigger-happy :-)

0x8004231F (VSS_E_INSUFFICIENT_STORAGE) is an error you get when VSS on the source machine has failed to create a snapshot. There is probably not enough free space there. This snapshot is required to ensure the data integrity after the conversion.


HTH,

Plamen

↧

Re: not enough space on the source volumes... Error code: 2147754783 (0x8004231F).

September 28, 2015, 7:23 am
$
0
0

Thank you for the quick answer! I'm in AZ, and it is normal to be "trigger happy" here

 

The Desktop has 300GB drive C with 63GB free. I do not select drive D for conversion. Is 63GB of free space not enough for snapshot? How much space should I have on C drive for the conversion?

↧
Search

Re: not enough space on the source volumes... Error code: 2147754783 (0x8004231F).

September 28, 2015, 7:54 am
$
0
0

 

63GB should be enough (usually about 15% are enough)

You may check whether there are no current snapshots that take the space (run "vssadmin list shadows" in command prompt)

You may eventually restart the "Volume Shadow Copy" service but beware that would not disrupt any applications that are using it (backups, SQL server,...)

↧

Re: not enough space on the source volumes... Error code: 2147754783 (0x8004231F).

September 28, 2015, 8:03 am
↧
↧

Re: 98% FAILED: A general system error occurred: Unknown exception. Win Svr 2003 SP2

September 28, 2015, 8:04 am
$
0
0

Should be network problem, I hope temporary, the NFC errors begins with the following message:

2015-09-25T18:06:06.172+08:00 error vmware-converter-worker[04840] [Originator@6876 sub=task-1] VimConnectionHelper Keepalive to host 192.168.4.38 failed: An existing connection was forcibly closed by the remote host

Try to configure only your destination VM

HTH

↧

Re: not enough space on the source volumes... Error code: 2147754783 (0x8004231F).

September 28, 2015, 11:42 am
$
0
0

Finally, it worked! I went to the Services Panel and stopped instances of SQL Server, MySQL, and the "Microsoft Software Shadow Copy Provider". And after that the conversion to the network NAS worked!

↧

Error 1935 when converting Windows Server 2008 R2

September 29, 2015, 1:18 am
$
0
0

Dear All

 

I am having following error when trying to convert a Windows server 2008 machine.

 

I was able to move other machines with same OS without issues but got stuck on 1 machine in particular.

 

"The error thrown is : Error 1935. An error occurred during the installation of assemble component {9DA4DC8A-9731-3F0E-8BD5-FC17CA6848AD}

HRESULT : 0x80070003"

 

Any help will be much appreciated.

 

Regards

Gaurav

↧
Viewing all 8478 articles
Browse latest View live
Search