Search results

Hello everyone, I've been using PBS on NFS storage (on several installations) for some time now, and I'm used to some kind of performance. For example, a full SSD datastore (on the NFS datastore) I know takes 2 hours for a full garbage collect, etc. (datastore from 25 to 300 Tbytes). This was...

7.2-7 ? Uses Qemu 7.0 ?

Yes, I use 28 PfSense (FreeBSD) on similar VMs on SeaBIOS... never a problem.... after 180+ days runtime

sorry ... I use 28 FreeBSD VMs distributed on 6 Proxmox clusters and I have never had problems ... OK, I don't use Ubuntu, only Debian, but relative to FreeBSD .... ???

Hi everyone ! The fix included in Qemu 7.0 seems to work fine. No VM from Windows 2012 to 2022 has more problems in reboot. Windows 2008 never introduced them. There remains a small problem, in my opinion related, at least to the timer and long time to run type. All Windows 7 VMs (and only...

I can confirm !!! Two nodes cluster, Node 1: Proxmox 7.2 enterprise full upgrade, Node 2: Proxmox 7.2 enterprise full upgrde but with Qemu 7.0. VM Windows 10 running on node 1 (25 days) . Reboot VM: spinning circle. Reset: spinning circle. Move the VM on node 2: reset: OK !

OK, did you turn off / on the VM after upgrading to Qemu 7.0 or did a motion to / from another node?

No, I am referring to the "QEMU" software that you use on the server. In the enterprise repository it is not yet available, only in the CE one. You need to upgrade "pve-qemu-kvm" from release 6.2.0-11 to 7.0-2 (see the posts above).

On Qemu 7.0 ?

... after 369 posts, seeing the phrase "the problem is solved" makes me a little touched.

The simplest method ... Add the test repository via gui, update, DO NOT upgrade otherwise install everything in testing. Via cli ... apt install pve-qemu-kvm then deactivate the test repository.

Yes @mira , I can confirm too. On a host with Proxmox 7.2-7 enterprise repo I am using Qemu 7.0-2 with no problems.

Very thanks @mira I hope to close this bug as soon as possible, after 8 months of delirium (by now we have got into the habit, before the monthly upgrades, to turn off and on the VMs, a hundred, so as to restart them without problems at the time of the upgrades).

Thank you @wbumiller and @spirit !!!! @wbumiller why did you release the patch in question on Qemu 7 series? Is the intention to release the next Proxmox 7.3 with Qemu 7 series? I have a test node in 7.2-7 enterprise, with Qemu downgraded to 6.0.0-3 (see above) I wonder if it makes sense to...

sorry, in detail which modification? Several have been proposed ... Various downgrades, tuning in VM options, etc.

Perfect. While you try to use 7.2-7 nodes with a 5.4 kernel ... A question arises spontaneously to the Proxmox Developers ... If it is true that a 5.4 kernel does not give problems all else being equal, while a 5.11 or higher kernel does, how does it differ?

Very interesting, I am convinced that with a kernel 5.4 also Proxmox 7.2 does not present problems (obviously to be verified, it would be interesting to do so). Do you have a test node with Proxmox 7.2-7 completely updated but with the kernel a downgrade to 5.4, so that you can test it for 30...

@fiona in light of the above, if the tests on the Proxmox 7.2-7 node completely updated but with QEMU downgrade to version 6.0.0-3 are NOT successful, I propose to bring that node to the latest QEMU release but to bring the kernel to the latest patch of the 5.4 series We have to isolate one...

.. downgrading the kernel may cause hardware problems, in the sense that you may run into unsupported hardware components. I think you can only do this type of test on older servers or with older components added. Apart from that, one thing should be investigated: "On the node with 5.15 i...

@fiona OK, applied the August updates to the two VMs I have in test, Proxmox 7.2-7 and Qemu in downgrade to 6.0.0-3 (see above). Regular reboot. I remember that the system certainly presents the problem of circle spinning. OK, I know, it doesn't mean anything after a 6 day uptime, but I'd...