diff options
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1903.toml')
| -rw-r--r-- | gitlab/issues/target_missing/host_missing/accel_missing/1903.toml | 49 |
1 files changed, 49 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1903.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1903.toml new file mode 100644 index 00000000..92646a6f --- /dev/null +++ b/gitlab/issues/target_missing/host_missing/accel_missing/1903.toml @@ -0,0 +1,49 @@ +id = 1903 +title = "qemu/kvm are instantly SIGKILLed by systemd on shutdown, without wait." +state = "closed" +created_at = "2023-09-22T22:47:50.126Z" +closed_at = "2023-09-28T10:05:49.626Z" +labels = [] +url = "https://gitlab.com/qemu-project/qemu/-/issues/1903" +host-os = "Linux, Arch" +host-arch = "x86" +qemu-version = "8.1.1 (arch package 8.1.1-1)" +guest-os = "not relevant i believe, but for the above, linux." +guest-arch = "x86" +description = """systemd assumes it cannot terminate qemu, and SIGKILLs it. Instantly.""" +reproduce = """1. Start qemu on a systemd managed host +2. Shutdown/Reboot""" +additional = """Nothing on qemu's own log, besides that it is starting a vnc server. + +```plaintext +# journalctl -b -1 +... +Sep 22 18:38:04 local kernel: kvm_amd: TSC scaling supported +Sep 22 18:38:04 local kernel: kvm_amd: Nested Virtualization enabled +Sep 22 18:38:04 local kernel: kvm_amd: Nested Paging enabled +Sep 22 18:38:04 local kernel: kvm_amd: Virtual VMLOAD VMSAVE supported +Sep 22 18:38:04 local kernel: kvm_amd: Virtual GIF supported +Sep 22 18:38:04 local kernel: kvm_amd: LBR virtualization supported +... +Sep 22 18:38:50 local systemd-logind[721]: The system will reboot now! +Sep 22 18:38:50 local systemd-logind[721]: System is rebooting. +Sep 22 18:38:50 local sddm-helper[850]: Signal received: SIGTERM +... +Sep 22 18:38:50 local systemd[1]: Stopping User Manager for UID 1000... +Sep 22 18:38:50 local systemd-logind[721]: Removed session 1. +Sep 22 18:38:50 local systemd[854]: Activating special unit Exit the Session... +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/> +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Killing process 1708 (qemu-system-x86) with signal SIGKILL. +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Killing process 1712 (kvm-nx-lpage-recovery-1708) with signal SIGKILL. +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/> +Sep 22 18:38:50 local systemd[854]: Stopped Konsole - Terminal. +... (some other applications terminanting normally ) +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Consumed 10.068s CPU time. +Sep 22 18:38:50 local systemd[854]: Removed slice User Background Tasks Slice. +Sep 22 18:38:50 local systemd[854]: background.slice: Consumed 2.960s CPU time. +... +``` + +I cannot explain why it sends SIGKILL to qemu/kvm... it is the same second as the shutdown started, their docs says there's a delay for that. + +Also, other processes owned by the user received a single SIGTERM after qemu was SIGKILLed. Some even take a couple seconds to exit and are not SIGKILLed.""" |