On Mon, 2014-12-08 at 15:11 +, Anthony PERARD wrote:
> > > The patch intend to get the tty path on the first call of GetXMLDesc.
> >
> > Doesn't it actually do it on domain start (which makes more sense to me
> > anyway).
>
> Just a wording issue. I meant: Have GetXMLDesc always return the pa
On Mon, Dec 08, 2014 at 11:59:44AM +, Ian Campbell wrote:
> On Fri, 2014-12-05 at 16:30 +, Anthony PERARD wrote:
>
> Jim Fehlig maintains the libxl driver in libvirt, so you should CC him
> (I've done so here...)
Thanks.
> > The path to the pty of a Xen PV console is set only in
> > virD
On Fri, 2014-12-05 at 16:30 +, Anthony PERARD wrote:
Jim Fehlig maintains the libxl driver in libvirt, so you should CC him
(I've done so here...)
> The path to the pty of a Xen PV console is set only in
> virDomainOpenConsole. But this is done too late. A call to
> virDomainGetXMLDesc done b
Not really familiar with libvirt, but...
On Fri, 5 Dec 2014 16:30:06 +
Anthony PERARD wrote:
> The path to the pty of a Xen PV console is set only in
> virDomainOpenConsole. But this is done too late. A call to
> virDomainGetXMLDesc done before OpenConsole will not have the path to
> the pty
The path to the pty of a Xen PV console is set only in
virDomainOpenConsole. But this is done too late. A call to
virDomainGetXMLDesc done before OpenConsole will not have the path to
the pty, but a call after OpenConsole will.
e.g. of the current issue.
Starting a domain with ''
Then:
virDomainGe
Hi,
I'm trying to fix an issue when using OpenStack with libvirt+xen (libxenlight).
OpenStack cannot access the console output of a Xen PV guest, because the XML
generated by libvirt for a domain is missing the path to the pty. The path
actually appear in the XML once one call virDomainOpenConsole
