I observe a strange problem, starting from 2026-02-13, when I rebooted my PVE host:
Since then, an external machine cannot be woken up from one of my VMs (Ubuntu 24.04 LTS) with the wakeonlan utility. This sends brodcasts over port 9 containing the MAC of the machine to wake up. I started that machine by hand and it does not get the WOL packets:
shows no output when I call this on my Ubuntu VM:
(the MAC of the target).
This worked fine before. Disabling the firewall on the VM does not change anything, either.
However, when I do the same from the PVE host, it works right out of the box.
There is a VLAN-aware bridge vmbr0, where both the PVE host and VM are connected as VLAN 10 tagged.
Even more strange: When I listen to the interface of the PVE Host, I can see the WOL packets from the Ubuntu VM.
There have been updates for both the kernel and pve-kernel-qemu before that which became active by the reboot:
Most notably, kernel 6.17.4-2 -> 6.17.9-1 and pve-qemu-kvm 10.1.2-5 -> 10.1.2-6. I rolled back both and rebooted, but to no avail. There also was qemu-server:amd64 (9.1.3, 9.1.4), but I do not think that could be the culprit. I do not believe that the VM - whatever changed there - is to blame.
Has anyone noticed this, too and knows what goes wrong here?
Since then, an external machine cannot be woken up from one of my VMs (Ubuntu 24.04 LTS) with the wakeonlan utility. This sends brodcasts over port 9 containing the MAC of the machine to wake up. I started that machine by hand and it does not get the WOL packets:
Code:
tcpdump -i eth0 -nn -s 1500 -A 'port9' -v
Code:
wakeonlan xx:xx:xx:xx:xx:xxThis worked fine before. Disabling the firewall on the VM does not change anything, either.
However, when I do the same from the PVE host, it works right out of the box.
There is a VLAN-aware bridge vmbr0, where both the PVE host and VM are connected as VLAN 10 tagged.
Even more strange: When I listen to the interface of the PVE Host, I can see the WOL packets from the Ubuntu VM.
There have been updates for both the kernel and pve-kernel-qemu before that which became active by the reboot:
Code:
Start-Date: 2026-02-05 18:21:26
Commandline: apt upgrade proxmox-headers-6.17/stable proxmox-kernel-6.17/stable zfs-initramfs/stable zfs-zed/stable zfsutils-linux/stable ifupdown2/stable libnvpair3linux/stable libuutil3linux/stable
Install: libzfs7linux:amd64 (2.4.0-pve1, automatic), proxmox-kernel-6.17.9-1-pve-signed:amd64 (6.17.9-1, automatic), libzpool7linux:amd64 (2.4.0-pve1, automatic), proxmox-headers-6.17.9-1-pve:amd64 (6.17.9-1, automatic)
Upgrade: proxmox-headers-6.17:amd64 (6.17.4-2, 6.17.9-1), zfs-zed:amd64 (2.3.4-pve1, 2.4.0-pve1), zfs-initramfs:amd64 (2.3.4-pve1, 2.4.0-pve1), libnvpair3linux:amd64 (2.3.4-pve1, 2.4.0-pve1), libuutil3linux:amd64 (2.3.4-pve1, 2.4.0-pve1), ifupdown2:amd64 (3.3.0-1+pmx11, 3.3.0-1+pmx12), proxmox-kernel-6.17:amd64 (6.17.4-2, 6.17.9-1), pve-container:amd64 (6.0.18, 6.1.0), zfsutils-linux:amd64 (2.3.4-pve1, 2.4.0-pve1)
Remove: libzfs6linux:amd64 (2.3.4-pve1)
End-Date: 2026-02-05 18:22:11
Start-Date: 2026-02-05 18:28:06
Commandline: apt install pve-container=6.0.18
Downgrade: pve-container:amd64 (6.1.0, 6.0.18)
End-Date: 2026-02-05 18:28:13
Start-Date: 2026-02-09 20:05:03
Upgrade: chromium-sandbox:amd64 (144.0.7559.109-1~deb13u1, 144.0.7559.109-2~deb13u1), pve-qemu-kvm:amd64 (10.1.2-5, 10.1.2-6), linux-cpupower:amd64 (6.12.63-1, 6.12.69-1), chromium:amd64 (144.0.7559.109-1~deb13u1, 144.0.7559.109-2~deb13u1), pve-container:amd64 (6.0.18, 6.1.1), chromium-common:amd64 (144.0.7559.109-1~deb13u1, 144.0.7559.109-2~deb13u1), usbmuxd:amd64 (1.1.1-6, 1.1.1-6+deb13u1), libcpupower1:amd64 (6.12.63-1, 6.12.69-1), linux-libc-dev:amd64 (6.12.63-1, 6.12.69-1)
Remove: proxmox-kernel-6.17.4-1-pve-signed:amd64 (6.17.4-1), libzpool6linux:amd64 (2.3.4-pve1), proxmox-headers-6.17.4-2-pve:amd64 (6.17.4-2)
End-Date: 2026-02-09 20:05:21
Start-Date: 2026-02-12 22:38:20
Commandline: apt -y purge libzfs6linux:amd64 proxmox-kernel-6.14.11-4-pve-signed proxmox-kernel-6.17.2-2-pve proxmox-kernel-6.17.4-1-pve proxmox-kernel-6.17.4-1-pve-signed proxmox-rrd-migration-tool pulseaudio
Purge: pulseaudio:amd64 (), proxmox-kernel-6.17.4-1-pve-signed:amd64 (), proxmox-kernel-6.14.11-4-pve-signed:amd64 (), proxmox-rrd-migration-tool:amd64 (), proxmox-kernel-6.17.2-2-pve:amd64 (), proxmox-kernel-6.17.4-1-pve:amd64 (), libzfs6linux:amd64 ()
End-Date: 2026-02-12 22:38:26
Start-Date: 2026-02-12 22:49:21
Upgrade: libpq5:amd64 (17.7-0+deb13u1, 17.8-0+deb13u1)
End-Date: 2026-02-12 22:49:21
Start-Date: 2026-02-12 23:03:57
End-Date: 2026-02-12 23:03:57
Start-Date: 2026-02-13 18:50:28
End-Date: 2026-02-13 18:50:28Most notably, kernel 6.17.4-2 -> 6.17.9-1 and pve-qemu-kvm 10.1.2-5 -> 10.1.2-6. I rolled back both and rebooted, but to no avail. There also was qemu-server:amd64 (9.1.3, 9.1.4), but I do not think that could be the culprit. I do not believe that the VM - whatever changed there - is to blame.
Has anyone noticed this, too and knows what goes wrong here?
Last edited:
