Whatever's latest activity
-
WWhatever replied to the thread W2025 virtio NIC -> connection drop outs.Have you fired bug report on virtio github?
-
WWhatever reacted to RoCE-geek's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with
Like.
Hi all, I'm the author of this ass-kicking post. After more than year, I'm back to service, as bug hunting never ends. I'm sorry that I've missed many of the questions and messages, but let's move forward, we have another urgent problem(s). In... -
WWhatever reacted to anon123's post in the thread reducing CEPH Quincy loglevel (mgr / pgmap) with Like.
I'm happy to report that using the latest version of Squid (19.2.3) the command ceph daemon {monId} config set mon_cluster_log_level info now does reduce the logging output. You have to execute this on every server hosting a monitor.
-
WWhatever replied to the thread Correct VM NUMA config on 2 sockets HOST.Thank It's all clear now. Thanks.
-
WWhatever reacted to readyspace's post in the thread Correct VM NUMA config on 2 sockets HOST with Like.
Hi, in numa0/numa1, the cpus= list refers to guest vCPU indexes (0…vCPUs-1), not host CPU IDs. Affinity is the host cpuset for the whole VM process (all vCPU threads), not per-vCPU. Proxmox VE (QEMU) doesn’t expose per-vCPU pinning in the VM...
-
WWhatever posted the thread Correct VM NUMA config on 2 sockets HOST in Proxmox VE: Installation and configuration.Good day Help me figure out and implement the correct virtual machine configuration for a dual-socket motherboard (PVE 8.4, 6.8.12 kernel) Given: root@pve-node-04840:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes...