Converter standalone 5.1 crashes host on retrieving source machine information

[BasGubbels]

Hi all,

I'm kinda stuck atm.

We are using 2 ESXi servers. I'd like to convert the servers of 1 ESXi to another.

I'm using Converter Standalone 5.1.

The source server is running ESXi 4.0, the destination is running ESXi 5.1.

Now when i'm trying to convert an offline machine, the host that is running

the standalone converter software crashes and reboots. I've tested this on several machines with different OS's, they all crash.

Out of the 4 VM's running on the source server, i succeeded in converting 2 machines to the new server.

The other 2 are giving me these issue's.

Could you give me any pointers of how to trouble shoot this? cause it's not giving me any errors

to work with.

Thanks in advance.

[POCEH]

Please upload the log bundle with fail.

[BasGubbels]

If you meant the log from the vm itself, this is it.

But if you meant the log of the converter standalone, i'm unable to find it :smileyblush:

[BasGubbels]

FYI:

I've tried other versions of the Converter SA. 4.0.0 / 5.0 / 5.0.1

These versions DO start to convert, but within a few seconds they fail because they are incompatible with ESXi 5.1.

[POCEH]

The log bundla can be retrieved from Converter UI - select the failed task, invoke context menu (right mouse button), and invoke 'export logs'.

Otherwise the logs location is:

XP, 2003

%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone\logs

Vista+

%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs

[BasGubbels]

The task isn't in the GUI because im not even getting that far,

when selecting the source machine. it crashed the whole server.

i found the files, i searched for .log files. But they were zipped.

[BasGubbels]

Anyone?

Are these the logs you are looking for?

[POCEH]

Please upload converter-worker and converter-agent logs.

[BasGubbels]

here are the logs you requested.

[POCEH]

Can you switch Worker logging level to verbose (instructions how to do it can be found at http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2008019) and retry the conversion and provide the worker log file?

[BasGubbels]

These are the verbose logs.

Server crashes (BSOD) with BAD_POOL_CALLER error

[POCEH]

Unbelivable... are you using an updated Converter version?

Could you unsinstall/reboot/install the Converter and try again?

[BasGubbels]

We are using the latest build (5.1.0 build 1087880)

Also tried it on different hardware and os versions, same result.

[POCEH]

I'm say to reinstall the Converter server and components, in case if something is broken.

What you mean with 'different hardware and os versions'? This should be virtual machines you want to convert, but seems the error is access to your ESX, is it possible to reboot the ESX?

Also you can try to disable SSL just in case.

[BasGubbels]

We tried the converter standalone software on different hardware with different OS version.

But don't waste any of your time yet.

I've installed a fresh Win7 VM on another ESXi server, installed the Converter standalone software.

Tried to convert a machine and it magicly started! I'm going to try the conversion this evening in the live environment.

[POCEH]

This is serious issue and I preffer to know why the converter crashes.

From the other hand this could be an issue with ESX itself, and this is what I want to understand.

[BasGubbels]

i agree that this is a serious issue, i got it working on a freshly installed Win7 system.

Let me try to explain what we were trying to do:

i took 1 server where I installed VMware converter Standalone.

From this server/software I was trying to convert offline VM's from an ESXi 4.0.0 host to a new ESXi 5.1.0 host.

It worked for several VM's but some of them (roughly 50%) made the server with the Standalone software crash with a BSOD.

I tried to use an other server (with different OS and different hardware) for installing the Converter SA software.

When trying to convert a VM's the server also crashed with a BSOD.

My last attempt was to use a Win7 client, installed the Converter SA software.

and somehow it DID work, the conversion was succesful w/o a BSOD.

Do you want me to test anything so we can figure out what was causing this BSOD?

[POCEH]

What are guest OSes when the Converter fails, on which OS the Converter was installed? There is a presumption that you'll convert only older or same OSes, for example you can not convert V2V, most ot the times, Win7 with the Converter installed on W2k3, this is because of NTFS versions, of cource crash is not acceptable. Is this your case?

[BasGubbels]

The VM's: Server 2003R2 x32 / Server 2008 SP2 x64

The server with the converter software installed on it and crashed: Server 2003R2 ent x64 / Server 2008R2 std.

The conversion of the VM's that did succeed on the above servers: Server 2008 SP2 x64/ Server 2003R2 x64.

So i can't say that it crashed because of the installed OS's.