as described in the troubleshooting, a serial console can be added with
args: -serial unix:/var/run/qemu-server/<VMID>.serial,server,nowait
why not make that default? the vga console would still exist unless the user disabled that within the vm.
then qm could have a console command for linux, bsd etc kvm instances. along with a quick, easy way to get to consoles from slow connections (cell phones) or troubleshooting, automated setup can then go something like this.
0. make template, with serial enabled, no nics defined
1. make instance
2. the script connects over serial to configure networks, get host keys, install user keys, etc
3. instance is shutdown
4. new devices,nics etc, are added
5. instance is booted and ready for use. this is where ansible, puppet, etc can take over.
in other words, roughly whats already possible with containers.
socat can expose that to the network if the user wants. maybe that could be provided the rest api too.
args: -serial unix:/var/run/qemu-server/<VMID>.serial,server,nowait
why not make that default? the vga console would still exist unless the user disabled that within the vm.
then qm could have a console command for linux, bsd etc kvm instances. along with a quick, easy way to get to consoles from slow connections (cell phones) or troubleshooting, automated setup can then go something like this.
0. make template, with serial enabled, no nics defined
1. make instance
2. the script connects over serial to configure networks, get host keys, install user keys, etc
3. instance is shutdown
4. new devices,nics etc, are added
5. instance is booted and ready for use. this is where ansible, puppet, etc can take over.
in other words, roughly whats already possible with containers.
socat can expose that to the network if the user wants. maybe that could be provided the rest api too.
Last edited: