Recent content by bat-zh

root@proxmox3:~# qm config 169 agent: 1 bios: ovmf boot: order=scsi0;ide2;net0 cores: 4 efidisk0: NVMe:vm-169-disk-0,efitype=4m,pre-enrolled-keys=1,size=528K ide2: none,media=cdrom memory: 8096 meta: creation-qemu=6.1.0,ctime=1649423345 name: GV-WHM net0...

I enabled the guest agent recently on a centos guest and now it's freezing everyday - seems to freeze during the backup PBS. We have to reset the server everyday. We summitted a ticket to cPanel and a tech there alerted us to this: https://gitlab.com/qemu-project/qemu/-/issues/520 I guess for...

Could be, but since we have never seen this issue on our 6.4 cluster and we've only seen this on our 7.1 cluster - Im not so sure.

Clearly this is a big issue affecting lots of users. Is there any official word from Proxmox on an upcoming fix or anything? I was hopeful that 7.2 would address this. I think we all desperately want to get this resolved. We had issues last night with 2 clients that resulted in of course early...

I have tested 2 additional VMs tonight while installing updates. 2K16 win std VMs. Updates install, reboot VMs (from inside the VM), watch the console and stuck at the boot screen with the spinning dots. Stop/Start VM comes back up, check updates and they have installed. Reboot VM (from...

Here are 2 VM confs. Both were imports from Hyper-V. Both have sporadic issues with reboot fail: VM 1 - agent: 1 balloon: 0 bios: ovmf boot: order=scsi0;sata2 cores: 8 cpu: host efidisk0: NVMe:vm-106-disk-1,size=128K machine: pc-i440fx-6.0 memory: 16384 name: VM-WEB05 net0...

We have tested a few things. This seems to be an issue with Hyper-V VMs imported to ProxMox on 7.1-4. We have been importing Gen 2 Hyper-V VMs into ProxMox and also importing from another KVM based hyper-visor using qm importdisk. The KVM based hyper-visor imports work fine, the Hyper-v imports...

Also to add. We are running one cluster with VE 6.4-13 - that cluster is not showing this issue at all with windows, Linux, native and imported VMs. The cluster that is showing this issue is running VE 7.1-4.

We have been experiencing this too. It's seems completely random. Some windows VMs will do it pretty consistently, some are random like every 2 weeks we have to stop/start then it's fine. Some never have the issue. Most of the ones that seem to have the issue were imported (qm import) from hyper-v.

Can you please elaborate on this. We are running into this very same issue only with VMs imported from Hyper-V

We're seeing this with our Windows guests too. Especially ones that have been imported from Hyper-V.

I just noticed this as well. We have some Windows VMs with uptimes showing over 50 days even though they are rebooted frequently. However we also have VMs that WILL show the correct uptime. We have the latest QEMU agent installed virtio-win-0.1.208 - why cant the agent relay the correct info?