-
Notifications
You must be signed in to change notification settings - Fork 434
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
Comments
Trying same topology. GNS3 now simply displays the error message above and does not start the virtual machine, in this case XP. |
…urce of timeout errors Ref GNS3/gns3-gui#1632
Could you test with this build? |
…urce of timeout errors Ref GNS3/gns3-gui#1632
GNS3-2.0.2016-11-02-all-in-one.exe GNS3 VM 2.0.0dev4 => Traceback (most recent call last): |
Could you test this: I'm sorry but we don't reproduce that on our own VMware VMs. But you are not alone. |
@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.
|
Oh, and I'm running nightly, latest build |
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. |
I'm happy to try GNS3-2.0.2016-11-04-all-in-one.exe. Will let you know ASAP. |
Using GNS3-2.0.2016-11-04-all-in-one.exe Traceback (most recent call last): |
Again, doubt I'm being much help but..... These are the error messages (there are two "sets"). |
Error msg when Windows virtual machine above is stopped from within GNS3. |
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 |
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. |
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? |
Thanks a lot for the help |
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.
The text was updated successfully, but these errors were encountered: