[{"id":3675513,"web_url":"http://patchwork.ozlabs.org/comment/3675513/","msgid":"<20260409210007.GA461870@fedora>","list_archive_url":null,"date":"2026-04-09T21:00:07","subject":"Re: [PATCH 0/2] NVMe namespace hotplug and drive reconnection support","submitter":{"id":17227,"url":"http://patchwork.ozlabs.org/api/people/17227/","name":"Stefan Hajnoczi","email":"stefanha@redhat.com"},"content":"On Thu, Apr 09, 2026 at 09:01:09AM +0200, mr-083 wrote:\n> This series adds two features that together enable transparent NVMe disk\n> hot-swap simulation in QEMU, matching the behavior of physical NVMe\n> drives being pulled and reinserted in the same PCIe slot.\n> \n> Problem:\n> Currently, hot-swapping an NVMe disk in QEMU requires removing the\n> entire NVMe controller via device_del, which causes the Linux guest to\n> assign a new controller number on re-add (e.g. nvme2 becomes nvme4).\n> This breaks storage software that tracks drives by device name.\n\nHi mr-083,\nNeat, I was looking for something like this recently!\n\n> Solution:\n> Patch 1 adds hotplug support for nvme-ns devices on the NvmeBus, with\n> proper Asynchronous Event Notification (AEN) so the guest kernel detects\n> namespace changes. This allows namespace-level hot-swap without removing\n> the NVMe controller.\n> \n> Patch 2 adds a drive_insert HMP command that reconnects a host block\n> device file to an existing guest device after drive_del. This is the\n> counterpart to drive_del for non-removable devices where\n> blockdev-change-medium cannot be used.\n> \n> The recommended hot-swap sequence is:\n> 1. drive_del # disconnect backing store\n> 2. drive_insert # reconnect backing store\n\nIs it possible to achieve this with device_del + device_add instead of\nintroducing a new monitor command?\n\ndevice_del nvme-ns2\nblockdev-del nvme-ns2-blk (or drive_del)\n...\nblockdev-add nvme-ns2-blk,... (or drive_add)\ndevice_add nvme-ns,id=nvme-ns2,nsid=2,drive=nvme-ns2-blk\n\n> 3. pcie_aer_inject_error SDN # trigger controller reset\n\nIs NVMe AEN insufficient to get the guest to recognize the Namespace\nchange? I looked at the Linux NVMe driver code recently and got the\nimpression it would process changes to the Namespace list upon receiving\nthe NVMe AEN.\n\n> After this sequence, the guest sees the same controller and namespace\n> names (e.g. /dev/nvme2n1 remains /dev/nvme2n1), and the NVMe driver\n> recovers transparently via the standard AER recovery path.\n> \n> Tested with:\n> - Linux 6.1 guest on QEMU aarch64 with HVF (macOS)\n> - NVMe subsystem model with multipath disabled\n> - DirectPV and MinIO AIStor storage stack\n> \n> mr-083 (2):\n> hw/nvme: add namespace hotplug support\n> block/monitor: add drive_insert HMP command\n> \n> block/monitor/block-hmp-cmds.c | 59 +++++++++++++++++++++++\n> hmp-commands.hx | 18 +++++++\n> hw/nvme/ctrl.c | 85 ++++++++++++++++++++++++++++++++++\n> hw/nvme/ns.c | 1 +\n> hw/nvme/subsys.c | 2 +\n> include/block/block-hmp-cmds.h | 1 +\n> 6 files changed, 166 insertions(+)\n> \n> --\n> 2.50.1 (Apple Git-155)\n>","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":["legolas.ozlabs.org;\n\tdkim=pass (1024-bit key;\n unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256\n header.s=mimecast20190719 header.b=aM5qRwUX;\n\tdkim-atps=neutral","legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)"],"Received":["from lists.gnu.org (lists1p.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fsC5f3YXKz1yGb\n\tfor ; Fri, 10 Apr 2026 07:01:08 +1000 (AEST)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from )\n\tid 1wAwU8-0003cT-Lw; Thu, 09 Apr 2026 17:00:20 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from )\n id 1wAwU6-0003bl-RK\n for qemu-devel@nongnu.org; Thu, 09 Apr 2026 17:00:18 -0400","from us-smtp-delivery-124.mimecast.com ([170.10.129.124])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from )\n id 1wAwU4-0003jJ-GY\n for qemu-devel@nongnu.org; Thu, 09 Apr 2026 17:00:18 -0400","from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com\n (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by\n relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,\n cipher=TLS_AES_256_GCM_SHA384) id us-mta-453-PGTYN7HeO5G6-jPpdStZvA-1; Thu,\n 09 Apr 2026 17:00:13 -0400","from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com\n (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4])\n (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest\n SHA256)\n (No client certificate requested)\n by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS\n id 79D5E1956080; Thu, 9 Apr 2026 21:00:11 +0000 (UTC)","from localhost (unknown [10.44.34.179])\n by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP\n id F41FB3000C16; Thu, 9 Apr 2026 21:00:09 +0000 (UTC)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1775768415;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:cc:mime-version:mime-version:content-type:content-type:\n in-reply-to:in-reply-to:references:references;\n bh=MTSN74Q0fLu2ja67fDRVvufeWhfWew7w8f7WnYKnbAY=;\n b=aM5qRwUXleFtGqYDBff9ys5fsotBvEpnaZwyiQFoBEe5TV+EMyUIUZe0mU6S5hM0+c+Hb7\n MOsjQuRpJLgL2kpnViimEDcWO61kW8AC1baR20njc8SITe9jJVEqVj38kqGTrjp2biGvS0\n 0i5SkehpFjQmJAFeIJY2QneAMAqy2fw=","X-MC-Unique":"PGTYN7HeO5G6-jPpdStZvA-1","X-Mimecast-MFC-AGG-ID":"PGTYN7HeO5G6-jPpdStZvA_1775768411","Date":"Thu, 9 Apr 2026 17:00:07 -0400","From":"Stefan Hajnoczi ","To":"mr-083 ","Cc":"qemu-devel@nongnu.org, qemu-block@nongnu.org, its@irrelevant.dk,\n kbusch@kernel.org, mr-083 ","Subject":"Re: [PATCH 0/2] NVMe namespace hotplug and drive reconnection support","Message-ID":"<20260409210007.GA461870@fedora>","References":"<20260409070114.11313-1-matthieu@min.io>","MIME-Version":"1.0","Content-Type":"multipart/signed; micalg=pgp-sha512;\n protocol=\"application/pgp-signature\"; boundary=\"rXDJNL5tS8FVxHtZ\"","Content-Disposition":"inline","In-Reply-To":"<20260409070114.11313-1-matthieu@min.io>","X-Scanned-By":"MIMEDefang 3.4.1 on 10.30.177.4","Received-SPF":"pass client-ip=170.10.129.124;\n envelope-from=stefanha@redhat.com;\n helo=us-smtp-delivery-124.mimecast.com","X-Spam_score_int":"7","X-Spam_score":"0.7","X-Spam_bar":"/","X-Spam_report":"(0.7 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.54,\n DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,\n RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001,\n RCVD_IN_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001,\n RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001,\n SPF_PASS=-0.001 autolearn=no autolearn_force=no","X-Spam_action":"no action","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development ","List-Unsubscribe":",\n ","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n ","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}},{"id":3675632,"web_url":"http://patchwork.ozlabs.org/comment/3675632/","msgid":"","list_archive_url":null,"date":"2026-04-10T00:49:01","subject":"Re: [PATCH 0/2] NVMe namespace hotplug and drive reconnection support","submitter":{"id":93098,"url":"http://patchwork.ozlabs.org/api/people/93098/","name":"Matthieu Rolla","email":"matthieu@minio.io"},"content":"Thanks for the review!\n\n> Is it possible to achieve this with device_del + device_add instead of\n> introducing a new monitor command?\n\nYes, device_del + device_add works. I tested it and the AEN properly\nnotifies the guest kernel which rescans and adds/removes the block\ndevice.\n\nHowever, when filesystems (XFS via DirectPV in our case) are mounted\non the namespace, the old block device number is not reused on re-add.\nThe kernel's IDA allocator only frees the ID when all references to\nthe namespace head are released (nvme_free_ns_head), but the stale\nXFS mount holds a reference indefinitely.\n\nWithout mounted filesystems, the ID is reused correctly (/dev/nvme0n1\nstays nvme0n1).\n\n> Is NVMe AEN insufficient to get the guest to recognize the Namespace\n> change?\n\nYou're right AEN is sufficient. I confirmed that the Linux NVMe\ndriver processes NVME_AER_NOTICE_NS_CHANGED and rescans automatically.\nThe SDN was unnecessary.\n\nI dropped Patch 2 (drive_insert) and sent v2 with just the\nnamespace hotplug support. The commit message now documents the\ncorrect device_del + device_add flow.\n\nHere is the link\nhttps://mail.gnu.org/archive/html/qemu-devel/2026-04/msg01507.html\n\nThanks\n\nOn Thu, Apr 9, 2026 at 11:00 PM Stefan Hajnoczi wrote:\n\n> On Thu, Apr 09, 2026 at 09:01:09AM +0200, mr-083 wrote:\n> > This series adds two features that together enable transparent NVMe disk\n> > hot-swap simulation in QEMU, matching the behavior of physical NVMe\n> > drives being pulled and reinserted in the same PCIe slot.\n> >\n> > Problem:\n> > Currently, hot-swapping an NVMe disk in QEMU requires removing the\n> > entire NVMe controller via device_del, which causes the Linux guest to\n> > assign a new controller number on re-add (e.g. nvme2 becomes nvme4).\n> > This breaks storage software that tracks drives by device name.\n>\n> Hi mr-083,\n> Neat, I was looking for something like this recently!\n>\n> > Solution:\n> > Patch 1 adds hotplug support for nvme-ns devices on the NvmeBus, with\n> > proper Asynchronous Event Notification (AEN) so the guest kernel detects\n> > namespace changes. This allows namespace-level hot-swap without removing\n> > the NVMe controller.\n> >\n> > Patch 2 adds a drive_insert HMP command that reconnects a host block\n> > device file to an existing guest device after drive_del. This is the\n> > counterpart to drive_del for non-removable devices where\n> > blockdev-change-medium cannot be used.\n> >\n> > The recommended hot-swap sequence is:\n> > 1. drive_del # disconnect backing store\n> > 2. drive_insert # reconnect backing store\n>\n> Is it possible to achieve this with device_del + device_add instead of\n> introducing a new monitor command?\n>\n> device_del nvme-ns2\n> blockdev-del nvme-ns2-blk (or drive_del)\n> ...\n> blockdev-add nvme-ns2-blk,... (or drive_add)\n> device_add nvme-ns,id=nvme-ns2,nsid=2,drive=nvme-ns2-blk\n>\n> > 3. pcie_aer_inject_error SDN # trigger controller reset\n>\n> Is NVMe AEN insufficient to get the guest to recognize the Namespace\n> change? I looked at the Linux NVMe driver code recently and got the\n> impression it would process changes to the Namespace list upon receiving\n> the NVMe AEN.\n>\n> > After this sequence, the guest sees the same controller and namespace\n> > names (e.g. /dev/nvme2n1 remains /dev/nvme2n1), and the NVMe driver\n> > recovers transparently via the standard AER recovery path.\n> >\n> > Tested with:\n> > - Linux 6.1 guest on QEMU aarch64 with HVF (macOS)\n> > - NVMe subsystem model with multipath disabled\n> > - DirectPV and MinIO AIStor storage stack\n> >\n> > mr-083 (2):\n> > hw/nvme: add namespace hotplug support\n> > block/monitor: add drive_insert HMP command\n> >\n> > block/monitor/block-hmp-cmds.c | 59 +++++++++++++++++++++++\n> > hmp-commands.hx | 18 +++++++\n> > hw/nvme/ctrl.c | 85 ++++++++++++++++++++++++++++++++++\n> > hw/nvme/ns.c | 1 +\n> > hw/nvme/subsys.c | 2 +\n> > include/block/block-hmp-cmds.h | 1 +\n> > 6 files changed, 166 insertions(+)\n> >\n> > --\n> > 2.50.1 (Apple Git-155)\n> >\n>","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":["legolas.ozlabs.org;\n\tdkim=pass (2048-bit key;\n secure) header.d=minio.io header.i=@minio.io header.a=rsa-sha256\n header.s=minio header.b=bq5vomI1;\n\tdkim-atps=neutral","legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)"],"Received":["from lists.gnu.org (lists1p.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fsMXZ2sHnz1yCv\n\tfor ; Fri, 10 Apr 2026 13:21:32 +1000 (AEST)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from )\n\tid 1wB2QN-00029j-MC; Thu, 09 Apr 2026 23:20:51 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from ) id 1wB03U-0006zQ-NU\n for qemu-devel@nongnu.org; Thu, 09 Apr 2026 20:49:06 -0400","from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)\n (Exim 4.90_1) (envelope-from ) id 1wB03S-0003w2-QM\n for qemu-devel@nongnu.org; Thu, 09 Apr 2026 20:49:04 -0400","by mail-yw1-x112d.google.com with SMTP id\n 00721157ae682-79d991c7b6aso15673317b3.2\n for ; Thu, 09 Apr 2026 17:49:02 -0700 (PDT)"],"ARC-Seal":"i=1; a=rsa-sha256; t=1775782141; cv=none;\n d=google.com; s=arc-20240605;\n b=SH1aeUTpn4T2JREYRUBrnEx0VHnIK4SWN6CE8Xo5LXYCcOqdGD9URZ5GlO2wmLwbPd\n Kom0uFTVm7KfVl5mYq4VTgBVGqhTmNCH6mfkqOdmXo6H/G0F+Qb9Dd2sWia7OhwqNX6R\n anBKVY4grdLXvtMTQtvNFyWutWxRwnr9cFVwW3paFdkpGKZO2h46qmNmzYr8HVvedHu/\n uv8VuIwrOoNSzg1FwaUi28EIxuSYdKqiJAfbJusaaOiOgRzq/PquTnktmzjY3Kb3lxsu\n hN7GlMcawkpas+Q3tnGNt8Aie80iPcTCT2V7tru5BgEszmURQ1j2H4p+5L478dUvhh6/\n 5adQ==","ARC-Message-Signature":"i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;\n s=arc-20240605;\n h=cc:to:subject:message-id:date:from:in-reply-to:references\n :mime-version:dkim-signature;\n bh=EOgZzkmBjXoou+oVC7LsJDXZfXvkE72jYXZxbhh+XBo=;\n fh=9APC4TOqqeyK4f+hBMC/WhXBwI4zhfL25tS7yb/7n7s=;\n b=Dqkgg6+it348Ns9lu8el32doB4oST98ycSweTXpCQRw0d+8a28JwZuyhxzXuBsX5Qf\n 9J8oLbSrjIUp/YaOAsEIW6fw9NZ4DmUn6rZPqNzL5tj/RHoNcUkgbzv57PUoGW3b+iOF\n U+j280BZ08Rm+zSEBz49Mo6i0n5KcoPvVzzbuvtm53Qm/lXC5o3U0DpeuOwM6RVIxaH+\n gxyVkRyvRzq0qN93cx3EswdCYTIeYvfi+ad1cO3zUXVN9OAJ3FL9kFtnVH+94ycjLOXn\n AT3yLg0qw0fik7aEYVfBvxZbOkAPmrUuQJYhg84zWr3qh3wa9epmNLjbJ+qA7tctPiSU\n AeoA==; darn=nongnu.org","ARC-Authentication-Results":"i=1; mx.google.com; arc=none","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=minio.io; s=minio; t=1775782141; x=1776386941; darn=nongnu.org;\n h=cc:to:subject:message-id:date:from:in-reply-to:references\n :mime-version:from:to:cc:subject:date:message-id:reply-to;\n bh=EOgZzkmBjXoou+oVC7LsJDXZfXvkE72jYXZxbhh+XBo=;\n b=bq5vomI1dzCdZxbMH+oRZYkwpBn8FXn+U9z+vyxzdw3Be+ZpKNXz7GcVk3RvdSGxHu\n RQ7AmFDR03pQnYbyhQITlYmb6xUIBZN6rqo5ESclNUxEfC46jQQp5tqt2vht0aFSgDCj\n JTh3YqP1MUViMAYOAWj9HIVKoV5uedkecsLEN0sdXgS5yT200wnJ5vyCwgBBJAj7J+DB\n 3H4aA5YfmOsvPnC5h1Sg5ZOw+Fxoaq/gC4AGWW/OcJ3wMRnVHfeRzgGfIA0pUPLOAKFK\n M+8qg12Uu3kkMoEzx+HdfegBb+VgbAvpOG7TPXkdLxULtghm76KAhAHbsc+qW1gNxiEe\n O+Xw==","X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=1e100.net; s=20251104; t=1775782141; x=1776386941;\n h=cc:to:subject:message-id:date:from:in-reply-to:references\n :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date\n :message-id:reply-to;\n bh=EOgZzkmBjXoou+oVC7LsJDXZfXvkE72jYXZxbhh+XBo=;\n b=TzyDuQHUdx8H9wEr6lI6mw8JqTtvcj5aE7XhQ49myIxYJUa0gsxn27oBA5BgxYEdfk\n 97gtJm/rHhVPOdtydwD35L88BdQt6gZSGbVbMUv3oee+GoHO7OtR31mDakvBJt9G2nJW\n 2hLjihhSLqrZN+6o70ZAGUdnC9veWrTgCJ0Sf04PH3k/4F51vUAmlpIsbMBQ6OSV6DFQ\n VJOG774WcL/tzVRFVR/Gh/qgpHLXb9ROrovv7/W/OMzX8251kv57cojt69E+uGj+QImj\n sa4/gpiS9I9W+Qau+D6UX0AFTISWFMsRmAxrwj0i7XvKMMNF/xzvxbqkpNwvXRj24j+Q\n +nDg==","X-Gm-Message-State":"AOJu0YyD0u7FRCHWGkJZc5KOSY1vtgjxtrdm0nyJaREETIQHipgtN3+U\n RHaR6dh6+WK+wemxBha5nBFxqZfKXlsLzCHhi0NHmSsPLG2/RpQYf72GoTNgUfm8lI35piDgORK\n B5FtL/VwDWwa4AJIChtaAmOgRVlPQQv1jt8VBno8ZEg==","X-Gm-Gg":"AeBDiesIY/JwOLa6rsYzFC8nvPjRB2omq9/mL7X0uAE+nfVVJqwhP8woZ/H1x8DeRym\n ba+tXmnCmbJJPbderSKlW6hau7d4F3mZGPTG8mccTo+vxKdOmgRY7Oeid6OFnMu1lELkMKH347v\n Q0Q73o1QWFHBhxHMzc5YdCRu2JLKm+WV9S+cJFdN/aOxjJlw6rYbFH7aJUK4nKMjHi2mgYRVu7D\n 7LaG8vE7yL+ayc93C2L2WOUcfNKcBdGwkRlTH0a+In7qa8PP2qBWUJDbXwq7mXZuEeJBt9mRhVL\n HJQAAPUwWd8gRizO/SGmT7vdd+zYTqBgw36JZkW5+3/qbJSvzbrdHWcRAwePBwjFidtbOjh0Cw=\n =","X-Received":"by 2002:a05:690c:d8e:b0:7a0:afb5:687d with SMTP id\n 00721157ae682-7af71962847mr14309907b3.39.1775782141035; Thu, 09 Apr 2026\n 17:49:01 -0700 (PDT)","MIME-Version":"1.0","References":"<20260409070114.11313-1-matthieu@min.io>\n <20260409210007.GA461870@fedora>","In-Reply-To":"<20260409210007.GA461870@fedora>","From":"Matthieu Rolla ","Date":"Fri, 10 Apr 2026 02:49:01 +0200","X-Gm-Features":"AQROBzDxmRHIc0fPSuXYC40YPnP0UyiTH5dEWqc1eruf_VMZ5m2sgSdzoKZR69Y","Message-ID":"\n ","Subject":"Re: [PATCH 0/2] NVMe namespace hotplug and drive reconnection support","To":"Stefan Hajnoczi ","Cc":"qemu-devel@nongnu.org, qemu-block@nongnu.org, its@irrelevant.dk,\n kbusch@kernel.org, mr-083 ","Content-Type":"multipart/alternative; boundary=\"000000000000b7192d064f107f0e\"","Received-SPF":"pass client-ip=2607:f8b0:4864:20::112d;\n envelope-from=matthieu@minio.io; helo=mail-yw1-x112d.google.com","X-Spam_score_int":"-20","X-Spam_score":"-2.1","X-Spam_bar":"--","X-Spam_report":"(-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,\n DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,\n RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,\n SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no","X-Spam_action":"no action","X-Mailman-Approved-At":"Thu, 09 Apr 2026 23:20:50 -0400","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development ","List-Unsubscribe":",\n ","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n ","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}}]