All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: svt-core@virtuozzo.com
Cc: andrey.drobyshev@virtuozzo.com, den@openvz.org
Subject: [PATCH hci-dev v3 0/2] vfio/migration: don't touch the device on guest shutdown #VSTOR-153976
Date: Mon,  9 Nov 2026 17:43:44 +0200	[thread overview]
Message-ID: <20261109154346.153153-1-andrey.drobyshev@virtuozzo.com> (raw)

v2 -> v3:

 - new patch 1: stop the device when QEMU quits or migrates a VM that
   a guest shutdown left stopped. A VF closed while running, after the
   Linux guest driver unloaded, breaks the next VM that resumes on it;
 - the stop at the start of a save moved to patch 1 and now covers only
   the SHUTDOWN run state, so a suspended guest is left alone (Sashiko);
 - the guest shutdown check is one helper, used by both VM state
   handlers.

v2: http://lore.virtuozzo.com/qemu/20261108205050.37277-1-andrey.drobyshev@virtuozzo.com/

Andrey Drobyshev (2):
  vfio/migration: stop a device left running after a guest shutdown
    #VSTOR-153976
  vfio/migration: don't touch the device on guest shutdown #VSTOR-153976

 hw/vfio/migration.c               | 67 +++++++++++++++++++++++++++++++
 hw/vfio/vfio-migration-internal.h |  1 +
 include/system/runstate.h         |  1 +
 system/runstate.c                 |  5 +++
 4 files changed, 74 insertions(+)


base-commit: 5d129c4dd43d131fbcdd411ad30be8a9a641895e
--
2.47.1


             reply	other threads:[~2026-11-09 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 15:43 Andrey Drobyshev [this message]
2026-11-09 15:43 ` [PATCH hci-dev v3 1/2]vfio/migration: stop a device left running after a " Andrey Drobyshev
2026-11-09 15:50   ` no-reply
2026-11-09 15:43 ` [PATCH hci-dev v3 2/2]vfio/migration: don't touch the device on " Andrey Drobyshev
2026-11-09 15:53   ` no-reply

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=20261109154346.153153-1-andrey.drobyshev@virtuozzo.com \
    --to=andrey.drobyshev@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=svt-core@virtuozzo.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.