VMware Cloud Community
fer82
Contributor
Contributor

Failed p2v redhat with converter 4 Standalone.

Hello,

I'm trying to p2v a redhat in a HP BL460c with the new converter 4 standalone.

I give an error "Unable to connect to the Converter helper server on the target virtual machine". And the Status on the "task progress" tab is "FAILED. Failed to communicate with the remote host, either due to network errors or because the host is not responding".

I'll found this error in documentation & forums, but I have no luck, maybe someone can help me with this issue. I attach the log files.

Thanks a lot.

Reply
0 Kudos
15 Replies
vmweathers
Expert
Expert

Converter Standalone 4.0's Linux P2V feature requires a helperVM in the destination ESX to perform the cloning.

1. We create the targetVM using the configured parameters, then boot it up with a live CD containing our helperVM bits (so it is on the same virtual network as the targetVM was configured to be).

2. Then the Converter server machine contacts the helperVM on port 443 (so there needs to be reachability from the Converter server to the helperVM on the targetVM's virtual network).

3. Then the helperVM contacts the source machine on port 22 (so there needs to be reachability from the targetVM's virtual network to the source machine).

4. Finally (and most probably your issue), the helperVM requires DHCP service in the targetVM's virtual network, unless you explicitly configure the Helper VM Network settings in the 3rd page of the Converter wizard, and setup static IP configuration for the helperVM.

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)
Reply
0 Kudos
fer82
Contributor
Contributor

Hi vmweathers, and thanks for your answer.

Just a concept question: As I understand, the helperVM and the targetVM are the same (when the converter ends his job, helperVM shutdown and becomes targetVM). Isn't it?

Well, revising the logs I found that Converter fails when source machine is calling via 443 port the helperVM. I don't understand why, because like you purpose, I configured the network settings in 3rd page of the Converter wizard, and I know that there are connectivity between the source network and the helperVM network.

The only step that I didn't follow as you say is the first:

"1. We create the targetVM using the configured parameters, then boot it up with a live CD containing our helperVM bits ".

As I read in the documentation "... the helperVM boots from an *.iso file that is located on the converter server machine".

I'm a bit confused, because I don't have any *.iso nor any live CD! :S Is this an automatic process of the converter4 or really I need to give an *.iso for booting the helperVM? If this is the case, where and when I could tell the converter where is the *.iso???

Thanks a lot!!!

Reply
0 Kudos
jasoncllsystems
Enthusiast
Enthusiast

Assign an IP address for helper server.

Regards,

CLL SYSTEMS

MALAYSIA VMWARE COMMUNITIES

http://www.malaysiavm.com
Reply
0 Kudos
fer82
Contributor
Contributor

The HelperVM already have an IP.

Thanks and regards.

Reply
0 Kudos
vmweathers
Expert
Expert

Just a concept question: As I understand, the helperVM and the targetVM are the same (when the converter ends his job, helperVM shutdown and becomes targetVM). Isn't it?

Yup, you got it!

Well, revising the logs I found that Converter fails when source machine is calling via 443 port the helperVM. I don't understand why, because like you purpose, I configured the network settings in 3rd page of the Converter wizard, and I know that there are connectivity between the source network and the helperVM network.

You sure there's no firewall or anything else? Would you mind uploading your logs? (Send me a private mail if you're not comfortable uploading them.) You could boot your own live CD (I like Ubuntu for this since it has a "try it now" feature) on a new VM you create with the same network settings, and verify that you can reach port 443 on the new VM from the Converter server. Then from the new VM ssh to the source system and make sure it connects.

Is this an automatic process of the converter4 or really I need to give an *.iso for booting the helperVM?

This is a fully automated process.

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)
fer82
Contributor
Contributor

Hi, I solved my issue. There was network troubles. Now It's running fine.

Best regards.

Reply
0 Kudos
boamek
Contributor
Contributor

Could you elaborate on what your network problems were ? I'm running into a similar situation.

Reply
0 Kudos
arusso
Contributor
Contributor

I wouldn't mind hearing how you resolved this as well. I'm getting the same error although we have assigned a static IP to the helper VM. We are trying to clone a live RH AS 4 server and the conversion get's as far as creating the target VM and starting it but then it just sits at the 1% complete mark. If I open the console for the helper/target VM, the last lines displayed on the console are

Setting up interface th0: done

Setting default route: done

Generating a 1024 bit RSA provate key

......++++++

................................+++++

wrting new private key to '/usr/lib/vmware-converter/ssl/rui.key'

-


Helper Thumpprint: <thumbprint>

Agent Thumbprint: <thumbprint>

and then it just seem to sit there for 20min or so and then fails saying it can't connect to the helper VM. I am using vCentre Converter Standalone v4.0.1 Build 161434

Any suggestions appreciated.

Craig

Reply
0 Kudos
boamek
Contributor
Contributor

I was able to get past the network error, there are 2 sections that need to be edited in Step #3 (View/Edit Options):

"Networks": You need to set a NIC to a VLAN that can be accessed by all parts of the Conversion, i.e. the converter, the ESX host & the original physical server.

"Helper VM Network": If the VLAN you selected above does not have DHCP, then you need to set a static IP for the Helper VM in the VLAN selected above.

This allowed me to get all the way through the conversion process, however, when I try to boot my new converted Redhat Server, I get a "can not find boot device" error. I'm still trying to figure out how to fix that one.

Hope this helps!

Reply
0 Kudos
arusso
Contributor
Contributor

Hi Boamek,

thanks for the update. One thing I noticed is that the helperVM has the NIC type set to Internal which doesn't seem right as it won't be able to connect to anything. Just curious as to why it would do this or if I am missing something. I've re-read the documents for this version and it doesn't mention anything about whether the Helpver VMs NIC should be set to Internal or LAN. I'm going to retry it seeing if I can set it to LAN and will see if I get any further. I would be interested to know if you can recall what your VM Helper NIC was configured as.

Craig

Reply
0 Kudos
arusso
Contributor
Contributor

Yep, putting the NIC to LAN did the trick. What a silly mistake on my part. Smiley Sad P2V'd ok and even booted. Yay. :smileyblush: Just hope the rest of the P2Vs go as smoothly.

Reply
0 Kudos
saleonovich
Contributor
Contributor

Hello,

thats my first post:

Anybody resolve that?

wouldn't mind hearing how you resolved this as well. I'm getting the same error although we have assigned a static IP to the helper VM. We are trying to clone a live RH AS 4 server and the conversion get's as far as creating the target VM and starting it but then it just sits at the 1% complete mark. If I open the console for the helper/target VM,  the last lines displayed on the console are

Setting up interface th0: done

Setting default route: done

Generating a 1024 bit RSA provate key

......++++++

................................+++++

wrting new private key to '/usr/lib/vmware-converter/ssl/rui.key'

-


Helper Thumpprint: <thumbprint>

Agent Thumbprint: <thumbprint>

Thank you Graig

Really apprisuated.

Alex

Reply
0 Kudos
saleonovich
Contributor
Contributor

Done myself:

set NIC to some real VLAN...(not for VM Network option), static IP, DNS suff., for Helper server .... Done.

Reply
0 Kudos
sabyr
Contributor
Contributor

Hi

I am mew to VMware and would like to convert a linux p2v server to a VM. i have convertor 4.3 standalone and ESXi 4.1 Vmware server.

after completing the convert wizard and after about 20 minutes i recive the below.

FAILED: Unable to communicate with the remote host, either due to network errors or because the host is not responding

I have done the checks suggested in the thread......setup a fixed ip for Vmware helper and diasbaled the firewall on the physical host. I believe ESXi 4.1 does not have a firewall.

What other test or things to look at to check where there is a possible communications problems.

Reply
0 Kudos
Fire07
Contributor
Contributor

Finally after the post here i found the solution and complete a migration of a ubuntu server without GUI.

But this is a old post...i dont know if anyone here still with the problem..or the doubt about this and need another solution hehe

greetings

Reply
0 Kudos