Dynamips hypervisor process has stopped, return code: -11
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 405
- Forks
- 99
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
I am getting this error:
Dynamips hypervisor process has stopped, return code: -11
C3725 'Ghost': generic_nvram_extract_config: Unknown error -61605
This happens when s0/0 is configured on either R1 and R2 (configured similar to below) but not when I configure f0/0 on either router.
I did see the bug from 2018 about compiling the i386 version just wanted to check if that would still be a viable solution or if this is a different bug
Running GNS3 and dynamips on arch linux
Router R1 is stopped
Running on server mythbox with port 3080
Local ID is 1 and server ID is 376bdbb8-e6d0-469f-ac63-78c9dcbe1abe
Dynamips ID is 1
Hardware is Dynamips emulated Cisco c3725 with 256MB RAM and 256KB NVRAM
Console is on port 5001 and type is telnet, AUX console is on port None
IOS image is "c3725-advsecurityk9-mz.124-3.image"
with idlepc value of 0x60752990, idlemax of 500 and idlesleep of 30 ms
PCMCIA disks: disk0 is 0MB and disk1 is 0MB
slot 0 hardware is GT96100-FE with 2 ports
FastEthernet0/0 connected to Switch1 on port Ethernet0
FastEthernet0/1 is empty
WIC-2T installed in WIC slot 0 with 2 ports
Serial0/0 connected to R2 on port Serial0/0
Serial0/1 is empty
WIC-2T installed in WIC slot 1 with 2 ports
Serial0/2 is empty
Serial0/3 is empty
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash with Serial0/0 configured between the two C3725 routers on Arch Linux, then inspect the Dynamips path around generic_nvram_extract_config and the -11 process exit. Done means the same topology runs without the hypervisor stopping and the reported error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100