Search results

Hello, Cluster with enabled HA will start migration on powerfail when UPS sends signal to shotdown. How can i avoid migration on this case? Thanks Wolfgang

I have today two production clusters PVE7 (each 3 nodes) of schools ( vacation) fully ugraded running with kernel 5.4. These cluster had kernel 5.15 and today ca. 20 VMs with spinning circle

Qemu was not downgraded! PVE 7 was fully upgraded, and one node had kernel 5.4.

Yes I never stopped the win10 VM just reset, and as i wrote earlier same behavior on PVE6 and PVE7

Thanks Proxmox Team, Just change on node of cluster 7.2.7 running kernel 5.15.39.3 to 5.4.98-1 On the node with 5.15 i have a Win10 VM with spinning circle, migrate to node with 5.4 reset VM and it worked.

Dear Proxmox Team, is it possible to provide a kernel 5.4 to PVE7?

Today i had one server 2019 running on a 5 node cluster with pve 6.4-13 and kernel 5.11.22 with spinning circle. First i migrate the vm to another node with the same config and reset the vm -> no luck spinning circle. Second i migrate the vm to a node with kernel 5.4.162-2 and reset the vm ->...

Its possible that you can update the kernel on the Old Cluster? Yes i can confirm proxmox 6.4 with kernel 5.4 i never had any problems.

PVE6 are all SeaBIOS

All i can say is we have this issue (spinnig dots) on all PVE7 and PVE6 ( exept kernel 5.4) yes it's EOL but the same problem with pve-qemu 5.2.0-6.

Just changed kernel of cluster 1 on one node to 5.4, now we have to wait.

Yes 5.2.0-6

hello as i wrote above: two cluster 6.4-13 1. pve-qemu-kvm: 5.2.0-6 kernel pve-kernel-5.11.22-5-pve: 5.11.22-10~bpo10+1 ===> problems with reboot 2. pve-qemu-kvm: 5.2.0-6 pve-kernel-5.4.78-2-pve: 5.4.78-2 ====> no problems since 1,5 years

Linux pve6-01 5.11.22-5-pve #1 SMP PVE 5.11.22-10~bpo10+1 (Tue, 28 Sep 2021 10:30:51 +0200)

I have another cluster 6.4-1 running kernel pve-kernel-5.4.78-2-pve uptime 522 days, with no Problems. PVE 6.4-1 with running kernel 5.11 has problems.

Here is my configuration, its a five node cluster: proxmox-ve: 6.4-1 (running kernel: 5.11.22-5-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.11: 7.0-8~bpo10+1 pve-kernel-5.4: 6.4-12 pve-kernel-helper: 6.4-12 pve-kernel-5.11.22-5-pve: 5.11.22-10~bpo10+1...

I have some cluster with 6.4 with the same Problem.

Has anybody the same problem with enterprise repo?

We have the the same problem on cluster running pve6 and pve7, never on pve5.