Difference between Aboot-veos-serial-8.0.0.iso vs Aboot-veos-8.0.0.iso

When booting up veos aboot-serial will send the console output (boot messages) to the serial port instead of the video port console (vga). You can still login both ways (you’ll get a login prompt at the completion of booting) but you will not see any of the boot/initialization messages on the VGA output, but instead on your serial port only.
If you’re just using the VGA console in VirtualBox, qemu, etc on your laptop, you’re probably better off to use the standard aboot image so you can see it on the console as you start up your vm.

On the other hand, using the serial aboot is really useful for headless VM’s where you would want to send all console output to a serial port (really a host pipe).

You’ll need to enable a serial port and create a host pipe for this to work.
Set this under your VM settings and select ’Create Pipe’. Define this for an appropriate location for your system, such as /tmp/veos-console

Then you can use socat if you want to telnet to it.
$ socat UNIX-CONNECT:/tmp/veos-console TCP-LISTEN:7001,reuseaddr=1

$ telnet localhost 7001
Trying 127.0.0.1…
Connected to localhost.
Escape character is ’^]’.

vEOS login:

Hope that clarifies things.

-J

Hi there!

If you use the aboot ISO with serial in the name, it will output to a virtual serial port. If you use the one without serial in the name, it outputs directly to the VM console.

If you use the serial image, make sure to attach the serial port first, or it won’t boot.

Hope that helps!

Alex

If you’re using KVM as your hypervisor and you’re using the Aboot-veos-serial image, you can access the console simply by typing ”virsh console <domainname>”. All bootup/shutdown/console messages will appear there instead of the virtual VGA console.