EXOS template first boot requires VNC, telnet not working

[TheNetworkIsDown]

With the empty QCOW image that is attached to the EXOS template, EXOS first needs to format the filesystem. That dialog is not displayed when using telnet to connect to the VM for some reason.

Therefore you have the impression nothing is happening, while EXOS is waiting for your input. --> You need to switch the console connection to VNC before first boot.

Either

1. make telnet work in that bootstrapping process, or
2. use VNC as the default configuration for the EXOS template. or
3. use the correct QCOW filesystem (see https://github.com/extremenetworks/Virtual_EXOS)

[grossmj]

@adosztal Do you have any comment on this? Thanks :)

[adosztal]

I'll check it, it's been a while since I last used EXOS.

[adosztal]

Could you check with the latest appliance file?

[TheNetworkIsDown]

Has anything changed in the "latest appliance file" that would make this work?
If so, I'd be willing to give it a try.
If nobody knows, then I won't waste any time testing something where no effort to fix it was given at all.
Thanks.

[adosztal]

When you start the node, you can choose from the grub menu if you want VGA or serial console. The only catch is that you have to be quick because VGA is the default and it boots that after a few seconds.

[cristian-ciobanu]

I just tested recently with the latest EXOS-VM_v32.1.1.6.qcow2 image and it boots ok when using telnet for console.
I'm not using the GNS3 registry template but a manual created one which is very similar.

By default it booted with telnet with no change required in the boot menu

 The highlighted entry will be executed automatically in 0s.                 
  Booting `Primary OS Image on (hd0,1) using serial console'

init started: BusyBox v1.31.1 ()
udevd: Starting version 244.5+
Starting ExtremeXOS 32.1.1b6