Recent content by bung69

I've just hit this too — happy to add a +1 to the existing bug (#6189) if that helps move it along. I get why the current default is to not let a backup prevent a VM from starting. But surely the second-best option is to back the VM up and block it from starting as a fallback, rather than...

Does QOS need to be set in proxmox? Wouldnt the effect be the same if the switches had QOS set on the appropriate Vlans and/or ports?

Yes, @bbgeek17 you have it right, i am trying to understand what is the limiting factor for low Q depth small block storage performance and why my benchmarks appeard much worse than your "proxmox-tuning-low-latency-storage/" results even though i am using lightly much faster localy attached...

Hi @bbgeek17 1. For most of my testing, my vm had 10 vcpu, type host and i tested both with and without affinity and numa. when testing iothread-vq-mapping at high Q depths and jobs i assigned 40 cores with affinity and 16 iothreads. 2. system is otherwise idle 3. all obvious bios settings...

note to future self and anyone thats interested, 1 million iops in a VM at higher Qdepths and threads is posible using iothread-vq-mapping and multiple io threads guide here - https://blogs.oracle.com/linux/post/virtioblk-using-iothread-vq-mapping args: -object iothread,id=iothread0...

What is the best expected latancy of storage within a VM? from reading https://kb.blockbridge.com/technote/proxmox-tuning-low-latency-storage/ it looks like their un-opimised guest is getting just over 50us, yet no matter what i try i am getting around 200-300us with raw image, virtio scsi...

Changing the bios setting from latancy optimissed to bandwith optimsed had quite a big effect. allthough i dont understand why the 256m read got worse. ioping is the same 256m Sequential Read: 1344MB/s IOPS=5 256m Sequential Write: 5493MB/s IOPS=21 512KB Read: 8258MB/s IOPS=16516 512KB...

Yeah i was supprised the throughput is as low as it is, though with higher Q and Threads it seems good. i will have to try with the bandwidth optimised setting in the bios too. Also this is only 2 interleaved dimms. I made the mistake of buying 256GB dims before i realised i would need...

No problem. heres a few that i think are the most relevant. i can do some more if theres anything specific you want to see. allthough i havent tried, i expect its posible to install Rocky on to a Fdax or raw namespace for increased performance. please take results with a huge dose of salt as...

An update for future me and anone else interested in optane Pmem. pve-qemu is compiled with --enable-libpmem as default. if namespaces are fsdax or dax, 2M aligned and passed to VM aligned to 128m native performance can be achived. i followed https://nvdimm.docs.kernel.org/2mib_fs_dax.html...

Thankyou. turns out pve QEMU seems to support nvdimm out of the box - i just typoed my -arg's

Hi, i am Trying to compile QEMU with nvdimm support. previously compiled custom versions of PVE QEMU however this time i am having a problem recursivly cloneing the proxmox qemu repo. when running: git clone --recursive git://git.proxmox.com/git/pve-qemu.git Resolving deltas: 100%...

Hi, did you get any further with this? any luck with compiling with --enable-libpmem and running VM with args pmem=on for migration to work? Thanks

ahh of course, it was the recursively bit i missed last time i tried. thankyou

Did you ever solve this? can you outline the process to build QEMU on proxmox?