Troubleshooting

If Proxmox shows QEMU guest agent is not running, check the VM option on the Proxmox node and the agent service inside the guest. Run qm agent <vmid> ping on the node to verify that the two can communicate. Which message do you see? Message or symptom First check QEMU guest agent is not running On the Proxmox node, check the VM’s agent option and ping the agent . No guest agent configured or Requires guest agent installed Check the VM option and guest installation . A dependency job for qemu-guest-agent.service failed In the Linux VM, check the virtio-serial device and boot journal . Error opening channel … No such file or directory Compare the path in the log with the configured channel . Windows service is running, but ping fails Check the VM option and the VirtIO Serial driver . Quick fix From the Proxmox host: ...

Wake-on-LAN failing on Proxmox? There are two completely separate problems people mean by this: Waking the physical Proxmox host from a full shutdown — this is regular hardware WoL. It works, with a few Proxmox-specific gotchas. Waking a VM that is powered off — classic magic-packet WoL does not work here. A virtual NIC is not a physical card sitting in a low-power state. If you mixed solutions from both threads and nothing worked, that is why. Do them separately. ...

If an Intel I225-V interface on Proxmox VE 9 starts falling into a repeating NETDEV WATCHDOG / Reset adapter loop after moving to a 7.0.x Proxmox kernel, there is now at least one well-documented report showing exactly that pattern. The important caveat is scope: this is not yet a broadly confirmed Proxmox-wide bug affecting every I225-V or I226-V system. The strongest current evidence comes from one detailed Proxmox VE 9.2.5 report where the same I225-V hardware was stable on 6.17.13-21-pve and repeatedly failed on two tested 7.0 kernels. ...

A Proxmox VE node without a paid subscription can show a subscription notice in the web UI. If the enterprise repository is enabled without a valid key, apt update can also return an authorization error. These are related to subscription status, but they are not the same problem. The web notice is informational. An enterprise-repository error prevents that repository from supplying updates and should be corrected. The supported choices are to buy a subscription and use the enterprise repository, or configure the public no-subscription repository for a non-production lab. ...