Search results

Sorry for the late reply. No, I don't have pve-firewall enabled.

I also just tried running kvm on the command line and everything works. So it might just be Proxmox timing out too early. Is there anyway to adjust Proxmox's start timeout?

No, kvm wasn't running. Here's the output of ulimit -a: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 2063315 max locked memory...

Said VM does start with 32, 64, 96 GB vRAM but not with 128GB or higher. Here is the output that I'm getting: TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc...

Great! e1000 doesn't seem to be affected so I'm using it instead of virtio-net at the moment.

What's the status on this? I'm also currently affected by this bug and am using e1000 NIC for now.