Re: [Qemu-devel] [PATCH v3] chardev: Allow for pty path passing.

2019-02-06 Thread Daniel P . Berrangé
On Sat, Jan 26, 2019 at 02:33:55PM +0100, Paulo Neves wrote: > If a user requires a virtual serial device like provided > by the pty char device, the user needs to accept the > returned device name. This makes the program need to > have smarts to parse or communicate with qemu to get the > pty devi

Re: [Qemu-devel] [PATCH v3] chardev: Allow for pty path passing.

2019-02-06 Thread Marc-André Lureau
Hi On Sat, Jan 26, 2019 at 2:34 PM Paulo Neves wrote: > > If a user requires a virtual serial device like provided > by the pty char device, the user needs to accept the > returned device name. This makes the program need to > have smarts to parse or communicate with qemu to get the > pty device.

Re: [Qemu-devel] [PATCH v3] chardev: Allow for pty path passing.

2019-02-01 Thread no-reply
Patchew URL: https://patchew.org/QEMU/1548509635-15776-1-git-send-email-ptsne...@gmail.com/ Hi, This series failed the docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT

[Qemu-devel] [PATCH v3] chardev: Allow for pty path passing.

2019-01-26 Thread Paulo Neves
If a user requires a virtual serial device like provided by the pty char device, the user needs to accept the returned device name. This makes the program need to have smarts to parse or communicate with qemu to get the pty device. With this patch the program can pass the path where a symlink to th