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...
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
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 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%...
It didn't help me. I set q35, loaded the virtual machine. Updated windows devices. I ran a reboot of the guest operating system and the system hung just like the previous time.
Windows 10 virtual machine freezes when shutting down (or rebooting). When this happens, one VM core is ~100% loaded.
The display of the virtual machine is black. The RESET function on the virtual machine does not lead to any result. Only STOP and then START.
Also with the same machine, the...
i fixed this problem with this patch:
ibp-proxmox:~# diff /usr/share/perl5/PVE/Storage.pm.dist /usr/share/perl5/PVE/Storage.pm
1143c1143,1144
< if ($line =~ m/^(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}:\d+)\,\S+\s+(\S+)\s*$/) {
---
> #if ($line =~...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.