Search results

The problem still occurred several times. The GUI times out, but the background functions continue their work. In addition to the GUI, the problem occurs on Proxmox VE which is unable to access (for a few tens of seconds) the PBS storage, while functions such as verification, sync, etc. they do...

@mira the fact that you are working on the problem is the best news of the last six months. VERY VERY VERY VERY THANKS (I've run out of corners where my head bangs with every windows upgrade).

It is not a problem with the network connection itself. When the problem occurs, I tried to open a new connection to the login page and it doesn't respond (the login page), but if I connect in ssh to the server there is no problem. After about 15 seconds it resumes and everything works.

Nothing interesting in the logs. On the VM, if I roll back to 2.2-1 the problem goes away.

Another problem two minutes ago:

I can see.. only an additional note... after 10-15 seconds resume the functionality. This problem present on two different PBS, one bare metal and one virtual (on Proxmox), the common components are the datastore: NFS for both, but the datastore is connected to a specific network, different from...

I have an intermittent problem with several PBS upgraded to the 2.2-3 release (previously the 2.2-1 version had no problems). The problems occur (identical) both on a PBS installed in bare metal (the one in the screenshot) and on a PBS installed in a Proxmox VM. Every now and then the...

Many thanks for the confirmation @check-ict. And now how can we proceed @mira & & Proxmox support team? The snapshot test you asked for (also me in a ticket that I opened directly) I would say that it has been passed. Do you need further tests? Personally I am willing to change the repositories...

Nice work, your every analysis coincides with mine. I am left with one question, uncertain. Is there a link with the hardware? Are there systems that are affected by this problem and others that are not? I use Lenovo servers (quite a few) and they all have this problem. Other Lenovo systems that...

.. what do you mean for one time only? The problem occurs when the VM has been running for a certain number of days, whether there are updates or not. A VM that has been running for a month, without applying the slightest update on reboot exhibits the problem. Does it only occur once? Ehhh yes...

I can confirm, Proxmox 6.4 running on several hardware without problems !!! I run Proxmox 7.2 on Lenovo sr650 with very last UEFI firmware (10 June 2022) and there are problems....

Very bad news. UEFI firmware updated a few days ago. Mitigations = OFF Proxmox 7.2-4 completely updated. Reboot VM and ... infinite spinning dots. Could the virtio driver version be a cause? I use 0.1.215 This problem is consuming me .... every month we have 50 VMs in freeze, we cannot...

New firmware released by Lenovo 2022-06-10 included new Intel Microcode. Update ok, now test.....

But this is not the problem with the thread. In my opinion, despite the setting "mitigations = off" and a firwmare update (latest version available from February 2022) the problem of spinning dots remains.

Yes. 11 servers Lenovo sr650 They do not have this problem with the last UEFI firmware.

I personally think that this problem (KVM: entry failed, hardware error 0x80000021) is related to the specific machine and its firmware. I use more than 14 Lenovo servers, UEFI firmware as of February 2022 and I've never seen this problem. As mentioned before, however, the problem under...

mmmm I've never seen that error .. and I'm talking about a good number of clusters. While the problem of spinning balls when restarting VMs arises methodically.

... me too. Windows receives the restart signal from the QEMU AGENT or via ACPI, then whether the reboot signal is passed from the agent or inside the VM, what changes? For Proxmox a VM reboot does not imply closing the QEMU process and opening a new one, it always remains the same. Different...

Has anyone tried if disabling the mitigations the problem continues to arise?

This one ? Systemd-boot The kernel commandline needs to be placed as one line in /etc/kernel/cmdline. To apply your changes, run proxmox-boot-tool refresh, which sets it as the option line for all config files in loader/entries/proxmox-*.conf.