A critical error has occurred. GNS3 and GNS3 VM
A critical error has occurred. GNS3 and GNS3 VM
I have just recently started using GNS3 and VirtualBox for a student project and I am finding it really useful.
-Windows 10 (64bit)
-Using VM for Ubuntu (64bit)
However, After coming back to it and installing new versions I have encountered a problem.
"A critical error has occurred while running the virtual machine and the machine execution has been stopped."
The VM error occurs when I try to >start my 'CiscoIOSv' or 'CiscoIOSvL2' Images on GNS3.
My VM worked smoothly before updating GNS3 to 2.2.18 and the GNS3 Server to 2.2.18.
I also re-added my Router & Switch (Cisco) Templates as it said the images were missing, Using the latest versions from the Cisco VIRL website.
PNG attached. Logs file too big to attach. Last line of log helpful?
"00:01:36.633091 emR3Debug: rc=VERR_EM_INTERNAL_ERROR
Thankyou for your assistance.
-Windows 10 (64bit)
-Using VM for Ubuntu (64bit)
However, After coming back to it and installing new versions I have encountered a problem.
"A critical error has occurred while running the virtual machine and the machine execution has been stopped."
The VM error occurs when I try to >start my 'CiscoIOSv' or 'CiscoIOSvL2' Images on GNS3.
My VM worked smoothly before updating GNS3 to 2.2.18 and the GNS3 Server to 2.2.18.
I also re-added my Router & Switch (Cisco) Templates as it said the images were missing, Using the latest versions from the Cisco VIRL website.
PNG attached. Logs file too big to attach. Last line of log helpful?
"00:01:36.633091 emR3Debug: rc=VERR_EM_INTERNAL_ERROR
Thankyou for your assistance.
- Attachments
-
- VBox.png (10.06 KiB) Viewed 3358 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: A critical error has occurred. GNS3 and GNS3 VM
Zipped logs fit.Seannn wrote:Logs file too big to attach.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log.
Search the far left tab's log for this text:
Attempting fall back to NEM
If you find it, Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Re: A critical error has occurred. GNS3 and GNS3 VM
-----------------------------------------------------------------------------------------------scottgus1 wrote:Zipped logs fit.Seannn wrote:Logs file too big to attach.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log.
Search the far left tab's log for this text:
Attempting fall back to NEM
If you find it, Hyper-V is enabled and needs to be disabled. See [REMOVED]HMR3Init: Attempting fall back to NEM (Hyper-V is active)[-].
If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Hello Scott, Thankyou for your quick reply!
ctrl-f in far-left log 'VBox.log' returns no line of that search or anything similar.
Logs zipped and attached. Thankyou!
- Attachments
-
- GNS3 VM 1-2021-03-04-19-39-05.zip
- (171.63 KiB) Downloaded 31 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: A critical error has occurred. GNS3 and GNS3 VM
Allocation of resources you don't have.
Why have you reduced graphics RAM to less than the template value? Increase to 128MB.
Reduce RAM allocation to 6144MB. I would also reduce the cores to 2. Throwing idle resources at a VM won't make it faster.00:00:03.147395 Host RAM: 16319MB (15.9GB) total, 8673MB (8.4GB) available
...
00:00:03.513889 RamSize <integer> = 0x0000000235800000 (9 487 515 648, 9 048 MB, 8.8 GB)
00:00:03.513887 NumCPUs <integer> = 0x0000000000000004 (4)
Why have you reduced graphics RAM to less than the template value? Increase to 128MB.
00:00:03.514131 VRamSize <integer> = 0x0000000000900000 (9 437 184, 9 MB)
Re: A critical error has occurred. GNS3 and GNS3 VM
Thankyou for your assistance.mpack wrote:Allocation of resources you don't have.Reduce RAM allocation to 6144MB. I would also reduce the cores to 2. Throwing idle resources at a VM won't make it faster.00:00:03.147395 Host RAM: 16319MB (15.9GB) total, 8673MB (8.4GB) available
...
00:00:03.513889 RamSize <integer> = 0x0000000235800000 (9 487 515 648, 9 048 MB, 8.8 GB)
00:00:03.513887 NumCPUs <integer> = 0x0000000000000004 (4)
Why have you reduced graphics RAM to less than the template value? Increase to 128MB.00:00:03.514131 VRamSize <integer> = 0x0000000000900000 (9 437 184, 9 MB)
I Just shot the RAM up and made sure to keep it in the green. I have now changed my RAM to 6144MB and reduced the cores to 2. I also fixed the video memory, it lowered after the update to 8mb.
The VM still crashes but I believe it to be an issue with GNS3 and the Cisco Images. As loading other Virtual devices in GNS3 works normally.
Thanks again.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: A critical error has occurred. GNS3 and GNS3 VM
Yes, I think that you're right. I assume that you're using CISCO VIRL images that use QEMU/KVM. Your settings for nested virtualization are correct for that. We have another user with a comparable problem and the same type of crash, trying to use an Android emulator. I'd suggest to create a ticket in the Bugtracker.Seannn wrote:The VM still crashes but I believe it to be an issue with GNS3 and the Cisco Images. As loading other Virtual devices in GNS3 works normally.
Re: A critical error has occurred. GNS3 and GNS3 VM
Hello,
Can you please tell me what CPU you are using? I am experiencing the same exact problem on my one of my pc's that has an Intel cpu but not on the one with AMD.
Can you please tell me what CPU you are using? I am experiencing the same exact problem on my one of my pc's that has an Intel cpu but not on the one with AMD.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: A critical error has occurred. GNS3 and GNS3 VM
It was an "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz".
Re: A critical error has occurred. GNS3 and GNS3 VM
Yeah I have a theory that is it is some bug that involves running QEMU/KVM devices on Intel CPU's. Hopefully the next update can address this problem.fth0 wrote:It was an "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz".
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: A critical error has occurred. GNS3 and GNS3 VM
Please check if your issue is solved by VirtualBox 6.1.20 and report back.
Re: A critical error has occurred. GNS3 and GNS3 VM
It fixed the problem for me so far! : )fth0 wrote:Please check if your issue is solved by VirtualBox 6.1.20 and report back.