This is functional and tested in maverick AMIs with cloud-init 0.5.15-0ubuntu2 (20100916.1 and later). I decided that I basically had 3 options: a.) disable plymouth b.) fix/add support to plymouth to, when configured as such, write data to /dev/console as it would have written to /dev/tty7 (or /dev/XXXX when it sees console=XXXX on the command line). c.) boot with console=hvc0
The easiest solution was to boot with console=hvc0. If there comes a time when we are forced to merge multiple platforms (ec2 and eucalyptus) into a single pre-generated bootloader configuration file, then we'll cross that bridge then. b.) boot cloud-init (0.5.15-0ubuntu2) maverick; urgency=low * grub-legacy-ec2: boot with console=hvc0 (LP: #606373) -- Scott Moser <[email protected]> Wed, 15 Sep 2010 16:41:48 -0400 ** Changed in: cloud-init (Ubuntu Maverick) Status: Confirmed => Fix Released ** Changed in: cloud-init (Ubuntu Maverick) Assignee: (unassigned) => Scott Moser (smoser) ** Changed in: linux (Ubuntu Maverick) Importance: High => Undecided ** Changed in: linux (Ubuntu Maverick) Status: Confirmed => Invalid -- cloud-init output does not get to console when booted with pv-grub and ramdisk https://bugs.launchpad.net/bugs/606373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
