On Mon, Dec 08, 2014 at 12:03:36PM -0700, Jim Fehlig wrote:
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, but a call
On 12/05/2014 05:30 PM, Anthony PERARD wrote:
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
On Mon, Dec 08, 2014 at 04:40:04PM +0100, Ján Tomko wrote:
On 12/05/2014 05:30 PM, Anthony PERARD wrote:
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
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, but a call after OpenConsole will.
Hi Anthony,
Thanks for the patch. Can
Anthony PERARD wrote:
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
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 'console type=pty/'
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