Search results

Hi! Könntest du die Config des containers (i.e. cat /etc/pve/nodes/ha-node-01/lxc/105.conf) und den Output eines Debug-Starts des Containers (i.e. pct start 105 --debug) posten?

Hi! Mixing Proxmox VE versions in a cluster is not something we test against, except during the (hopefully brief) update procedure of the individual cluster nodes, so it's definitely not recommended to do that in a production environment. I'm not very familiar with Vitastor yet except the...

AFAICT from this error message, this is related to a wrong address width that is being sent to the iommufd (the vIOMMU functionality is provided by iommufd, which allows userspace programs to work directly with the IOMMU and therefore DMAR): vfio_container_dma_map uses iommufd and sends a...

Yes, the guest-phys-bits cpu option is now exposed via the VM config for Proxmox VE too. Setting the cpu in -args overwrites the CPU option provided by Proxmox VE and there guest-phys-bits and phys-bits could've been set before too, even though it's more fragile. Could you try setting the...

Great that it works. But no, for the intel-iommu it can only take 39 or 48 bits for now (it might allow 52 at a later time when 5-level paging is supported by QEMU, but that's for quite specific use cases and one needs the hardware that supports that, but I digress). The only thing that's...

I just sent the patch to the mailing list for review, if we go with exposing the aw-bits option then this patch will be available in a future release. For now, setting the machine version to 9.1 or lower or setting qm set <vmid> -args '-global intel-iommu.aw-bits=39' should mitigate the change...

Just to update this thread too [0], the Intel vIOMMU's default address bit width value was increased from 39 bits to 48 bits in QEMU 9.2, so the error Failed to set vIOMMU: aw-bits 48 > host aw-bits 39 can be mitigated by pinning the machine version to 9.1 or lower, which still has the old...

Hm, please look into whether /etc/apt/sources.list.d/ contains the Debian Trixie repositories, Proxmox VE 9 / Trixie repositories, Ceph Trixie repositories and that you run apt dist-upgrade. Other packages might be held back because Proxmox VE 9 package dependencies might not be available.

Hi! Which command have you used to upgrade the packages? It is important to always use apt dist-upgrade instead of apt upgrade as described in [0], because among other things the latter will make packages stay on a lower versioned package instead of resolving the package dependencies correctly...

Wie schaut denn die apt history aus (cat /var/log/apt/history.log - am besten als eigene Datei anhängen)? Ist Proxmox VE nach dem Ausführen der obigen Kommandos überhaupt noch am Host installiert (nach dem purge sollte eine Warnung kommen, dass man explizit eine Datei anlegen muss, um die...

Interessant, wurde der journalctl Befehl auch mit dem root user ausgeführt (nur dieser User hat Einsicht auf die Logs dieser Services)? Andernfalls deutet das eventuell hin dass auf dieser Node weder der CRM noch LRM Service gestartet wurde... Was ist denn der Output von journalctl -xeu corosync...

Danke, ich nehme an, dass der beschriebene Fehler bei der HLS-PVE3 Node auftritt? Wenn ja, was ist denn der Output von journalctl -xeu pve-ha-lrm und journalctl -xeu pve-ha-crm auf dieser Node? Ein Verdacht ist, dass das Lock für den LRM auf HLS-PVE3 nicht richtig freigegeben wurde.

FYI, one rather insecure way to mitigate this is to disable the apparmor profile for now with aa-disable /usr/bin/man or another slightly better solution is to use aa-logprof (in apparmor-utils package) which allows modifying the apparmor profile with interactive suggestions, but the latter...

Hi! Have you set up any man pager with the MANPAGER environment variable (echo $MANPAGER)? Either way, the audit message doesn't say much, but I can only guess that it could be about the seccomp(...) syscalls that man does make at startup to confine any children processes (like pagers, groff...

Hi! Wird auf dem Cluster aktiv der HA Manager betrieben? Was ist der Zustand vom HA Manager (ha-manager status / ha-manager status --verbose)?

FYI, multiple (external) users reported [0] [1] [2] that processes with the name "kauditd0" were malware running on their system / containers, especially because they try to imitate a kernel thread but are clearly not a kernel thread at all. [0]...

And what does ls -lha /proc/$pid/exe show? If it's a kernel thread (and kauditd normally is a kernel thread), then it won't exist. But in your case it exists and should be a symbolic link to the executable that is running in that process.

Hi! This is just a guess, but it seems like this is a process imitating the actual kernel thread kauditd, especially because kernel threads lack information like the uptime, cpu%, mem%, etc. Could you post the output of cat /proc/$pid/cmdline and cat /proc/$pid/exe for one of these kauditd0...

Unfortunately, that was a false flag as the patch that introduced the bug is not in v10.0.2, but is in the upstream's staging tree. However, a quick setup with a Windows 11 VM with a 9th generation Intel UHD 630 GPU in passthrough showed similar errors, I'll look into it, but I couldn't find any...

Hi! Assuming that JavitoVE is the Proxmox VE host, could you post the output of pveversion -v on that host?