From: Stefan Hajnoczi <stefanha@redhat.com>
To: Matthieu Rolla <matthieu@minio.io>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v3] hw/nvme: add namespace hotplug support
Date: Mon, 13 Apr 2026 13:18:51 -0400 [thread overview]
Message-ID: <20260413171851.GA42769@fedora> (raw)
In-Reply-To: <CAPSO8MwceccK3gHgbeZi0A9=p8B9VV85whYmN1D343gV=9PucA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Mon, Apr 13, 2026 at 04:13:38PM +0200, Matthieu Rolla wrote:
> Hello Stefan,
>
> Thanks let me know how it goes.
[Resending to qemu-devel so others are aware too.]
Hi Matthieu,
Windows Server 2022 Build 20348 successfully handles NVMe Namespace List
changes with your QEMU patch.
When adding the disk a new drive appears as expected.
When removing the disk the drive disappears and there is a Windows Event
Log event about a surprise removal. Windows probably has a procedure for
safely removing drives, but this basic test seems like enough
confirmation that it is working.
Drive letters are preserved across hotplug, so I think everything is
working as expected.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2026-04-13 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPSO8MwceccK3gHgbeZi0A9=p8B9VV85whYmN1D343gV=9PucA@mail.gmail.com>
2026-04-13 17:18 ` Stefan Hajnoczi [this message]
2026-04-09 6:01 [PATCH 0/2] NVMe namespace hotplug and drive reconnection support mr-083
2026-04-10 14:30 ` [PATCH v3] hw/nvme: add namespace hotplug support mr-083
2026-04-10 14:33 ` Matthieu Rolla
2026-04-10 20:14 ` Stefan Hajnoczi
2026-04-13 15:24 ` Matthieu Rolla
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=20260413171851.GA42769@fedora \
--to=stefanha@redhat.com \
--cc=matthieu@minio.io \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.