Am 22.01.2026 um 17:00 hat Daniel P. Berrangé geschrieben: > > Does the new program becomes basically an external project unrelated to > > QEMU, that simply talks to QMP like libvirt does? > > It could be a separate project under QEMU on github, or it could just be > binary in qemu.git. What matters is that it is out of the main QEMU process > eventually.
I think the basic requirement for any HMP replacement is that it just works, i.e. no manual setting up of sockets etc. like for qmp-shell. If it's an external process, QEMU should just launch it automatically, and the user interface should still go through the usual chardevs so that the current backends still work and the default of '-monitor vc' can be retained. (Of course, once this plumbing has been done, it could be reused for qmp-shell to provide a nicer and more integrated option there, too.) This pretty much means that it has to be in the same project, or at least a subproject that is automatically downloaded when building QEMU. Kevin
