qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Cc: lvivier@redhat.com, farosas@suse.de, pbonzini@redhat.com,
	berrange@redhat.com
Subject: [PATCH v2 0/2] Implement -run-with exit-with-parent=on
Date: Thu,  9 Oct 2025 17:12:45 +0100	[thread overview]
Message-ID: <20251009161526.140497-1-rjones@redhat.com> (raw)

v1 was here:

https://lists.gnu.org/archive/html/qemu-devel/2025-10/msg00762.html

In v2:

 - Fix unused variable warning.

 - Remove the #ifdefs from the libqtest.c code.

 - Add the missing S-o-B in the second patch.

 - Rebase and retest.

As before, one test fails both before and after this change:

  4/405 qemu:func-quick+func-x86_64 / func-x86_64-bad_vmstate               ERROR            0.15s   exit status 1

And as before, some questions:

 - There's no way to find out if the qemu binary supports
   exit-with-parent=on except to try it.  Maybe this should be exposed
   somehow?

 - Or should we have exit-with-parent=best ?

 - On macOS I wasn't able to find a satisfactory way to force
   shutdown, except calling 'qemu_system_killed' and pretending we'd
   been killed by SIGTERM (which does at least emulate what Linux &
   FreeBSD do).  I suppose it'd be nice if there was a "killed by
   parent" reason which also forced shutdown.

Rich.




             reply	other threads:[~2025-10-09 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 16:12 Richard W.M. Jones [this message]
2025-10-09 16:12 ` [PATCH v2 1/2] Implement -run-with exit-with-parent=on Richard W.M. Jones
2025-10-10 10:09   ` Daniel P. Berrangé
2025-10-09 16:12 ` [PATCH v2 2/2] tests/qtest: Use exit-with-parent=on in qtest invocations Richard W.M. Jones
2025-10-10 10:10   ` Daniel P. Berrangé

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=20251009161526.140497-1-rjones@redhat.com \
    --to=rjones@redhat.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).