qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jason Andryuk <jandryuk@gmail.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Anthony Perard <anthony.perard@citrix.com>,
	Paul Durrant <paul@xen.org>,
	xen-devel@lists.xenproject.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] xen: fix dm_restrict startup
Date: Mon, 13 Mar 2023 08:54:03 +0000	[thread overview]
Message-ID: <96d1510d9d84a3a7db0c24c430940beb33390942.camel@infradead.org> (raw)
In-Reply-To: <20230312234131.46898-1-jandryuk@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

On Sun, 2023-03-12 at 19:41 -0400, Jason Andryuk wrote:
> QEMU is failing to signal it start when launched by libxl with
> dm_restrict=1.  When xenstore_record_dm_state() is called, the
> restrictions prevent xs_open() from succeeding.  QEMU can't write
> running to the xenstore, and libxl fails the VM start up.
> 
> Pass in a open xenstore connection.  Let the call back use it and the
> close it.  Use the completed boolean to only allow it to be called once.
> This lets the xenstore connection be closed after the startup
> indication.
> 
> Fixes: ba2a92db1ff6 ("hw/xen: Add xenstore operations to allow redirection to internal emulation")
> Signed-off-by: Jason Andryuk <jandryuk@gmail.com>

Thanks. Of the possible fixes though, I don't think this is my
favourite. I think I'd prefer to go back to using the existing global
'xenstore' from xen-legacy-backend.c as I just tried in my other email.

Or, as I said there, if the write is destined to fail anyway when
xen_domid_restrict is set, why even bother to try?

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]

      reply	other threads:[~2023-03-13  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 23:41 [PATCH] xen: fix dm_restrict startup Jason Andryuk
2023-03-13  8:54 ` David Woodhouse [this message]

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=96d1510d9d84a3a7db0c24c430940beb33390942.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=anthony.perard@citrix.com \
    --cc=jandryuk@gmail.com \
    --cc=paul@xen.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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).