Comment 8 for bug 1391919

------- Comment From <email address hidden> 2015-05-05 05:04 EDT-------
A few more thoughts: The situation may be more complicated on PowerKVM due there being many ways to create the console device in the domain file. What I mean is: it's possible there is some domain configuration that makes 14.04 work as-is, and I just haven't seen it. The bug I just worked on had a configuration like this, with no "video" or "graphics" stanza:

<serial type='pty'>
<source path='/dev/pts/4'/>
<target type='isa-serial' port='0'/>
<alias name='serial0'/>
<address type='spapr-vio' reg='0x30001000'/>
</serial>
<console type='pty' tty='/dev/pts/4'>
<source path='/dev/pts/4'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
<address type='spapr-vio' reg='0x30001000'/>
</console>

Honestly, I'm not even clear how the console gets mapped to /dev/hvc0 on PowerKVM. On x86 KVM a similar-looking config maps the console to /dev/ttyS0. But in all cases, the device can be gleaned from /proc/consoles.

And of course, I'm considering only what is seen over the text console accessed by "virsh console". There are additional ttys mapped to the video console, and that's something that's also a bit different between x86 and Power..

Anyway, without going into more detail that may not be relevant: I'd like to understand how hvc0.conf is created, why it's not being created in some cases, and if ensuring it is created might just be the simple fix.