On Thu, Dec 10, 2009 at 01:41:39PM +, Matthew Booth wrote:
This change makes the QEMU driver get pty paths from the output of the monitor
'info chardev' command. This output is structured, and contains both the name
of
the device and the path on the same line. This is considerably more
On Wed, Nov 25, 2009 at 11:31:37AM +, Daniel P. Berrange wrote:
On Mon, Nov 23, 2009 at 12:30:29PM +, Matthew Booth wrote:
@@ -1291,7 +1330,7 @@ qemudWaitForMonitor(virConnectPtr conn,
{
char buf[4096]; /* Plenty of space to get startup greeting */
int logfd;
-int
This change makes the QEMU driver get pty paths from the output of the monitor
'info chardev' command. This output is structured, and contains both the name of
the device and the path on the same line. This is considerably more reliable
than parsing the startup log output, which requires the
On Mon, Nov 23, 2009 at 12:30:29PM +, Matthew Booth wrote:
This change makes the QEMU driver get pty paths from the output of the monitor
'info chardev' command. This output is structured, and contains both the name
of
the device and the path on the same line. This is considerably more
This change makes the QEMU driver get pty paths from the output of the monitor
'info chardev' command. This output is structured, and contains both the name of
the device and the path on the same line. This is considerably more reliable
than parsing the startup log output, which requires the
