New Whonix KVM images are broken - FIX

[Lanman]

For some reason, the new 17.2.2.7 Whonix KVM images do not have console access configured, meaning that you cannot access the KVM’s without mounting the qcow2 first and making changes to /etc/default/grub. This means that in its current state, the KVM images alongside their instructions are considered broken, as following the documentation will not work without mounting the image and running the below steps manually.

@HulaHoop , are you able to release a new Whonix KVM version with the below changes to /etc/default/grub to allow console access straight after the KVM is created and started? Also unrelated, but thanks for your work on Whonix KVM, we do appreciate it.

GRUB_CMDLINE_LINUX=“console=tty0 console=ttyS0,115200n8 rootdelay=60”
GRUB_TERMINAL=“console serial”
GRUB_SERIAL_COMMAND=“serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1”

[Patrick]

@Lanman

This means that in its current state, the KVM images alongside their instructions are considered broken,

Not considered broken.

@Lanman

are you able to release a new Whonix KVM version with the below changes to /etc/default/grub to allow console access straight after the KVM is created and started?

No, unfortunately not.

There’s a reason why this is the case:
Serial Console in VirtualBox - #13 by Patrick

[Lanman]

Ah, well should there not be some sort of warning on the documentation, since if you followed the documentation you would be unable to create a Whonix KVM setup and you wouldn’t know why.