GNS3 VM cannot be imported in latest versions of VMware #1184

AJNOURI · 2017-10-01T15:17:24Z

On brand new windows installation + vmware installation, when trying to open an imported GNS3 VM:

grossmj · 2017-10-01T15:35:13Z

What VMware version did you use?

AJNOURI · 2017-10-01T15:52:52Z

14.0.0 build-6661328

grossmj · 2017-10-01T16:00:22Z

Thanks, I suspect this problem is only with the newest version of VMware.

AJNOURI · 2017-10-01T16:21:01Z

Indeed Jeremy, it works fine with the prior release 12.5.7

Maybe we should somehow inform users during GNS3 VM download.

grossmj · 2017-10-01T16:48:56Z

We need to figure this out. Let's keep that issue open for now ;)

grossmj · 2017-10-01T20:21:15Z

Seems this also happens with VMWare Fusion 10 too. Is this a temporary bug with the newest version of VMware or is this an issue with how we build the GNS3 VM.ova?

https://gns3.com/qa/gns-vm-_-vmware_unsupported-valu

julien-duponchelle · 2017-10-01T20:41:06Z

pciSlot number is annoying because we need that to make sure the OS see it in correct order. Le dim. 1 oct. 2017 à 22:21, Jeremy Grossmann <notifications@github.com> a écrit :

…

Seems this also happens with VMWare Fusion 10. Is this a temporary bug with the newest version of VMware or is this an issue with how we build the GNS3 VM.ova? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1184 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVFXfWSF4kBZ42s4EvwiPhDqXq6MNogks5sn_Q7gaJpZM4Pp7Iw> .

AJNOURI · 2017-10-02T03:32:32Z

I have tested old GNS3 VMs it is the same behavior with VMWare 14.

ziajka · 2017-10-04T07:34:12Z

Updating thread. It seems to that VMWare has dropped the support for ExtraConfig or it's a bug on WMware side. We will try to contact with VMWare and get an answer.

tani10 · 2017-10-09T06:09:17Z

I had the same problem.The solution: First you install GNS3 VM.ova on VMWare 12 and then just upgrade to VMWare 14. It works fine.

grossmj · 2017-10-12T09:23:32Z

I have posted on VMware forum about this problem: https://communities.vmware.com/message/2711239#2711239

grossmj · 2017-10-13T11:51:08Z

Note that VIRL has similar issues: https://learningnetwork.cisco.com/thread/120789 and https://learningnetwork.cisco.com/thread/120925

jsicuran · 2017-10-16T02:13:27Z

I did exactly what Tani10 mentioned "I had the same problem.The solution: First you install GNS3 VM.ova on VMWare 12 and then just upgrade to VMWare 14. It works fine."

No luck and it mucked up my VIRL setup too. I opened ticket with VMware and posted link to one of the other threads here about this. This is nonsense to pay for an in place upgrade to 14 and it breaks your other tools.

jsicuran · 2017-10-16T02:22:25Z

Here is what I posted at VMware for I just purchased the 14 upgrade last week. This is just unacceptable.
Plus I hear 12 will be EOL in Feb 18.

Note:I removed VMware key and it fixed it so now it runs but it blew up my Cisco VIRL and GNS 3 installations. This is unacceptable what kind of junk release is this. I rely on your product as a solid tool. I should not have to downgrade to get my other tools working because 14 has issues. See support thread at https://gns3.com/qa/unable-to-import-gns3-vm-2-0-3-i

julien-duponchelle · 2017-10-16T11:46:53Z

We can strip network settings with that:
https://github.com/GNS3/gns3-vm/blob/master/fix_vmware_ova_network.py

But not sure why VMware dropped it. Could be intersting to see what is inside the file .ova when you export it in VMware 14

ziajka · 2017-10-16T12:08:54Z

Hi @noplay ,

Yes, stripping that config makes no issue (ESXi release is without ExtraConfig and it can be imported).

I tried to export in VMware 14, basically ExtraConfig is dropped at all.

I'm thinking if we really need that ExtraConfig. We obtain IP in "a guest-way":

https://github.com/GNS3/gns3-server/blob/master/gns3server/controller/gns3vm/vmware_gns3_vm.py#L142

and only if it fails we fall-back to:

https://github.com/GNS3/gns3-server/blob/master/gns3server/controller/gns3vm/vmware_gns3_vm.py#L150

which requires correct order of interfaces.

You know maybe if there are any case that we really need it?

We're also thinking to modify VMX file before running GNS3 VM (after import).

Thanks and cheers,
Dominik

ziajka · 2017-10-17T13:45:09Z

I think I was able to solve the issue, except hardware virt. enabled on default. Test VM will come with RC3 which should be in this week.

tani10 · 2017-10-17T17:15:59Z

Sorry for that .It works fine to me On Monday, 16 October 2017, 05:13:33 EEST, AMILABS <notifications@github.com> wrote: I did exactly what Tani10 mentioned "I had the same problem.The solution: First you install GNS3 VM.ova on VMWare 12 and then just upgrade to VMWare 14. It works fine." No luck and it mucked up my VIRL setup too. I opened ticket with VMware and posted link to one of the other threads here about this. This is nonsense to pay for an in place upgrade to 14 and it breaks your other tools. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Set vhv.enable before run for VMware. Fixes #1184

ziajka · 2017-10-19T09:16:30Z

This version should run on VMware 14 and older:

https://github.com/GNS3/gns3-gui/releases/download/v2.1.0rc3/GNS3.VM.VMware.Workstation.2.1.0rc3.zip

Please test and if works fine then I will close this issue.

bigbigmo · 2017-10-19T11:04:03Z

IT WORK!
But you need install same version on your local machine
Write pls actual link for downloading version 2.1.0rc3 for mac

Gauravism2017 · 2017-10-19T19:52:35Z

where i can get v2..1.3 for windows to be installed on local machine

dwright726 · 2017-10-19T21:15:07Z

The matching local installation can be found here :)

https://github.com/GNS3/gns3-gui/releases/tag/v2.1.0rc3

onpaws · 2017-10-20T21:51:04Z

Would it possible to enable VT-x/EPT by default?
I just downloaded and installed 2.1.0rc3 image and noticed it seems to be off by default.

As you know this is necessary for best possible Qemu support.

macOS 10.13
VMware Fusion 10.0.1
GNS3 2.1rc3 + appliance

onpaws · 2017-10-20T21:51:54Z

The correct line to add to the .vmx (Virtual Machine definition file) is
vhv.enable = "TRUE"

I think we should be able to add it to the .OVF file inside the appliance

If possible seems good to provide the best possible Qemu support by default, no?

AJNOURI · 2017-10-21T05:18:09Z

works with rc3 VM

grossmj · 2017-10-21T05:19:12Z

@AJNOURI do you have KVM support in the VM?

AJNOURI · 2017-10-21T05:55:02Z

Looks OK (had to check the option in VM processor)

AJNOURI · 2017-10-21T06:01:02Z

By the way @grossmj
Looks like Vmware 14 uses different default location for VMs (C:\Users{user}\Documents\Virtual Machines)

and GNS3 looks for (C:\Users{user}\Documents\My Virtual Machines), that's why it cannot detect GNS3 VM nor its IP.

I had to rename the default "Virtual Machines" to "My Virtual Machines" for GNS3 to detect GNS3 VM.

Should I open a new issue?

grossmj · 2017-10-21T06:07:01Z

Yes please.

onpaws · 2017-10-23T00:53:33Z

@AJNOURI
You had to check the Virtualize VT-x/EPT checkbox yourself, right?
I'm suggesting it would be ideal if the appliance was already configured for that.

@grossmj
If you could please direct me to the repo for the GNS3 VM I'd be happy to try and submit a PR.

ziajka · 2017-10-23T05:39:15Z

Hi @onpaws,

You're right, when you just load GNS3 VM (without using GNS3) then this option is not enabled. This is because VMware 14 doesn't allow to pass this value. I was trying different options and none of them were working. You may try to do this on your computer and see if you can export -> change VM -> import VM. Any ideas which may enabled it on default are very welcome.

In case you load VM via GNS3 then we add option "vhv.enable = "TRUE"" directly to VMX before start.
Cheers,
Dominik

grossmj · 2017-10-23T06:25:29Z

@onpaws this is the GNS3 VM repo, please feel free to try: https://github.com/GNS3/gns3-vm

In case you load VM via GNS3 then we add option "vhv.enable = "TRUE"" directly to VMX before start.

Indeed, the only problem is when an user doesn't start the VM using GNS3, for example a remote GNS3 VM

onpaws · 2017-10-23T15:18:12Z

Gotcha, it sounds like VMware appliance files don't support this particular setting.
Would be nice to know if that's deliberate or support just may be lagging on VMware's side.

Has anyone filed a bug with VMware before?

grossmj · 2017-10-23T15:32:47Z

I only posted on VMware community forums: https://communities.vmware.com/message/2714144#2714144

AJNOURI · 2017-10-23T22:53:06Z

@onpaws , indeed I had to check it. It was unchecked by default.

grossmj · 2017-10-24T06:13:31Z

VMware 14 ignores the vhv.enable parameter in the .ovf file inside the .ova. Can you confirm that the Virtualize VT-x/EPT is checked when starting the GNS3 VM using the GNS3 GUI?

grossmj · 2017-10-24T07:26:58Z

I have tried on Windows. Importing the last GNS3 VM 2.1 RC3 into VMware 12.x: Virtualize VT-x/EPT was automatically checked as expected. I did the same with VMware 14 and the option was not checked after importing the OVA. Starting the VM from the GNS3 GUI and the option was checked.

I think we cannot do anything more from our side. Maybe VMware is going to fix this or provide a way to automatically activate the Virtualize VT-x/EPT setting on OVA import. Also, we are not the only ones affected by this problem: https://learningnetwork.cisco.com/thread/120789

grossmj added the Bug label Oct 1, 2017

grossmj added this to the 2.1 milestone Oct 1, 2017

AJNOURI closed this as completed Oct 1, 2017

grossmj reopened this Oct 1, 2017

grossmj assigned ziajka Oct 1, 2017

grossmj changed the title ~~Unsupported value ethernet~~ GNS3 VM cannot be imported in latest versions of VMware Oct 12, 2017

ziajka added a commit that referenced this issue Oct 18, 2017

Set vhv.enable before run for VMWare 14. Fixes #1184

44efab1

grossmj added a commit that referenced this issue Oct 18, 2017

Merge pull request #1198 from GNS3/vmware-config

d2a7f72

Set vhv.enable before run for VMware. Fixes #1184

grossmj closed this as completed Oct 19, 2017

grossmj reopened this Oct 21, 2017

grossmj closed this as completed Oct 24, 2017

GNS3 VM cannot be imported in latest versions of VMware #1184

GNS3 VM cannot be imported in latest versions of VMware #1184

Comments

AJNOURI commented Oct 1, 2017

grossmj commented Oct 1, 2017

AJNOURI commented Oct 1, 2017

grossmj commented Oct 1, 2017

AJNOURI commented Oct 1, 2017

grossmj commented Oct 1, 2017

grossmj commented Oct 1, 2017 • edited

julien-duponchelle commented Oct 1, 2017 via email

AJNOURI commented Oct 2, 2017

ziajka commented Oct 4, 2017

tani10 commented Oct 9, 2017

grossmj commented Oct 12, 2017

grossmj commented Oct 13, 2017

jsicuran commented Oct 16, 2017

jsicuran commented Oct 16, 2017

julien-duponchelle commented Oct 16, 2017

ziajka commented Oct 16, 2017

ziajka commented Oct 17, 2017

tani10 commented Oct 17, 2017 via email

ziajka commented Oct 19, 2017

bigbigmo commented Oct 19, 2017 • edited

Gauravism2017 commented Oct 19, 2017 • edited

dwright726 commented Oct 19, 2017

onpaws commented Oct 20, 2017 • edited

onpaws commented Oct 20, 2017 • edited

AJNOURI commented Oct 21, 2017

grossmj commented Oct 21, 2017

AJNOURI commented Oct 21, 2017 • edited

AJNOURI commented Oct 21, 2017 • edited

grossmj commented Oct 21, 2017

onpaws commented Oct 23, 2017

ziajka commented Oct 23, 2017

grossmj commented Oct 23, 2017 • edited

onpaws commented Oct 23, 2017

grossmj commented Oct 23, 2017

AJNOURI commented Oct 23, 2017

grossmj commented Oct 24, 2017

grossmj commented Oct 24, 2017

grossmj commented Oct 1, 2017 •

edited

bigbigmo commented Oct 19, 2017 •

edited

Gauravism2017 commented Oct 19, 2017 •

edited

onpaws commented Oct 20, 2017 •

edited

onpaws commented Oct 20, 2017 •

edited

AJNOURI commented Oct 21, 2017 •

edited

AJNOURI commented Oct 21, 2017 •

edited

grossmj commented Oct 23, 2017 •

edited