Ben, Please do not change the images just yet. I'd really rather not make a change without knowing explicitly what happens in each case of the following, given the command line 'console=tty1 console=ttyS0':
a.) kvm -nographic b.) no serial device present For each of these, where does console output end up? I'm also concerned about arm arch, where ttyX might not be meaningful. It seems likely that the kernel has sane behavior, but I'd like to know for sure. case 'b' is (I believe) the case that is affecting Jeremiah. Because there is no serial device, the kernel then is selecting tty0 as the /dev/console device, and upstart is putting 'console output' cloud-init job output there. However, in the case where there *is* a serial device, I honestly cannot understand how the tty1 param would change anything. The change does seem reasonable, but I just want to avoid making arbitrary changes that we do not completely understand. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty1 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
