Thanks will open a ticket, if I recall correctly there were some murmuring recently from some people about primary paste being obsolete but since it works outside of the xterm context I don't think they killed it yet (that would be a sad sad day...
OK, die vfio-pci Bindung ist jetzt sauber, das war's also nicht. Wenn JEDES PCI-Passthrough den Node unter 7.x einfriert, liegt das Problem tiefer, vermutlich IOMMU/VFIO-seitig im neuen Kernel.
Poste mal zwei Sachen zum Vergleichen:
Unter dem...
I think we've found a possible workaround for the moment, to avoid the crashes (we are in contact with HPE with an open case, in case it's a hardware or firmware issue). We are not seeing the crashes after changing de discard option at the pool...
Confirmed working on HP DL360p G8 with P420i on firmware 8.32 (latest).
A few notes that might help someone:
1. The controller automatically creates a temporary logical volume when it detects a disk. You MUST delete all logical volumes before...
ok on firefox 151 on wayland (sway here) i can see that the copy action with middle click does not work (in chrome it does)
not sure why that is though and if were even able to fix it from our side (might be a firefox issue)
could you please...
Hi everyone,
there is a known regression in Kernel 6.8.12-29 concerning IOMMU which can cause these types of errors. See [1] for context.
Kernel 6.8.12-28 is the last known good in this case.
Yours sincerely
Jonas
[1]...
Ok, sadly this is expected. In 6.8.12-29 there is a known regression in context with IOMMU which causes these types of errors. See [1] for more info.
In this case please install and pin kernel 6.8.12-28 as suggested in the other thread, which is...
Ok, sadly this is expected. In 6.8.12-29 there is a known regression in context with IOMMU which causes these types of errors. See [1] for more info.
In this case please install and pin kernel 6.8.12-28 as suggested in the other thread, which is...
This doesn't work, because pve-network-interface-pinning will not generate if there is a pinned name already. So, I'll have to remove the Links first. Now I'm not very confident in your answer, I'm sorry to say, as your way won't run in the first...
Thanks for providing the info!
As you can see here
Ceph actually knows about the traffic but doesn't seem to consider it for the status page.
While i can't say for certain if this will fix the issue, i'd still urge you to update your servers...
Yes.
- First run pve-network-interface-pinning as shown above
- Then, afterwards, remove the .link for the old interface name under /usr/local/lib/systemd/network/.
- Finally, reboot
The pve-network-interface-pinning takes care of updating all...
Hello torbho,
You are right after a reboot the OSDs go "down"... and the system restart before the OSDs go "out".
For the configuration "mon_osd_down_out_interval" we have the default 10mn.
So no "noout" necessary, thank you.
Francis
Yes, that's what I tried to communicate. So, the removal of these links is all I need? Then I can pin the names I want? It read in the posts out there like other configuration files had to be edited, too.
Hello torbho,
You are right after a reboot the OSDs go "down"... and the system restart before the OSDs go "out".
For the configuration "mon_osd_down_out_interval" we have the default 10mn.
So no "noout" necessary, thank you.
Francis
If they are named nic4 and nic5, then they are were already pinned by the installer. It's our default naming scheme.
Afterwards, you just need to remove the old file at /usr/local/lib/systemd/network/50-pmx-<oldname>.link.
In order to upgrade I had to re-apply the commands you provided on a previous post:
rm /run/proxmox-datacenter-manager/api-cache/remote-*/subscription-state.json &&\
proxmox-datacenter-manager-admin support-status update &&\
apt update...