Recent content by Vasily Poterjyko

I have Supermicro X9DRi-LN4+/X9DR3-LN4+, integrated Ethernet Intel I350 network card. After updating and rebooting to kernel 6.8.12-5, I saw that my network adapter is not visible in the system In dmesg I found an error: [ 3.018745] igb 0000:06:00.0: BAR 0: can't reserve [mem...

I have Supermicro X9DRi-LN4+/X9DR3-LN4+ I had pve v7 for a long time. Today I decided to update to pve v8. After updating and rebooting on kernel 6.8.12-5 I saw that my network adapter is not visible in the system. lspci shows that the system has an Ethernet Intel I350 adapter. Booting on kernel...

As described above, I changed the cluster name and configuration version in the /etc/pve/corosync.conf file. Then I restarted the service. However, after that, in the ui, in the Datacenter (...) tree, I see the old cluster name. In order for the name to be updated, you need to restart the...

Do you have any news on this encryption?

I am also interested in this question. Have you found any solutions?

Thank you very much! Your answer helped a lot. Why hasn't this information been added to the official proxmox documentation yet? There is not a word about this on the page https://pve.proxmox.com/wiki/Renaming_a_PVE_node

How can this setting be configured? So that the notification is sent only after the third unsuccessful replication? Is there any mechanism provided?

In virtual machines that use OVMF (UEFI) Bios, it is necessary that an EFI disk be added. If such a disk has not been added, then the problems described in the branch are observed. To solve this problem, you need to add an EFI disk. When adding a disk, you must uncheck the "Pre-Enroll Keys" option.

After a short rest, I again returned to the analysis of this problem. I cloned a virtual machine that was configured with UEFI. The configuration of this machine did not have an EFI drive connected. I created such an EFI disk in the GUI and started the virtual machine. The noVNC screen said...

Thank you very much for your reply! I'll check out what you suggested for increasing the machine recovery timeout from hibernation. I created a feature request. https://bugzilla.proxmox.com/show_bug.cgi?id=3911

Restoring a heavy machine with >270Gb RAM. The state of the machine is on SSD disks, reading the entire volume of this file takes less than 300 seconds, but I still get the timeout of the machine restore operation from hibernate. How to increase VM recovery timeout? I also want to note that...

I am still seeing this issue. I was under the impression that the problem is only on virtual machines with uefi bios.

I ran into exactly the same problem. Restoring a heavy machine with >270Gb RAM. The state of the machine is on SSD disks, reading the entire volume of this file takes less than 300 seconds, but I still get the timeout of the machine restore operation from hibernate. How to increase VM recovery...

With a dozen machines running windows10, after updating windows, you have to manually stop "press the STOP button" and then start it. These machines cannot reboot themselves, they freeze at the moment when the reboot itself should be. At the same time, one processor core is loaded at 100%...

Is there a solution for this problem? I have the same problem.