Recent content by Juan Pablo Abuyeres

It was some faulty memory sticks. We removed them, and things look good so far again.

It worked fine for several days, but now I have this in one node: [324845.995993] BUG: unable to handle page fault for address: ffffffff00000008 [324845.996316] #PF: supervisor instruction fetch in kernel mode [324845.996610] #PF: error_code(0x0010) - not-present page [324845.996854] PGD...

This has helped us on the kernel (IO) stuck issues https://forum.proxmox.com/threads/cpu-soft-lockup-watchdog-bug-soft-lockup-cpu-0-stock-for-24s.84212/post-452383

Hi, which virtual disk controller are you using?

Finally!!! Thank you!

Attaching complete journal of the day this happened

This is very strange. We have a 6-node cluster. The newest node is the only one with a Xeon Platinum 8358. The others are mostly Xeon Gold 6154. The newest node had over 100 VMs. Out of the blue, a few VMs on the newest node started to malfunction. They weren't frozen, we could still log-in, and...

Did you have to rollback the older cpu node? or everything?

Bitten here by the same problem :/ We subscribed to the enterprise repository to avoid this kind of problems :/

https://pve.proxmox.com/wiki/Storage Look for "Preallocation mode"

Great! Thank you!

Hi, I have to resurrect this topic. One of our VMs has a 5Tb raw virtual drive. When trying to move that disk to another storage, the hipervisor issues this command: /usr/bin/qemu-img create -o preallocation=metadata -f qcow2 /mnt/pve/SN7/images/373/vm-373-disk-0.qcow2 5368709120K That takes...

Hi, this just happened here. Once. I tried to reproduce, but I couldn't. Here is the relevant information: Node A (Origin) root@tcn-05-lon-vh22:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve) pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754) pve-kernel-5.4: 6.2-4...

Hi Fabian, Would it be possible to include this https://github.com/TheGrandWazoo/freenas-proxmox into the main proxmox repository? Regards, JP