EXOS on GNS3 not booting past BusyBox

[wkb289]

Trying to boot EXOS v32.6.3.126 on GNS3 v2.2.50 running as a VM on Hyper-V and cannot get past BusyBox. I don't see anything on the tutorial site about this. The only warning I see during boot is about the CPU:

Warning. Could not determine the CPU Family.
model name      : QEMU Virtual CPU version 2.5+

Attached is the full boot screen via telnet (it's a text doc; rename and take off the csv extension).

I've tried building the template using both what's built-in to GNS3 and downloading from the Github tutorial page. Files: exos.gns3a/exosvm.gns3a, EXOS-VM_v32.6.3.126.qcow2

Qemu is set to /usr/bin/qemu-system-x86_64.

The VM has ExposeVirtualizationExtensions set to true in Hyper-V.

[sam30]

It seems you're having trouble booting EXOS in GNS3 on Hyper-V. First, ensure that "Expose Virtualization Extensions" is correctly set for your GNS3 VM, as this is essential for nested virtualization. Additionally, the warning about the CPU family may indicate a need to adjust the CPU type in Hyper-V settings; try switching to a different virtual CPU type, such as Intel or AMD. It might also help to use a different version of QEMU, as specific versions can cause compatibility issues, so consider upgrading or downgrading QEMU as needed. Double-check that your GNS3 VM settings align with EXOS recommendations, including CPU allocation and memory. Review the full boot log for specific errors, and ensure your network settings in both GNS3 and Hyper-V are configured properly, as network misconfigurations can sometimes lead to boot issues. If the problem persists, reaching out to GNS3 community forums might provide additional insights, as other users may have faced similar challenges. If you can share specific error messages from the boot log, that could help pinpoint the issue further.

[Gabriel_G]

Hmm,

I'm not sure what your issue is exactly, I'm not having this problem with VMWare 32.6 so it could be hyper-V specific?

Regardless, the 'press c to continue' prompt is similar to a prompt that you see during a rescue image installation:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000098366

This makes me think that some input is being provided to the switch during bootup getting it into a pre-boot menu.
Or potentially the pre-boot environment is having some error leading to the prompt?

[wkb289]

I was just trying different commands in BusyBox and typed exit then it booted........ How can it be configured to boot without having to do that? You first have to press c to continue then exit.

c) continue with boot process
~> c
...
BusyBox v1.31.1 () built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
~ # exit
...
init started: BusyBox v1.31.1 ()
udevd: Starting version 244.5+
Starting ExtremeXOS 32.6.3b126
...
login: