aboutgitcodebugslistschat
path: root/contrib/qemu
diff options
context:
space:
mode:
authorStefano Brivio <sbrivio@redhat.com>2025-03-07 23:27:03 +0100
committerStefano Brivio <sbrivio@redhat.com>2025-03-12 21:34:36 +0100
commit04701702471ececee362669cc6b49ed9e20a1b6d (patch)
tree89690dbaa3eb94c0fc8cb6ff973dacc242f825c0 /contrib/qemu
parent2b58b22845a76baf24141155eb4d4a882f509e97 (diff)
downloadpasst-04701702471ececee362669cc6b49ed9e20a1b6d.tar
passt-04701702471ececee362669cc6b49ed9e20a1b6d.tar.gz
passt-04701702471ececee362669cc6b49ed9e20a1b6d.tar.bz2
passt-04701702471ececee362669cc6b49ed9e20a1b6d.tar.lz
passt-04701702471ececee362669cc6b49ed9e20a1b6d.tar.xz
passt-04701702471ececee362669cc6b49ed9e20a1b6d.tar.zst
passt-04701702471ececee362669cc6b49ed9e20a1b6d.zip
passt-repair: Add directory watch
It might not be feasible for users to start passt-repair after passt is started, on a migration target, but before the migration process starts. For instance, with libvirt, the guest domain (and, hence, passt) is started on the target as part of the migration process. At least for the moment being, there's no hook a libvirt user (including KubeVirt) can use to start passt-repair before the migration starts. Add a directory watch using inotify: if PATH is a directory, instead of connecting to it, we'll watch for a .repair socket file to appear in it, and then attempt to connect to that socket. Signed-off-by: Stefano Brivio <sbrivio@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'contrib/qemu')
0 files changed, 0 insertions, 0 deletions