so, i had a fully working OMV VM and i restarted it and i saw this error. this was like 2 weeks ago. asked around and no one replied so i just wiped everything and started again. and it worked great for over a week. went in to restart my machine so the RAM cache would clear and further prove my system was ready to be moved to a remote location and now i cannot boot my VM again... same error as before.
![Screenshot 2024-06-02 131621.png Screenshot 2024-06-02 131621.png](https://forum.proxmox.com/data/attachments/68/68847-e688d90580a8f5c2125f49ffe9b956e2.jpg)
so far i've:
Jun 02 13:27:01 pve2 pvedaemon[1142]: <root@pam> starting task UPID pve2:00001570:0001D146:665CD595:qmstart:102:root@pam:
Jun 02 13:27:01 pve2 pvedaemon[5488]: start VM 102: UPID pve2:00001570:0001D146:665CD595:qmstart:102:root@pam:
Jun 02 13:27:01 pve2 systemd[1]: Started 102.scope.
Jun 02 13:27:02 pve2 kernel: tap102i0: entered promiscuous mode
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered blocking state
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwpr102p0: entered allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwpr102p0: entered promiscuous mode
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered blocking state
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered forwarding state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwln102i0: entered allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwln102i0: entered promiscuous mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered forwarding state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: tap102i0: entered allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered forwarding state
Jun 02 13:27:02 pve2 kernel: tap102i0: left allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwln102i0 (unregistering): left allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwln102i0 (unregistering): left promiscuous mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwpr102p0 (unregistering): left allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwpr102p0 (unregistering): left promiscuous mode
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered disabled state
Jun 02 13:27:02 pve2 pvedaemon[1142]: VM 102 qmp command failed - VM 102 not running
Jun 02 13:27:02 pve2 systemd[1]: 102.scope: Deactivated successfully.
Jun 02 13:27:02 pve2 systemd[1]: 102.scope: Consumed 1.496s CPU time.
Jun 02 13:27:02 pve2 pvedaemon[5488]: start failed: QEMU exited with code 1
Jun 02 13:27:02 pve2 pvedaemon[1142]: <root@pam> end task UPID pve2:00001570:0001D146:665CD595:qmstart:102:root@pam: start failed: QEMU exited with code 1
I could really use the help haha. thanks!
![Screenshot 2024-06-02 131621.png Screenshot 2024-06-02 131621.png](https://forum.proxmox.com/data/attachments/68/68847-e688d90580a8f5c2125f49ffe9b956e2.jpg)
so far i've:
- changed display to SPLICE(qxl) because i saw that on another forum post.
- restarted entire node again
Jun 02 13:27:01 pve2 pvedaemon[1142]: <root@pam> starting task UPID pve2:00001570:0001D146:665CD595:qmstart:102:root@pam:
Jun 02 13:27:01 pve2 pvedaemon[5488]: start VM 102: UPID pve2:00001570:0001D146:665CD595:qmstart:102:root@pam:
Jun 02 13:27:01 pve2 systemd[1]: Started 102.scope.
Jun 02 13:27:02 pve2 kernel: tap102i0: entered promiscuous mode
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered blocking state
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwpr102p0: entered allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwpr102p0: entered promiscuous mode
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered blocking state
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered forwarding state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwln102i0: entered allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwln102i0: entered promiscuous mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered forwarding state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: tap102i0: entered allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered forwarding state
Jun 02 13:27:02 pve2 kernel: tap102i0: left allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwln102i0 (unregistering): left allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwln102i0 (unregistering): left promiscuous mode
Jun 02 13:27:02 pve2 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Jun 02 13:27:02 pve2 kernel: fwpr102p0 (unregistering): left allmulticast mode
Jun 02 13:27:02 pve2 kernel: fwpr102p0 (unregistering): left promiscuous mode
Jun 02 13:27:02 pve2 kernel: vmbr0: port 2(fwpr102p0) entered disabled state
Jun 02 13:27:02 pve2 pvedaemon[1142]: VM 102 qmp command failed - VM 102 not running
Jun 02 13:27:02 pve2 systemd[1]: 102.scope: Deactivated successfully.
Jun 02 13:27:02 pve2 systemd[1]: 102.scope: Consumed 1.496s CPU time.
Jun 02 13:27:02 pve2 pvedaemon[5488]: start failed: QEMU exited with code 1
Jun 02 13:27:02 pve2 pvedaemon[1142]: <root@pam> end task UPID pve2:00001570:0001D146:665CD595:qmstart:102:root@pam: start failed: QEMU exited with code 1
I could really use the help haha. thanks!
Last edited: