© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The /etc/init/hvc0.conf file is created by the installer (finish-install, 90console). The code that adds it is in the following conditional:
elif [ -e /sys/bus/xen ] && [ -e /dev/hvc0 ]; then
Until raring, we didn't have Xen or hvc_console support on armhf, so this code branch was never taken.
We're only seeing this now because our testing of highbank raring has been all based on quantal->raring upgrades, where obviously the installer code does not run. But, once we had a working installer (yesterday), we began hitting it reliably.
Here's a change to finish-install that avoids creating an upstart job for the hvc0 getty on armhf/generic systems. Perhaps this can serve as a workaround until the kernel can be fixed?
I've investigated kernel cmdline options we could pass to serve as a documented workaround, but came up empty handed. I found no option to disable xen at runtime (avoiding the instantiation of /sys/bus/xen), and no option to disable the hvc_console driver, which is statically linked.