Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GNS3 2.0.0 alpha 3 error running virtual machine (XP) #1632

Closed
jtorri opened this issue Oct 29, 2016 · 16 comments
Closed

GNS3 2.0.0 alpha 3 error running virtual machine (XP) #1632

jtorri opened this issue Oct 29, 2016 · 16 comments
Assignees
Labels
Milestone

Comments

@jtorri
Copy link

jtorri commented Oct 29, 2016

Windows 10 Prof x64 with 28gig RAM, all latest updates. VMWare Workstation 12.5.1. GNS3 2.0.0 alpha 3. Running all networks object in GNS3 VM created with GNS3 2.0.0 alpha 3 GNS3.ova.
All network objects (IOU, IOS, ASAv, IOSv, etc.) load and configure without problems. So far IOU, IOS and ASAv run without problems as does the GNS3 VM.

However, I can add a VMWare virtual machine (in this case XP) to a topology but when I start the VMware virtual machine within the topology it starts and is accessible but the following error appears as the virtual machines is starting.

untitled

@jtorri jtorri changed the title GNS3 2.0.0 alpha 3 error running virtual machine (XP0 GNS3 2.0.0 alpha 3 error running virtual machine (XP) Oct 29, 2016
@jtorri
Copy link
Author

jtorri commented Oct 29, 2016

Trying same topology. GNS3 now simply displays the error message above and does not start the virtual machine, in this case XP.

@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Oct 31, 2016
@julien-duponchelle julien-duponchelle self-assigned this Nov 2, 2016
julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Nov 2, 2016
@julien-duponchelle
Copy link
Contributor

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Nov 3, 2016
@jtorri
Copy link
Author

jtorri commented Nov 4, 2016

GNS3-2.0.2016-11-02-all-in-one.exe GNS3 VM 2.0.0dev4
Added VMWare Workstation 12.5.1 virtual machine, Lubuntu. All seemed to be working until I started the network objects. Then got this.

=> Traceback (most recent call last):
File "./gns3-server\gns3server\web\route.py", line 197, in control_schema
File "./gns3-server\gns3server\handlers\api\controller\node_handler.py", line 124, in start_all
File "./gns3-server\gns3server\controller\project.py", line 722, in start_all
File "./gns3-server\gns3server\utils\asyncio\pool.py", line 46, in join
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\asyncio\tasks.py", line 241, in _step
File "./gns3-server\gns3server\controller\node.py", line 389, in start
File "./gns3-server\gns3server\controller\node.py", line 424, in post
File "./gns3-server\gns3server\controller\compute.py", line 524, in post
File "./gns3-server\gns3server\controller\compute.py", line 354, in http_query
File "./gns3-server\gns3server\controller\compute.py", line 468, in run_http_query
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\aiohttp\client.py", line 555, in iter
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\aiohttp\client.py", line 202, in request
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\aiohttp\client_reqrep.py", line 640, in start
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\async_timeout__init
.py", line 44, in exit
concurrent.futures._base.TimeoutError

@julien-duponchelle
Copy link
Contributor

Could you test this:
https://sourceforge.net/projects/gns-3/files/Nightly%20Builds/2016-11-04/2.0/GNS3-2.0.2016-11-04-all-in-one.exe/download

I'm sorry but we don't reproduce that on our own VMware VMs. But you are not alone.

@codeassassin
Copy link

codeassassin commented Nov 4, 2016

@noplay , I am also having issues running VMware VMs inside GNS3. I experienced two issues.

1)When I go to run the VM, GNS3 appears to try, unsuccessfully, to install Virtual NICs. However, after losing internet access to my host workstation, I discovered that not only had GNS3 installed a motherload of vnet nic cards, VMware Worstation doesn't recognize the addition of said nvet cards, and it appears that the vnet interfaces I had configured for my other VMware VMs has been overwritten. Major bummer and major headache. What I did to experiance this was, after reading the error statement after starting the VM, I went to the VMware network settings like it stated, and then I just clicked the little "configure" button, as stated in the console output. I should not have clicked the little configure button.

gns3networkbug

gns3networkbug2

  1. After cycling through 19 error windows for the vnet nics I really didn't want created, and certainly didn't want overwritten, I right-clicked and attempted to start the VM again. This time, VMware Workstation does begin to start the VM. However, GNS3 waits what appears to be 5 seconds and throws an error that the VM didn't start. Even with an SSD, it's not going to start that fast.

image

@codeassassin
Copy link

Oh, and I'm running nightly, latest build

@julien-duponchelle
Copy link
Contributor

Can you open a separate issue for the missing DLL. vnetlib64.exe is not a GNS3 program we need to understand if your VMware install is broken or if it's a side effect of running it from GNS3.

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Nov 4, 2016
@jtorri
Copy link
Author

jtorri commented Nov 4, 2016

I'm happy to try GNS3-2.0.2016-11-04-all-in-one.exe. Will let you know ASAP.
I am largely guessing but I am beginning to believe the reason I generate errors you do not has to do with the difference in the way we are configuring GNS3. But, as I said, it's a guess.

@jtorri
Copy link
Author

jtorri commented Nov 5, 2016

Using GNS3-2.0.2016-11-04-all-in-one.exe
Sorry to say same as before. Able to add a VMware virtual machine but as soon as I start the network objects get the error. As I mentioned I suspect I am configuring GNS3 2.0.0 alpha 3 incorrectly.

Traceback (most recent call last):
File "./gns3-server\gns3server\web\route.py", line 197, in control_schema
File "./gns3-server\gns3server\handlers\api\controller\node_handler.py", line 124, in start_all
File "./gns3-server\gns3server\controller\project.py", line 722, in start_all
File "./gns3-server\gns3server\utils\asyncio\pool.py", line 46, in join
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\asyncio\tasks.py", line 241, in _step
File "./gns3-server\gns3server\controller\node.py", line 389, in start
File "./gns3-server\gns3server\controller\node.py", line 424, in post
File "./gns3-server\gns3server\controller\compute.py", line 524, in post
File "./gns3-server\gns3server\controller\compute.py", line 354, in http_query
File "./gns3-server\gns3server\controller\compute.py", line 468, in run_http_query
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\aiohttp\client.py", line 555, in iter
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\aiohttp\client.py", line 202, in request
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\aiohttp\client_reqrep.py", line 640, in start
File "C:\Jenkins\workspace\Nightly Branch Build Windows\Windows\python-3.5.1\lib\site-packages\async_timeout__init
.py", line 44, in exit
concurrent.futures._base.TimeoutError

@jtorri
Copy link
Author

jtorri commented Nov 6, 2016

Again, doubt I'm being much help but.....
Windows 10 Prof 64 bit, all latest OS updates. Went back to GNS3 2.0.0 alpha 3 and the GNS3 VM.ova
from that release. VMWare Workstation 12.5.1
In the topology below the error messages do not appear until I start the Window 7 virtual machine. If I merely "ignore" the error messages and keep going all seems to work. Curious?

topology

These are the error messages (there are two "sets").

ErrorMsg.txt

@jtorri
Copy link
Author

jtorri commented Nov 7, 2016

Error msg when Windows virtual machine above is stopped from within GNS3.

ErrorMsg2.txt

@jtorri
Copy link
Author

jtorri commented Nov 7, 2016

Well, never mind. I closed the above topology by closing GNS3 and then started GNS3 and opened that topology. GNS3 did start the GNS3 VM but not the VMware virtual machines. Back where I was with GNS3 2.0.0 alpha 3

@jtorri
Copy link
Author

jtorri commented Nov 7, 2016

Here's a very similar topology run on the same OS and version of VMWare but with GNS3 1.5.1. It all works as expected.

topology151

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Nov 7, 2016
@jtorri
Copy link
Author

jtorri commented Nov 8, 2016

Windows 10 Prof x64. VMWare Workstation 12.5.1. GNS3-2.0.2016-11-07-all-in-one.exe GNS3 VM version dev4. As before all network objects run from inside GNS3 VM. Windows virtual machines run in VMWare Workstation on Windows 10 running GNS3. Here's the thing, THIS TOPOLOGY ALL WORKS! None of the errors I list in previous post on this particular issue occurred.

topology1172016

@jtorri
Copy link
Author

jtorri commented Nov 11, 2016

Same environment as in my previous comment but running GNS3-2.0.2016-11-09-all-in-one.exe The problem does not appear with any consistency now. Perhaps close this one and reopen if needed?

@julien-duponchelle
Copy link
Contributor

Thanks a lot for the help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants