Hi all,
Having an issue and unable to find a resolution, which is baffling me.
I created a small infrastructure on VMware Workstation 8, which I am now planning on moving to our test infrastructure, before moving to our live environment, but encountering issues.
Software used
Converter 4.3
ESXi 4.1
Workstation 8
Server 2008 R2
What I am trying to do
Move my Server 2008 virtual machine from VMware Workstation, to my ESXi 4.1 host.
The issue
Keeps on failing at 1% with the error message > FAILED: An error occurred during the conversion.
Having looked at it further on the logs, getting the following;
error = (converter.fault.CloneFault) {
Infrastructure + further info
ESXi host network = 10.1.90.1/24
Workstation 8 desktop = 10.1.90.1/24
Firewall + AV turned off on desktop.
ESXi hosts added to DNS records.
Not sure how it could be a networking issue, as I can ping it all, host/ip address.
The strange
No matter what I want to move, irrespective of it being Server 2008 R2/2003/Windows 7, all of them fail at 1%
If I move a none windows machine, such as a nested ESXi image, it transfers ok with no faults ( have not tried all OS's)
I have even removed network adapters when trying to convert the machines, but still getting the same issues.
Summary
Really baffled and confused, if anyone can help, I would be most grateful.
I have attached a copy of the last log file.
Many thanks in advanced,
Gabi.
see the below links
Sadly, that hasn't resolved the issue.
This is also the standalone converter and it's from V to V at them moment.
Interestingly enough, just tried moving Ubuntu Server and that failed too.
There is something strange going on, sure we will find it
Gabi
Could you upload the log bundle with failed task? Also you can try the conversion with latest Converter 5.0
Could you upload logs from Converter 5.0? There is no reason to use older Converter.
Thanks very much.
Sometimes there is, for instance when virtualising Server 2000, anything over 3.0.3 doesn't work
Thought I would test it on 4.3, but no luck.
Anyhow, back on 5.0 and attached are the logs,
The error message on 5.0 is slightly different, it states "The operation experienced a network error", i'll have more of a look this end.
Thank you ever so much, really appreciated.
Gabi.
Could you verify the following things: the user you logged in is *local* administrator, and UAC is disabled?
Hi,
I have domain rights, not logged in as the "local" admin though. Never do.
UAC, horrible thing, turned off already.
AV is off.
FW is off.
No funny apps are on.
Many thanks,
Gabi.
But you must verify that your user has *local* administrator rights?
User has local admin rights, no problems in that end.
I have tried converter on several machines, so that might not be the issue.
Must be the hosts, I implemented the installation through vmware workstation on USB sticks, could it be that something has gone wrong there?
Alternatively, I will have to redo the certificates as per one of the KB's, but I would rather that be last resort.
Gabi
The fail is "Network error" which means that your source if OK but destinations has the problem, you can point in this direction.
Hi,
Thank you for replying.
I have tried two destinations.
Both same hardware. ML110 G6's, with 16GB ram and 250GB Sata.
Host 1 ) 10.1.90.10
Host 2 ) 10.1.90.11
Workstation ) 10.1.90.100
Host 1 and 2 have a USB installation of 4.1, which was installed via Workstation 8 on USB.
Please can you explain to me what "you can point in this direction." means?
Once again,
Thank you very much,
Gabi
I think that you can check (or change) something in network...
Also try to do disk-based V2V instead of volume-based V2V (because Linux V2V is disk-based).
Thank you for answering this ZippyDaMCT
Any reason why you went to 4.1 and then tested it out?
I tried going down to 4.3 from 5.0, still failed, tried to do an OVF but that failed when I imported it to ESXi, stating it was of a different config and not compatible (apologies, cannot remember the exact error message)
Really unsure as to why this is happening, it's not something complicated we are doing :s
Yes, because it has the option to export to .ovf and seemed to always work for me, even for tricky VM's like vCloud Director, vShields etc...
Reach out to your VMware Account Manager as they should be able to source it via an SE.
Regards