Setting SECURETTY=YES in the context does not appear to work to enable the console

[jamie-pate]

This is the context code for SECURETTY=YES
https://github.com/OpenNebula/addon-context-linux/blob/27b1b1febabd8d0b2eda8fa4e7c59b0f452d72f0/src/etc/one-context.d/loc-35-securetty#L51

If you create a debian11 vm then the contents of /etc/pam.d/login matches this file:
https://sources.debian.org/src/shadow/1%3A4.8.1-1/debian/login.pam/

It doesn't appear to contain the correct line to match against to update the configuration correctly. Maybe a new file should just be added if the grep fails?

I have followed the instructions here:
https://docs.opennebula.io/6.6/open_cluster_deployment/kvm_node/kvm_driver.html#additional-attributes

to add the following to the kvm config:

<devices><serial type="pty"><source path="/dev/pts/5"/><target port="0"/></serial><console type="pty" tty="/dev/pts/5"><source path="/dev/pts/5"/><target port="0"/></console></devices>

And set SECURETTY=YES, but that did not enable the console in debian.

I also need to run the following inside my startup script: systemctl start [email protected]

It took me a while to figure out that I should run virsh console one-<vmid> in order to connect to the console on the correct host.

I don't know if this is a new consequence of debian's switch to systemd?