Recent content by xenon96

An alle Interessenten, also ich habe mein MS-S1 Max Setup genau so hinbekommen wie ich es mir vorgestellt habe, und das war eigentlich sehr einfach. Ich habe mich vorab schon viel informiert und mir viele Foren durchgelesen und Lesezeichen gesetzt, letztendlich war es wirklich total einfach. -...

My issue went away by moving back my iGPU-Passthrough to a NVIDIA-Passthroungh to my Plex VM. Maybe the issue itself Game from the strongtz/i915-sriov-dkms By disabling the driver everything works Fine again. PS: I Enabled the Driver again and only do Windows-Passthrough, this works fine and...

Hast du es noch zum laufen bekommen? Kannst du nochmal eine kurze Zusammenfassung schreiben? Ich bin am überlegen, mir eine Strix-Halo Plattform zuzulegen, und das wäre definitiv ein Pluspunkt wenn das funktioniert. Zusatzfrage: Theoretisch kannst du die GPU dann ja mehreren LXCs parallel...

Yes, I have a Minisforum MS-01 with Intel 13th Gen CPU with Litte-Big Endian architecture. And sometimes I have some Segfaults - I'll try to see if this comes from jumping cores from P-Core to E-Core or vice versa. So with lxc.cgroup2.cpuset.cpus I do not take resources away from the other...

sorry, I think you misunderstood me or I expressed it incorrectly. I know that there is exactly this setting for cpu-affinity in kvm, but this works like: - kvm has 2 cores - affinity is set to 0-11 => kvm selects 2 cores out of the set from 0-11 lxc.cgroup2.cpuset.cpus works this way: - lxc...

Is there a way to set this as "affinity" (like for kvm / qemu) ? So if I set cores: 2 and also set lxc.cgroup2.cpuset.cpus: 0-11 (because of little-bit endian architecture), the lxc sees all 12 cores instead of only two (from the pool of 0-11 / 1-12).

So pvestatd crashes again. It seems there is another problem, or the original one is not solved. First, I'll run a memtest next week. But @fiona, why there is no Restart=always in the pvestatd service? I manually addad this line, as long with RestartSec=60 (to [Service])

This is not solved on pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.14.4-1-pve) @Xedon, @tomtom13 do you solved this by manually installed the driver? Or how you solved this?

Everything is still up and running. I tihnk thats a working solution

I'll do it, next week. I'm currently remodeling the office and can't connect a montior and don't have KVM configured. @promo2100 @fiona I maybe found a "stable" workaround. Currently everything is running fine since ~15h. I have set cpuaffinity on all my QEMU-Machines. Every machine now only...

With 6.8 Kernel the system is unreachable after a while. I think its a kernel-panic and the whole system goes down while with >=6.11 only the pvestatd crashes. Thats the log before the reboot, but I don't think its very meaningful. So I have no solution for this yet. I'll go back to 6.14 and...

@fiona kernel 6.11 does not help (last 2 days several deads of pvestatd). Downgrading now back to 6.8 ...

I have installed the latest micocode: # grep microcode /proc/cpuinfo | uniq microcode : 0x4124 I'll try this the next days. But yes, after the update to 6.14 this became much more frequent. Before I also had the problem, but rather once a week / a few times a month. But it didn't...

Before this logs, there are some messages which are interessing (may warnigns or errors?). This messages are before the above one (see timestmaps)

pvestatd is failed again. Please tell me if I should debug specific logs / services. Unless I'll keep posting error messages.