William Roche 06152b89db migration: prevent migration when VM has poisoned memory ... A memory page poisoned from the hypervisor level is no longer readable. The migration of a VM will crash Qemu when it tries to read the memory address space and stumbles on the poisoned page with a similar stack trace: Program terminated with signal SIGBUS, Bus error. #0 _mm256_loadu_si256 #1 buffer_zero_avx2 #2 select_accel_fn #3 buffer_is_zero #4 save_zero_page #5 ram_save_target_page_legacy #6 ram_save_host_page #7 ram_find_and_save_block #8 ram_save_iterate #9 qemu_savevm_state_iterate #10 migration_iteration_run #11 migration_thread #12 qemu_thread_start To avoid this VM crash during the migration, prevent the migration when a known hardware poison exists on the VM. Signed-off-by: William Roche <william.roche@oracle.com> Link: https://lore.kernel.org/r/20240130190640.139364-2-william.roche@oracle.com Signed-off-by: Peter Xu <peterx@redhat.com>		2024-02-05 14:41:58 +08:00
..
kvm-accel-ops.c	accel: Do not set CPUState::can_do_io in non-TCG accels	2024-01-19 12:28:59 +01:00
kvm-all.c	migration: prevent migration when VM has poisoned memory	2024-02-05 14:41:58 +08:00
kvm-cpus.h
meson.build
trace-events
trace.h