since the last infrastructure update to 5.5 (latest available) the Converter is not working anymore. When starting a conversion it hangs in "Retrieving source machine information" and CPU is eating 25% on "System" Task.
Had anyone similar problems and get them solved?
vCenter Server 5.5.0 build 1891313
Source machine resides on a NFS datastore
Last messages in logfile "vmware-converter-worker-1.log":
2014-07-04T14:45:59.826+02:00 [06084 info 'Default'] Partition found type HPFS/NTFS(7) name:HPFS/NTFS start:63 size:8385867 active primary
2014-07-04T14:46:00.150+02:00 [06084 info 'Default'] Partition found type HPFS/NTFS(7) name:HPFS/NTFS start:8385930 size:8385930 primary
2014-07-04T14:46:00.150+02:00 [06084 info 'Default'] Disk with signature 3394074573, recognized partitions 2
2014-07-04T14:46:00.156+02:00 [05140 info 'ThreadPool'] Thread enlisted
2014-07-04T14:46:00.156+02:00 [00608 info 'ThreadPool'] Thread enlisted
2014-07-04T14:46:00.157+02:00 [00608 info 'Default'] HOSTINFO 974731309 @ 2241044Hz -> 0 @ 1000000000Hz-->
2014-07-04T14:46:00.158+02:00 [00608 info 'Default'] HOSTINFO ((x * 3743169701) >> 23) + -434945190246-->
Thanks and regards.
Edit: The converter can be aborted and closed, but the "System" windows task is still eating 25% CPU, windows cannot reboot without hard reset.
Message was edited by: virtualnobody
Ok, after restarting both services and created a new conversion task it still hangs on "retrieving source machine information". And now the "System" task is eating up excactly 50% CPU. Having two processes "vmware-converter.exe *32" in task manager.
Can it be some sort of "file locking" problem? Must be something low-level windows related?
Have tried the conversion on different OS, virtual and physical hardware. Same problem for "Local install" and "Client/Server install" of the converter.
A conversion task is running normal when selecting a different source VM. Must be specific to that VM.
Details of source VM:
Power state: offline
Compatibility: ESXi 5.5 and later (VM version 10)
Guest OS: Windows NT 4.0 SP6
VMware Tools: Not running, version:7392 (Current)
Memory: 1024 MB
Hard Disk 1: 8.00 GB
Nothing uncommon except the very old OS. Maybe its that issue?
Thanks for your reply. That is the issue, OS is Windows NT 4.0.
It is still possible to download the vmdk and vmx from datastore and start that VM locally in Player.