trouble with ttyS0 (cloud-init, agetty....)

Matthew Miller mattdm at
Fri Jun 14 19:47:15 UTC 2013

We added console=ttyS0 to the cloud image kernel command line, so that
console output is logged in OpenStack -- see, and also a request on
this list.

But, that doesn't exist in Amazon EC2, which ...

1. ... had the effect of making cloud-init totally fail to run (see earlier
   threads), and ....

2. results in systemd generating a getty service for ttyS0, which then fails 

Now, it happens that in EC2, we are using the menu.lst file to boot, and in
OpenStack, it's the extlinux.conf. We _could_ kludge this by putting
console=ttyS0 in extlinux.conf and console=hvc0 in menu.list. But that seems
pretty ugly.

Also, in EC2, we probably want to actually disable all agettys. But in
OpenStack, you can actually get to the console (a cool feature!) and having
a getty might be useful..... except, I realize as I'm typing, that there's
really no way to log in there without further configuration. Would it be so
awful to suppress the agettys completely by default?

Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm at>

More information about the cloud mailing list