The slightly more long-winded analysis I tossed in an email a few minutes ago:
So, there are two (maybe three) issues in play with this specific bug. 1) The console wasn't in use as "The Console" when we installed, which we (probably incorrectly, in this case) key off of to decide what console to set up. 2) The console he set up was using an old kimchi default that used a non-standard address we don't look for. Newer versions of kimchi are meant to use a more standard address to work around that, but it's still an Ubuntu bug that we blatantly ignore random consoles. 3) He may not have had that console configured at install time at all, and we only probe for and setup up console jobs in the installer, we make no attempt to do so at boot time. So, if new consoles were to show up on second or fifth boot, tough look, no console for you. The first two bugs are ones we can and should fix in trusty. The third is probably a wart we need to live with, but can probably fix a bit better with systemd in 15.04/15.10/16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391919 Title: ISST-KVM:Ubuntu14.04: guest console not accessible but ssh and ping works fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
