Search results

https://fedorapeople.org/groups/virt/virtio-win/CHANGELOG They did in the past some sort of changelog, but lately there is none. All you can do is collecting yourself a changelog based on Commets and Tags from the github repository: https://github.com/virtio-win/kvm-guest-drivers-windows Bit...

Sorry i didn't had time to Reply on the Docker Thread xD But now i do. This may not be really correct what i said in this thread, because that was the time i just learned about Numa etc... And at that time, i didn't knew that Numa isn't working Correctly. It was just the beginning. There where...

Thats correct. But that info was still good. Between 2 nodes, i would need a 100gb Connection, that i dont have to test properly. Just 2x 25g

In the context of NUMA (Non-Uniform Memory Access) configurations, it's crucial to understand that the significance extends beyond just memory; the L3 cache plays a pivotal role. On Genoa platforms, L3 caches are distributed across NUMA nodes, with each cache supporting eight threads. This...

This is exactly what we want: If you enable this feature, your system will try to arrange the resources such that a VM does have all its vCPUs on the same physical socket Socket = Numa-Node The issue is, that this doesnt work at all. Not even a bit. And its absolutely critical on Single-Socket...

Read what @Dunuin said. My preferred way tbh is to use LXC-Containers and Passthrough a ZFS Folder (dataset) from the Host to the Container. Those datasets which i passthrough, have all Hourly ZFS-Snapshots and are only exclusively for the Samba Shares. And Samba has VSS enabled or defined, so...

Which nag-screen? xD Do anyone here really still "realize" that there is a Nag-Screen and removes it? xD Edit: I think Proxmox has the most unobtrusive Nag-Screen or Ads etc, that i've ever seen. Check this out: https://www.youtube.com/watch?v=PF9QYLOFZyE xD

I think tbh, that we will regret it. Docker has Compared to LXC Containers a huge amount of Options/Features and i don't believe that we will get anything usefull in the GUI, so we will still prefer the CLI. I mean we still don't even have Numa Support, which makes Proxmox mostly useless on...

Is there any timeframe when it reaches the pve-test repo to check out the impact?

I had never issues with intel Cards, i had issues with multiple Mellanox ConnectX 4-LX Cards, that have issues with vlan's. Actually all Mellanox ConnectX 4-LX Cards in the OCP Formfactor, while the normal PCIe formfactor had no issues. But im avoiding all of them. Generally i do prefer...

I had an x520 fake, the card worked actually without any issues, it just runs hotter as an genuine one and the speed is limited to 5/6 Gbps max with jumbo frames, without ~4 Gbps Original ones reach over 9 Gbps without jumbo frames already.

Issue: Update package database Task runs since 23h - I know i can disable the regularly Proxmox Package Updates with disabling pve-daily-update.timer But this will disable acme certificate updates and a lot more, not just apt update - I know i can simply kill apt and fix the issue, but i have...

I suspect that there is something in the compression pipeline. Because like i mentioned in the Bug Report, even if the way the Backup works with PBS compared to Local-Storage Backup, the limitations are all exactly the same. Or the speeds are identical between Local and PBS as soon as...

Only those 2 Genoa Servers with 9374F. Everywhere else i don't have an PBS, that can keep up. Or don't need an PBS etc...

Yeah PBS Speeds are very limiting. About the CPU, you're right, i never throught it makes so much of a Difference. With some Cheap Silver 4210R CPU's i cannot break 200MB/s either. But i never looked to that servers, as they are only front-servers for Opnsense instances: INFO: virtio0...

Ich denke der Sucht eine Lösung um Backups von seinem Hetzner Server zu machen. PBS auf ner Hetzner Box ist absolut nicht empfehlenswert, die Box ist unterirdisch was iops angeht. Die einzige lösung ist, die Box direkt zu verwenden ohne PBS, und dort dann Backups darauf zu machen. Da kommts...

can you test with "sync mode: none" in PBS under Datastore -> Your Storage -> Options -> Tuning Options ? INFO: starting new backup job: vzdump 150 166 135 --notes-template '{{guestname}}' --quiet 1 --prune-backups 'keep-all=1' --fleecing 0 --mode snapshot --notification-mode...

set recordsize to 1M on the Backupserver. Should give you a huge performance boost. xattr=sa (i would recommend this too) dnodesize=auto (Only recommended if you begin with, not afterwards if there is a lot data on the pool) I reach here with normal SAS-Drives 800MB/s - 1GB/s Backup speeds...

Thats all easy. In that department there is actually nothing that is missing. There are only some weknesses: - ZFS-Zvols beeing 5x slower as they should be (but that is an ZFS issue, nothing the Proxmox devs can do about) Just mentioning this, because thats the "default storage option" for most...

No it make absolutely no difference. The socket option makes only sense if you enable the numa option. But that just tells the OS in the VM itself to use numa. Which is as i said previously absolutely senseless either 99% of the usecases. (I dont know any usecase or anything that does benefit...