Did libvirt actually do something with the second definition, or did it ignore it? What actually created that xml - was it done by hand, by virtinst, or by virt-manager?
If libvirt actually used to parse this in a way to give you two different consoles, then libvirt in precise should handle this. But if it is just a mistaken duplicate and libvirt used to ignore it, then I'd argue that the errors in the log files are sufficiently clear, and there is no bug here.
@Torsten,
Thanks for finding this. This is interesting and may catch some other people.
In the original xml:
<console type='pty'>
<target port='0'/>
</console>
<console type='pty'>
<target port='0'/>
</console>
Did libvirt actually do something with the second definition, or did it ignore it? What actually created that xml - was it done by hand, by virtinst, or by virt-manager?
If libvirt actually used to parse this in a way to give you two different consoles, then libvirt in precise should handle this. But if it is just a mistaken duplicate and libvirt used to ignore it, then I'd argue that the errors in the log files are sufficiently clear, and there is no bug here.