Search results

Just adding into this thread now. Running Windows 11 on a ProxMox cluster with NFS backing is now a little bit more difficult. As I'm sure many people here do, I run ProxMox + TrueNAS NFS. I use the ZFS snapshots on TrueNAS as one level of protection, but being able to take a quick Snap of a...

To make myself feel better I doubled the storage to 100GB. Doesn't seem like I'll need it, but eased my mind a little.

This was very helpful. Thank you!

I am currently testing the Proxmox Mail Gateway on a low priority domain before we roll out on our primary mail domain. I see the recommended specs have 8GB available storage on the server, but I can't wrap my head around how that would be enough space for a domain receiving 10-15K emails a...

Well, I have two different setups. One with a local ZFS pool created with Proxmox. With that, I used this with some modifications - https://github.com/apprell/proxmox-autosnap. Then I pull the snapshots with a TrueNAS server. One other setups I have TrueNAS machines with NFS shares as the...

Just curious, what's your backing storage on this? We were having similar issues. Beat the lockups by using ZFS snapshots and replication to get everything backed up.

I don't think it is network related. Any high disk IO causes havoc. Noticed it with both NFS based storage and local ZFS. I'm sure adding faster storage would mask the issue, but it would only mask the issue.

Are you guys setting *all* of your VMs with virtio-scsi-single/iothread/threads or just the problem machines?

On one of my 4 nodes (all with identical hardware specs), the early stages of the monthly ZFS scrub push the IO_Delay on the host to very, very high levels causing some issues with the VMs on that host. In the past on my FreeNAS boxes, I used the tunable vfs.zfs.scrub_delay to lessen the scrub...

Honestly, this issue was so disruptive I almost switched Hypervisors over it. In the end, we stayed with proxmox due to our admin comfort level. We did spin up a new 4 node cluster with dedicated ZFS mirrors in each node. I have had no real luck with Proxmox and SSD's (just seem to have a...

Well, an easy way to check. Do you have any disks with known SMART errors that you are waiting to destroy? Pop one of them in and see what happens. I know having full access to SMART has definitely been a benefit in the past on our FreeNAS/TrueNAS machines.

If you pass through the iGPU to the VM it will be unavailable to your local machine (ProxMox Host). There is no hardware available to the local machine to use as the display to display the VM. You really need 2 GPUs or RDP/VNC/SPICE from another computer to make it work.

I am 99% sure when you set a PERC controller to JBOD each disk becomes a singular RAID0. So you have 4 single disk RAID 0 arrays.

I'm on ProxMox 7.1. Funny enough, on the same hardware we had zero issues on Proxmox 6.X. It was only after the 7 upgrade that these issues started.

What type of storage are you using for that VM? We're seeing similar issues when there is heavy IO on a NFS storage. Machines will lock up and go unresponsive.

My issue seems to span nodes. For Example: I have Nodes 1,2,3,4,5 and NFS Storage A and B Machine X is on Storage A, running on Node 1. Machine Y is on Storage B, Running on Node 1. Machine Z is on Storage A, Node 5. If Machine X is doing anything with high IO (backup is a great...

There seems to be some issues on Proxmox 7 when there is heavy IO on storage. Our cluster with multiple NFS storages will lock up VMs whenever there is heavy IO on a VM on the same storage. Never had this issue on Proxmox 6.

I want to keep an eye on this. There is a definite issue when there is a big hit on IO.

Can you confirm that the swap to NFS4 fixed your freezing issue? We have issues whenever there is significant IO on a VM that is sharing NFS storage. It's most noticable with our SQL servers. On Proxmox 6 with the same exact setup, we had none of these issues.

Ahhh, I guess I only halfway understood. This helps. Thank you!