qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: John Snow <jsnow@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Gustavo Romero" <gustavo.romero@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>
Subject: Re: [PATCH] tests/functional: add --debug CLI arg
Date: Fri, 19 Sep 2025 08:13:21 +0200	[thread overview]
Message-ID: <835bdd7f-3662-4fd0-be2c-1fc1bca030a9@redhat.com> (raw)
In-Reply-To: <CAFn=p-Z_Du_xbOKg+2wMPzshgOT1MX+AKLNNE9FLpEp+gkQLhQ@mail.gmail.com>

On 15/09/2025 21.54, John Snow wrote:
> On Tue, Sep 9, 2025 at 6:37 AM Thomas Huth <thuth@redhat.com> wrote:
>>
>> On 07/08/2025 23.46, John Snow wrote:
>>> On Thu, Jul 24, 2025 at 3:47 PM Thomas Huth <thuth@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



  reply	other threads:[~2025-09-19  6:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  6:08 [PATCH] tests/functional: add --debug CLI arg Manos Pitsidianakis
2025-07-16 16:23 ` Pierrick Bouvier
2025-07-17  8:42 ` Alex Bennée
2025-07-17  8:46   ` Thomas Huth
2025-07-17 10:36     ` Alex Bennée
2025-07-21  7:25       ` Thomas Huth
2025-07-17  8:47   ` Manos Pitsidianakis
2025-07-17 10:04     ` Alex Bennée
2025-07-17 10:13       ` Manos Pitsidianakis
2025-07-21 20:38   ` John Snow
2025-07-24 19:47     ` Thomas Huth
2025-08-07 21:46       ` John Snow
2025-09-09 10:37         ` Thomas Huth
2025-09-15 19:54           ` John Snow
2025-09-19  6:13             ` Thomas Huth [this message]
2025-07-17  9:21 ` Daniel P. Berrangé
2025-07-17  9:27   ` Manos Pitsidianakis
2025-07-17  9:39     ` Daniel P. Berrangé
2025-07-17 10:02       ` Manos Pitsidianakis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835bdd7f-3662-4fd0-be2c-1fc1bca030a9@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=gustavo.romero@linaro.org \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).