[SOLVED] VMs Not Starting after Update / Reboot - QEMU exited with Code 1

iweinstein

New Member
Nov 27, 2022
6
1
3
Hi All,

I was trying to resolve a networking issue on my Proxmox server this AM (network speeds dropping after a few minutes of transfers using Truenas). Eventually, I gave up on the networking issue and simply rebooted the server. Since that reboot, none of my VMs will start.

In Task History, I see the following on the Status Tab:

stopped: start failed: QEMU exited with code 1

On the Output tab, I see the following:

failed to open /proc/sys/net/ipv6/conf/fwln111i0/disable_ipv6 for writing: No such file or directory
kvm: -netdev type=tap,id=net0,ifname=tap111i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: QEMU exited with code 1

I am running Proxmox version 7.2-3 on a Dell T630 Server.

Note - I'm definitely a Proxmox newbie, but I somehow managed to get Proxmox running and doing what I need it to do.

Any help or suggestions would be appreciated.

Thanks!

Ira
 
It looks like the problem is solved.

Earlier today, while trying to fix a networking issue, I changed MTU from default. Then, when I rebooted, I had the above QEMU error. Once I set the MTU back to default and rebooted, the VMs started up again.

Thanks anyway !!!
 
  • Like
Reactions: leesteken

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!

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!