VMware Cloud Community
Mig29Fulcrum
Contributor
Contributor
Jump to solution

P2V Conversion issue (no connection to the helper machine) - fails at 1%

Hi,

No matter what i've tried, adding routes (route add GATEWAY dev eth0 ; route add default gw GATEWAY) , changing VLAN's before conversion start, changing helper machine IP adresses , conversion didn't work out.

I've logged in Helper machine and found out that "eth0" interface is not down and i can not bring it up, can you guys please suggest anything else i miss?

Default gateway is accessible and pingable from both ESXi server which  i'm trying to use for new  VM and also from the source Physical machine. IP address is unique in the LAN, lost in suggestions..

thanks, everyone for input

Conversion Task fails with

"Error: Unable to connect to the Converter helper server on the destination virtual mac"

Here's a screen from Helper machine -

VMWARE.png

0 Kudos
1 Solution

Accepted Solutions
Mig29Fulcrum
Contributor
Contributor
Jump to solution

Hi, the issue was that I've assigned VLANS to helper machine NIC that were defined at another vSwitch. As soon as i assigned VLAN that was created on the vSwitch which has route to source machine  - conversion started.

Notes:

vSwitches - are not able to communicate with each other.

First switch (the "wrong one" )  initially were not able to connect with source machine, missed that at first

View solution in original post

0 Kudos
3 Replies
rcporto
Leadership
Leadership
Jump to solution

Can you share the /etc/ifconfig/network-scripts/ifcfg-eth0 file from your Helper virtual machine?

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
Mig29Fulcrum
Contributor
Contributor
Jump to solution

Here is it -

the only difference in path is -

/etc/sysconfig/network-scripts/ifcfg-eth0

vmw1.png

Thanks Richardson!

0 Kudos
Mig29Fulcrum
Contributor
Contributor
Jump to solution

Hi, the issue was that I've assigned VLANS to helper machine NIC that were defined at another vSwitch. As soon as i assigned VLAN that was created on the vSwitch which has route to source machine  - conversion started.

Notes:

vSwitches - are not able to communicate with each other.

First switch (the "wrong one" )  initially were not able to connect with source machine, missed that at first

0 Kudos