CRON jobs from shutdown VMs causing errors?

X

xokia

Member
Apr 8, 2023
95
8
8
So wondering what proxmox is doing here. VM101 is a windows-11 VM that I do not have set to start on reboot and do not have running. I.e. I only enable this VM when I want to use it otherwise I have it shut down. It looks as though when CRON jobs are run its expecting something back from VM101 and since its shutdown creating an error. What is proxmox doing here?


May 28 03:12:56 HOME-SERVER systemd[1]: Started 101.scope.
May 28 03:12:56 HOME-SERVER systemd-udevd[10272]: Using default interface naming scheme 'v247'.
May 28 03:12:56 HOME-SERVER systemd-udevd[10272]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 28 03:12:57 HOME-SERVER kernel: device tap101i0 entered promiscuous mode
May 28 03:12:57 HOME-SERVER kernel: vmbr0: port 3(tap101i0) entered blocking state
May 28 03:12:57 HOME-SERVER kernel: vmbr0: port 3(tap101i0) entered disabled state
May 28 03:12:57 HOME-SERVER kernel: vmbr0: port 3(tap101i0) entered blocking state
May 28 03:12:57 HOME-SERVER kernel: vmbr0: port 3(tap101i0) entered forwarding state
May 28 03:12:57 HOME-SERVER pvedaemon[1415]: <root@pam> end task UPID:HOME-SERVER:00002815:0003D12E:64732928:qmstart:101:root@pam: OK
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 2/KVM/10307 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 12/KVM/10317 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 1/KVM/10306 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 5/KVM/10310 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 26/KVM/10331 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 24/KVM/10329 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 27/KVM/10332 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 25/KVM/10330 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 4/KVM/10309 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:57 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 15/KVM/10320 took a split_lock trap at address: 0x7ed9d050
May 28 03:12:59 HOME-SERVER pvedaemon[10336]: starting vnc proxy UPID:HOME-SERVER:00002860:0003D242:6473292B:vncproxy:101:root@pam:
May 28 03:12:59 HOME-SERVER pvedaemon[1415]: <root@pam> starting task UPID:HOME-SERVER:00002860:0003D242:6473292B:vncproxy:101:root@pam:
May 28 03:13:00 HOME-SERVER pvedaemon[1413]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:13:19 HOME-SERVER pvedaemon[1415]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:13:38 HOME-SERVER pvedaemon[1414]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:13:57 HOME-SERVER pvedaemon[1415]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:14:16 HOME-SERVER pvedaemon[1414]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:14:35 HOME-SERVER pvedaemon[1415]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:14:54 HOME-SERVER pvedaemon[1414]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:15:04 HOME-SERVER kernel: split_lock_warn: 16 callbacks suppressed
May 28 03:15:04 HOME-SERVER kernel: x86/split lock detection: #AC: CPU 0/KVM/10305 took a split_lock trap at address: 0xfffff800360b248f
May 28 03:15:13 HOME-SERVER pvedaemon[1415]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
May 28 03:15:32 HOME-SERVER pvedaemon[1414]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
 
not sure what you mean with cron jobs (nothing in the given logs about that), the logs only show the vm is started, then it seems like the console is opened (and possible the webinterface)
the line
xokia said:
May 28 03:13:38 HOME-SERVER pvedaemon[1414]: VM 101 qmp command failed - VM 101 qmp command 'guest-ping' failed - got timeout
Click to expand...
means thtat you configred the guest agent in the config, but it isn't responding to the 'guest-ping' call which either means the agent is not installed or running
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom