VMware Cloud Community
TT250
Contributor
Contributor
Jump to solution

SCP between 4.1 and 6.7 no matching KexAlgo

So after many years I have built a new 6.7 machine to replace my 4.1 host, I now need to migrate my VM's to the new host.

But SCP on 4.1 won't connect with error "No matching KexAlgo"

I have come across it before on some old distros but can't find how to fix it on vSphere???

Anyone got the solution?

Thanks

Rob

1 Solution

Accepted Solutions
frankenmaddin
Contributor
Contributor
Jump to solution

After running in the same trouble

login with putty on the new 6.x hypervisor

esxcli network firewall set --enabled false

deaktivate Firewall (ssh is OUTGOING disabled)

scp -oKexAlgorithms=+diffie-hellman-group1-sha1 -r root@192.168.x.x:/vmfs/volumes/datastore/nameofthevm/ /vmfs/volumes/datastore/

(192.168.x.x is the "old" 4.x hypervisor)

enable firewall

esxcli network firewall set --enabled true

View solution in original post

11 Replies
SupreetK
Commander
Commander
Jump to solution

If I understand this correctly, you want to move the VMs from 4.1 local datastore to 6.7 host local datastore? Or Is it a shared datastore? That's one big leap from 4.1 to 6.7 Smiley Wink

Cheers,

Supreet

Reply
0 Kudos
TT250
Contributor
Contributor
Jump to solution

Local to Local over network.

It's a home system so it's never really needed upgrading.

Reply
0 Kudos
TT250
Contributor
Contributor
Jump to solution

Prehaps a temporary FREENAS will be built.

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

Can you share the screenshot of the command syntax you are using and the error being reported?

Cheers,

Supreet

Reply
0 Kudos
IRIX201110141
Champion
Champion
Jump to solution

Facing this problem 2 years go when bringing a customer from 4.x to 6.5.  IIRC i "pull" the VMs rather than pushing them and i specify an old key algorythm/ cipher on command line for scp.  Not sure about  6.5.

Regards,

Joerg

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

What may be an option is https://www.virtuallyghetto.com/2012/06/how-to-copy-vms-directly-between-esxi.html

Hint: In case you want the target VMs being thin provisioned, insert the option --dm=thin behind the ovftool command.


André

Reply
0 Kudos
TT250
Contributor
Contributor
Jump to solution

i don't think ovftool exists on 4.1

I could use "converter" I guess, may try that.

Rob

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

There's neither an OVFTool nor Converter version which officially supports both, ESXi 4.1 and ESXi 6.7.

However, I was curious to see whether it will work anyway and tested with different OVFTool versions.

With the latest version 4.3, I was able to copy VMs directly from ESXi 4.1 to ESXi 6.7.

ovftool -dm=thin -ds=datastore1 vi://root@esxi41/Test-for-OVF-import vi://root@esxi67

André

Reply
0 Kudos
TT250
Contributor
Contributor
Jump to solution

one to keep in reserve that.

Spun up freenas in 5 mins, mounted NFS export on both hosts and its copying across now.

Once across will import the VM.

Cheers

Rob

frankenmaddin
Contributor
Contributor
Jump to solution

After running in the same trouble

login with putty on the new 6.x hypervisor

esxcli network firewall set --enabled false

deaktivate Firewall (ssh is OUTGOING disabled)

scp -oKexAlgorithms=+diffie-hellman-group1-sha1 -r root@192.168.x.x:/vmfs/volumes/datastore/nameofthevm/ /vmfs/volumes/datastore/

(192.168.x.x is the "old" 4.x hypervisor)

enable firewall

esxcli network firewall set --enabled true

TT250
Contributor
Contributor
Jump to solution

Wow, I come back to the same problem 2 years later, converting the same machine again.. 

 

Great Solution... 

 

 

Reply
0 Kudos