Ctrl-Alt-Del in VM Restarting PVE

[LongDono]

TLDR: Ctrl-Alt-Del restarting PVE

I have a Windows 11 VM with passthrough GPU, onboard audio, USB mouse and USB keyboard. Lately I've noticed PVE shutting down all of my VMs and restarting when I try to use the Windows VM.

I've realized that, if the monitor is not displaying a signal after moving the mouse, I've been pressing Ctrl-Alt-Del to let Windows know I want to login.

Debian (likely) is seeing this keystroke sequence and acting upon it directly, where I would have expected the USB mouse and keyboard to only be assigned to the VM:
systemd[1]: Received SIGINT.

Also of significance, possibly, is that my monitor has a KVM, and attaches/detaches the keyboard and mouse depending on the input being used. So the scenario is likely my changing the input back to the PVE passed through GPU/system, and then pressing Ctrl-Alt-Del... expecting that to be passed through to the VM.

How can I prevent PVE from responding to Ctrl-Alt-Del? The keyboard and mouse should only ever be used with the Windows VM but it looks like the core Debian OS is seeing that keystroke combination and restarting the system as if it's a regular single OS Linux installation where that might not be quite as much of a bad thing.

Thanks,
...Donovan

 

[fabian]

it sounds like your pass through is not configured properly, else the PVE host wouldn't "see" the key presses at all.. how are you passing through the keyboard to the windows VM?

 

[LongDono]

it sounds like your pass through is not configured properly, else the PVE host wouldn't "see" the key presses at all.. how are you passing through the keyboard to the windows VM?

I just noticed that Windows 11 had suspended itself (it's a wipe/reinstall and so suspend wasn't disabled), so this is scenario:

Windows 11 VM is suspended, I'm trying to wake it up with the keyboard, and the Ctrl-Alt-Del is passing through to Proxmox as the the VM isn't awake to receive events.

Disabling Windows suspend may be necessary, and will probably fix this issue as well, though it could be nice not to have Windows eating CPU cycles.

For the Windows VM, I am passing through the USB port:
USB Device > Use USB Port > Freestyle Edge RGB Keyboard (5-3.1)

Thanks,
...Donovan

 

[fabian]

suspended or hibernated? if the latter, than the VM is not running at all, and thus pass through is also not active at that point and the behaviour is to be expected.

 

[LongDono]

Suspended. PVE VM hover shows status: Suspended, and offers Resume action for the VM.
In Windows 11, Sleep after is 15 minutes and Hibernate after set to Never.

 

[fabian]

could you also post the VM config in question and pveversion -v output?

 

[LongDono]

Absolutely, thanks.

agent: 1
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
balloon: 0
bios: ovmf
boot: order=scsi0;net0;ide2
cores: 4
cpu: host,hidden=1,flags=+pcid
cpuunits: 1024
efidisk0: local-zfs:vm-102-disk-0,size=1M
hostpci0: 0000:10:00,pcie=1,x-vga=1
hostpci1: 0000:12:00.4,pcie=1
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.1
memory: 6144
name: Leviathan
net0: virtio=72:E7:45:59:E4:2B,bridge=vmbr0,firewall=1
numa: 1
onboot: 0
ostype: win10
parent: BeforeGPU
scsi0: local-zfs:vm-102-disk-1,discard=on,size=550G
scsihw: virtio-scsi-single
smbios1: uuid=5a1bf664-bbf1-4496-b90e-a1a97ba86a67
sockets: 1
tablet: 0
tpmstate0: local-zfs:vm-102-disk-2,size=4M,version=v2.0
usb0: host=5-3.1
usb1: host=5-3.3.1
usb2: host=4-3.1,usb3=1
usb3: host=5-4
vga: none
vmgenid: 0529a0a4-bbed-4195-bf6b-63e520cd416f

[BeforeGPU]
#Before GPU Driver Reinstall
agent: 1
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
balloon: 0
bios: ovmf
boot: order=scsi0;net0;ide2
cores: 4
cpu: host,hidden=1,flags=+pcid
cpuunits: 1024
efidisk0: local-zfs:vm-102-disk-0,size=1M
hostpci0: 0000:10:00,pcie=1,x-vga=1
hostpci1: 0000:12:00.4,pcie=1
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.1
memory: 6144
name: Leviathan
net0: virtio=72:E7:45:59:E4:2B,bridge=vmbr0,firewall=1
numa: 1
onboot: 0
ostype: win10
parent: win11prewipe
runningcpu: host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off
runningmachine: pc-q35-7.1+pve0
scsi0: local-zfs:vm-102-disk-1,discard=on,size=550G
scsihw: virtio-scsi-single
smbios1: uuid=5a1bf664-bbf1-4496-b90e-a1a97ba86a67
snaptime: 1679507215
sockets: 1
tablet: 0
tpmstate0: local-zfs:vm-102-disk-2,size=4M,version=v2.0
usb0: host=5-3.1
usb1: host=5-3.3.1
usb2: host=4-3.1,usb3=1
usb3: host=5-4
vga: none
vmgenid: 0529a0a4-bbed-4195-bf6b-63e520cd416f
vmstate: local-zfs:vm-102-state-BeforeGPU

[win11prewipe]
#Windows 11 before wipe
agent: 1
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
balloon: 0
bios: ovmf
boot: order=scsi0;net0
cores: 4
cpu: host,hidden=1,flags=+pcid
cpuunits: 1024
efidisk0: local-zfs:vm-102-disk-0,size=1M
hostpci0: 0000:10:00,pcie=1,x-vga=1
hostpci1: 0000:12:00.4,pcie=1
machine: pc-q35-7.1
memory: 6144
name: Turanga
net0: virtio=72:E7:45:59:E4:2B,bridge=vmbr0,firewall=1
numa: 1
onboot: 0
ostype: win10
scsi0: local-zfs:vm-102-disk-1,discard=on,size=550G
scsihw: virtio-scsi-single
smbios1: uuid=5a1bf664-bbf1-4496-b90e-a1a97ba86a67
snaptime: 1679433688
sockets: 1
tablet: 0
tpmstate0: local-zfs:vm-102-disk-2,size=4M,version=v2.0
usb0: host=5-3.1
usb1: host=5-3.3.1
usb2: host=4-3.1,usb3=1
usb3: host=5-4
vga: none
vmgenid: 0529a0a4-bbed-4195-bf6b-63e520cd416f

proxmox-ve: 7.3-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-8
pve-kernel-5.15: 7.3-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-6
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-5-pve: 5.13.19-13

ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-6
libpve-storage-perl: 7.3-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.2-7
pve-firmware: 3.6-4
pve-ha-manager: 3.5.1
pve-i18n: 2.8-3
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

 

[dcsapak]

hi,

could you post the journal from before the vm goes into sleep/suspends to after you press the buttons?
my guess is that when the vm pauses, qemu will release the usb devices to the host and only after you resume the vm will they be attached again