Search results

Indeed. And also to note it is still marked as experimental as well as not being completely documented as yet. Patiently waiting for further improvements.

And then it was March of 2024...

I can confirm that it's a measure of data read/written by the disk. I copied some data around on the OS disk and saw the reported values in the OS match up with the Disk IO graph for that VM. I would presume it's KiB/MiB as that is what is used in other places in the Proxmox GUI. What could be...

Is there a way to know when Optimal will become Actual? I thought it might take some time to start a rebalance but it has shown Optimal 256 and actual 128 for a couple of weeks now. I understand the defaults are most likely fine and only need to be manually adjusted in very specific cases but...

If you've come across this thread from a google search like I did, please add your voice to the enhancement request over at: https://bugzilla.proxmox.com/show_bug.cgi?id=1083

Add your voice here: https://bugzilla.proxmox.com/show_bug.cgi?id=1083

Thank you so much @aaron for this excellent explanation. It makes perfect sense now. Oops no... I couldn't find an answer on this so I put them on the same subnet. My thinking was that in the case of a NIC failure, that it would not be able to route to the other subnet since I have no router...

Hi everyone I have 4 nodes running 7.1-10 with each node having 5 x SSD's. I have set up CEPH and created monitors, managers and metadata servers on all of the nodes. I know that not all nodes need to have these set up but the plan is to expand this cluster in future. I've created OSD's for all...

I'd also love to know. I've had a cluster running with 802.3ad LACP across 2 x Cisco Nexus 3064's spanned with VPC in a lab environment for some time now and cannot see any negative effects so far

Sorry to resurrect this old thread but I thought it might benefit others that come across it. I was not aware that always-on or hot-standby was not a feature of Proxmox HA and only discovered this after commissioning 8 servers in a cluster with CEPH. I made the mistake of assuming that this...

Thanks that seems to have done the trick. Back to my normal vCPU and hardware setup and running stable for a few hours now

Having the same issue but KVM64 vs host didn't seem to make any difference. With the vCPU set to 1 it has been stable so far. I noticed some updates waiting for Homeassistant OS so will apply those and see if it makes any difference

There we go https://forum.proxmox.com/threads/grub-not-updating-with-update-grub.68699/

Having the exact same issue on 7.0-11 with Kernel 5.11.22-1-pve and 5.11.22-3-pve It seems at least somewhat related to this very old kernel bug that was picked up on Ubuntu https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488426 Editing the grub boot option to include...