From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Qing Wang" <qinwang@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Hannes Reinecke" <hare@suse.de>,
pkrempa@redhat.com, "Eduardo Habkost" <eduardo@habkost.net>,
"Alberto Faria" <afaria@redhat.com>,
berrange@redhat.com
Subject: Re: [PATCH v3 0/5] scsi: persistent reservation live migration
Date: Wed, 4 Feb 2026 08:16:02 -0500 [thread overview]
Message-ID: <20260204131602.GB591743@fedora> (raw)
In-Reply-To: <20260129212035.219676-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]
On Thu, Jan 29, 2026 at 04:20:30PM -0500, Stefan Hajnoczi wrote:
> v3:
> - Use warn_report_err() instead of suppressing errors [Daniel Berrangé]
> - Wrap lines exceeding 80 characters
CCing Daniel Berrangé (sorry, I forgot!)
>
> v2:
> - Add user documentation [Paolo]
> - Send PREEMPT on the source if migration fails. This rollback operation
> ensures the source regains access to the LUN even if migration fails after
> the destination issues its own PREEMPT.
>
> Live migration does not work for SCSI Persistent Reservations acquired on
> scsi-block devices. This patch series migrates the reservation key and
> reservation type so that the destination QEMU can take over the persistent
> reservation with the PREEMPT service action upon live migration.
>
> The approach involves snooping PERSISTENT RESERVE OUT replies and tracking the
> scsi-block device's current reservation key and reservation type. In most cases
> this involves no additional SCSI commands. This approach isn't perfect: if
> another machine modifies the reservation on the physical LUN, then QEMU's state
> becomes stale. Persistent reservations are inherently cooperative, so this is
> acceptable as long as real applications don't run into problems.
>
> I am also working on a test suite called pr-tests that runs sg_persist(8)
> commands across multiple machines in order to exercise various scenarios:
> https://gitlab.com/stefanha/pr-tests
>
> Stefan Hajnoczi (5):
> scsi: generalize scsi_SG_IO_FROM_DEV() to scsi_SG_IO()
> scsi: add error reporting to scsi_SG_IO()
> scsi: track SCSI reservation state for live migration
> scsi: save/load SCSI reservation state
> docs: add SCSI migrate-pr documentation
>
> docs/system/device-emulation.rst | 1 +
> docs/system/devices/scsi/index.rst | 10 +
> docs/system/devices/scsi/migrate-pr.rst | 54 +++++
> include/hw/scsi/scsi.h | 15 +-
> include/scsi/constants.h | 21 ++
> hw/core/machine.c | 4 +-
> hw/scsi/scsi-bus.c | 3 +
> hw/scsi/scsi-disk.c | 90 +++++++-
> hw/scsi/scsi-generic.c | 291 +++++++++++++++++++++++-
> hw/scsi/trace-events | 2 +
> 10 files changed, 476 insertions(+), 15 deletions(-)
> create mode 100644 docs/system/devices/scsi/index.rst
> create mode 100644 docs/system/devices/scsi/migrate-pr.rst
>
> --
> 2.52.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-02-04 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 21:20 [PATCH v3 0/5] scsi: persistent reservation live migration Stefan Hajnoczi
2026-01-29 21:20 ` [PATCH v3 1/5] scsi: generalize scsi_SG_IO_FROM_DEV() to scsi_SG_IO() Stefan Hajnoczi
2026-01-29 21:20 ` [PATCH v3 2/5] scsi: add error reporting " Stefan Hajnoczi
2026-01-29 21:20 ` [PATCH v3 3/5] scsi: track SCSI reservation state for live migration Stefan Hajnoczi
2026-01-29 21:20 ` [PATCH v3 4/5] scsi: save/load SCSI reservation state Stefan Hajnoczi
2026-01-29 21:20 ` [PATCH v3 5/5] docs: add SCSI migrate-pr documentation Stefan Hajnoczi
2026-02-04 13:16 ` Stefan Hajnoczi [this message]
2026-02-07 13:42 ` [PATCH v3 0/5] scsi: persistent reservation live migration Paolo Bonzini
2026-02-07 13:42 ` Paolo Bonzini
2026-02-09 14:32 ` Stefan Hajnoczi
2026-02-10 13:12 ` Kevin Wolf
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=20260204131602.GB591743@fedora \
--to=stefanha@redhat.com \
--cc=afaria@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=fam@euphon.net \
--cc=hare@suse.de \
--cc=kwolf@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qinwang@redhat.com \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@intel.com \
/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.