[SOLVED] VMs not shutting down through GUI

[medicineman25]

Proxmox 7.1-7
AMD Epyc 7402
Gigabyte MZ72-HBO

Various Win10 Pro and Arch Linux VMs that are not responding to shutdown from the GUI. Arch Linux machines have qemu-geust-agent installed.

Syslog:

Jan 08 16:21:28 central pvedaemon[1516470]: <root@pam> end task UPID:central:003D8D90:0120D713:61D9B96A:vncproxy:100:root@pam: OK
Jan 08 16:21:28 central pvedaemon[4091218]: starting termproxy UPID:central:003E6D52:012114A6:61D9BA08:vncshell::root@pam:
Jan 08 16:21:28 central pvedaemon[3522838]: <root@pam> starting task UPID:central:003E6D52:012114A6:61D9BA08:vncshell::root@pam:
Jan 08 16:21:28 central pvedaemon[1516470]: <root@pam> successful auth for user 'root@pam'
Jan 08 16:21:28 central login[4091294]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Jan 08 16:21:28 central systemd[1]: Created slice User Slice of UID 0.
Jan 08 16:21:28 central systemd[1]: Starting User Runtime Directory /run/user/0...
Jan 08 16:21:28 central systemd-logind[3985]: New session 2049 of user root.
Jan 08 16:21:28 central systemd[1]: Finished User Runtime Directory /run/user/0.
Jan 08 16:21:28 central systemd[1]: Starting User Manager for UID 0...
Jan 08 16:21:28 central systemd[4091303]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Jan 08 16:21:28 central systemd[4091308]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Jan 08 16:21:28 central systemd[4091303]: Queued start job for default target Main User Target.
Jan 08 16:21:28 central systemd[4091303]: Created slice User Application Slice.
Jan 08 16:21:28 central systemd[4091303]: Reached target Paths.
Jan 08 16:21:28 central systemd[4091303]: Reached target Timers.
Jan 08 16:21:28 central systemd[4091303]: Listening on GnuPG network certificate management daemon.
Jan 08 16:21:28 central systemd[4091303]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 08 16:21:28 central systemd[4091303]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 08 16:21:28 central systemd[4091303]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 08 16:21:28 central systemd[4091303]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 08 16:21:28 central systemd[4091303]: Reached target Sockets.
Jan 08 16:21:28 central systemd[4091303]: Reached target Basic System.
Jan 08 16:21:28 central systemd[4091303]: Reached target Main User Target.
Jan 08 16:21:28 central systemd[4091303]: Startup finished in 282ms.
Jan 08 16:21:28 central systemd[1]: Started User Manager for UID 0.
Jan 08 16:21:29 central systemd[1]: Started Session 2049 of user root.
Jan 08 16:21:29 central login[4091446]: ROOT LOGIN  on '/dev/pts/10'
Jan 08 16:21:29 central systemd[1]: session-2049.scope: Succeeded.
Jan 08 16:21:29 central systemd-logind[3985]: Session 2049 logged out. Waiting for processes to exit.
Jan 08 16:21:29 central systemd-logind[3985]: Removed session 2049.
Jan 08 16:21:29 central pvedaemon[3522838]: <root@pam> end task UPID:central:003E6D52:012114A6:61D9BA08:vncshell::root@pam: OK
Jan 08 16:21:29 central kernel: kvm_msr_ignored_check: 4 callbacks suppressed
Jan 08 16:21:29 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:29 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:30 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:30 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:31 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:31 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:31 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:31 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:32 central pvescheduler[3812841]: INFO: Finished Backup of VM 850 (00:01:38)
Jan 08 16:21:32 central pvescheduler[3812841]: INFO: Starting Backup of VM 851 (lxc)
Jan 08 16:21:32 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:32 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:34 central kernel: kvm_msr_ignored_check: 4 callbacks suppressed
Jan 08 16:21:34 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:34 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:35 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:35 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:36 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:36 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:37 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:37 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0
Jan 08 16:21:37 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x400
Jan 08 16:21:37 central kernel: kvm [3008846]: ignored wrmsr: 0xc0011020 data 0x0

 

[Moayad]

Hi,

What happens if you try using CLI?

qm shutdown <VMID>

 

[medicineman25]

Hi,

What happens if you try using CLI?

qm shutdown <VMID>

Nothing. I have to manually shutdown from inside the VM or run:

qm stop <vmid>

 

[Moayad]

Hi,

are you sure that Qemu is up and running inside the VM?
You can check for the QEMU service using CLI e.g:

PowerShell:

Get-Service -Name QEMU-GA

CMD

sc query QEMU-GA

 

[medicineman25]

Hi,

are you sure that Qemu is up and running inside the VM?
You can check for the QEMU service using CLI e.g:

PowerShell:

Get-Service -Name QEMU-GA

CMD

sc query QEMU-GA

Oh god, does it need to be turned on... It definitely isn't on either VM. That doesn't seem to be mentioned anywhere relevant *sigh*... I need to find another career.

Enabled and started the service in my Linux VMs, now shuts down properly.

 

[medicineman25]

oop.. forgot to say thank you @Moayad. Very grateful for your assistance!

 

[Moayad]

Hi

Glad that you solved your issue.
I will go ahead and set your thread as [SOLVED] to help other people who have the same issue

Have a nice weekend