Since criu 2.4 there is a support to skip unknown controllers
via command line options. So use this facility instead of
hardcoding names into CRIU.
Signed-off-by: Cyrill Gorcunov
---
scripts/vz-cpt.in | 21 +
1 file changed, 21 insertions(+)
diff --git a/scripts/vz-cpt.in b/
Igor, please take a look. And please note that this patches
require *new* CRIU, thus we need to update libvzctl spec
to require criu-2.4.0.1-1.vz7 and above.
https://jira.sw.ru/browse/PSBM-50551
Cyrill Gorcunov (2):
scripts: vz-rst-action -- Use env variable instead of pidfile value
scripts:
Since CRIU-2.4 the pidfile is written into file on lazy fasion.
So we have to use @CRTOOLS_INIT_PID variable instead.
https://jira.sw.ru/browse/PSBM-50551
Signed-off-by: Cyrill Gorcunov
---
scripts/vz-rst-action.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/
From: Paolo Bonzini
Commit 172b2386ed16 ("KVM: x86: fix missed hardware breakpoints",
2016-02-10) worked around a case where the debug registers are not loaded
correctly on preemption and on the first entry to KVM_RUN.
However, Xiao Guangrong pointed out that the root cause must be that
KVM_DEBU
From: Nadav Amit
DR0-DR3 are not cleared as they should during reset and when they are set from
userspace. It appears to be caused by c77fb5fe6f03 ("KVM: x86: Allow the guest
to run with dirty debug registers").
Force their reload on these situations.
Signed-off-by: Nadav Amit
Message-Id: <14
A couple of mainstream backports to fix debug register updates on vcpu
transitions to/from guest.
Supposed to fix, in particular, occasional misses of hardware
breakpoints (https://jira.sw.ru/browse/PSBM-50488).
Nadav Amit (1):
KVM: x86: DR0-DR3 are not clear on reset
Paolo Bonzini (1):
KVM:
