>>>> I doubt I manage to finish (and test!) it before xmas. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >>> Okay, the QMP interface seems sane to me (from libvirt POV). However, >>> what about other chardev types like pipe and vc? And I guess pty can be >>> covered by tty, right? > > I think that is the missing part.
Exactly. /me wades through the socket code (unix+tcp) right now, which needs some refactoring to make it fly. >> From libvirt's POV, I think the most important chardev types are pty, >> unix and tcp. The other types are pretty rarely used AFAICT. pty looks like another non-trivial challenge. How does libvirt gather the pty device today? IIRC there is some stderr parsing? Or was it info chardev? With QMP we probably want switch to a more sane model here ... cheers, Gerd
