On 15/09/2025 21.54, John Snow wrote:
On Tue, Sep 9, 2025 at 6:37 AM Thomas Huth <th...@redhat.com> wrote:
On 07/08/2025 23.46, John Snow wrote:
On Thu, Jul 24, 2025 at 3:47 PM Thomas Huth <th...@redhat.com> wrote:
...
Wouldn't it be possible to add the module as a wheel in python/wheels/ ?
That's maybe the easiest solution, isn't it?
The qemu.qmp wheel, yes, because it's purepython. The part I am
worried about is that by removing qemu.qmp from the tree, you cannot
just use the PYTHONPATH hack anymore to use the remaining in-tree
goodies, namely the machine module used extensively throughout
testing, because they will now rely on an external dependency.
Would it maybe be possible to add the machine part to the qemu.qmp module,
too? (Gerd also ask me at KVM forum about this, so there is certainly
interest for extending the qemu.qmp module with the machine part)
I could, can you explain a little why we want it?
I hope that Gerd can chime in, but basically he wanted to test another piece
of software in a similar way we do it in QEMU with the functional framework.
That means some function that manage the life-cycle of a QEMU VM would be handy.
It would involve
cleaning up the interfaces a good deal and while I don't think it is
hard, it will be a lot of clerical work and shuffling for a little
while. I have some drafts somewhere that add an asyncio VM appliance
to replace the existing one in the same manner as for what I did for
async QMP to help solve the complicated logging stack we have for VM
console scripts.
Having a solid justification and guinea pigs^H^H^H^H^H^H^H^H^H^H^H^H
beta users would push the project over the line for me.
I'm sure Gerd is happy to help if he can find some spare time, and I'm of
course happy to help with regards to the QEMU functional testing framework -
let me know when you've got something ready and we want to have a try to
move the functional tests to that new VM management code.
Thomas
