Search results

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?

Great that it worked out! The issue could've been that the node where the package upgrades failed because there wasn't any available source for these packages, i.e., there weren't any Debian Trixie repositories in the sources list. Anyway, it would be helpful to change this thread to "[SOLVED]"...

Thanks, so the Intel graphics driver's ctlInit fails and prints a CTL_RESULT_ERROR_NOT_INITIALIZED error (1073741825 = 0x40000001) [0], which unfortunately is quite generic and doesn't tell much about the error except that the Control API / device wasn't initialized at all. Later...

I'm not sure about what you're trying to do here: iface vmbr0 inet6 static address 2a01:4f8:10b:2119::***/127 up ip -6 route add 2a01:4f8:10b:***::/64 dev vmbr1 But you shouldn't reference other interfaces in the command then the currently referenced one. Or did you meant vmbr0 here?

Yes, plymouth is not the issue but there might be an issue while generating the initramfs, installing the kernel image, etc. So you can try to regenerate the GRUB config and check if the installation of the new kernel was successful (or try reinstalling the package) and check whether the host...

There's also another warning in your bootlog that might point in a direction: Aug 08 14:37:01 server networking[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device "vmb> Aug 08 14:37:01 server networking[694]: ) Aug 08 14:37:01...

Hi! There is a failing service logged in the bootlog: Aug 08 14:37:03 server (plymouth)[514]: emergency.service: Unable to locate executable 'plymouth': No such file or directory With the fact that the boot works with another kernel it's likely that there's something wrong with the boot entry...

Thanks, according to the output this looks like that there was an error while upgrading the packages and the packages were only upgraded partially. Were there any issues during the upgrade when running apt update and apt dist-upgrade? Were the bookworm/pve8 repositories removed/replaced in the...

Thank you both for the thorough reports! I investigated a bit and as already noted the kernel images should be the same AFAICT, even though these have different build times the versions indicate that these have the same upstream base kernel and patches applied. The only thing that stood out is...

Hi! On which versions are the packages on pve3 (output of pveversion -v)? Edit: It seems like an error from a partial upgrade where pve-cluster is not up-to-date yet.

Hi! If that also happens for any Live CD (e.g. Debian 12/13), then check whether there are any memory-related BIOS settings that might cause this (e.g. BAR, IGD, ...). It could also help to upgrade the BIOS firmware and/or reset BIOS settings first (if possible) and check whether the RAM is...

Are you sure? Or did I misunderstood that those errors are from within the VM? Especially with the error message above, I cannot see any reason that the host would fail with that error message if there wasn't any API breakage introduced by at least an upgrade of the python package.

You cannot run Promox VE 8 while also running on Debian Trixie on the host, because there are many API breakages inbetween. The error is caused because Debian Trixie already ships a recent version of Python3, where API was changed which affects ifupdown2 here. You need to also fully upgrade to...

How did you remove the old lrm exactly? If there are no resources, if the manager_status was deleted or the HA Manager doesn't have to manage any HA resources, then it is expected that the status won't show any CRM nor LRMs, because there are no HA resources to be managed. As soon as there are...

Thanks! Could you provide further information about the GPU passthrough (VM config, lspci -nnk, cat /proc/cmdline, any errors in the boot log / syslog at vm startup?, etc.)

Hi! According to [0] Code 43 for a device means: Could you verify whether using the older Proxmox VE kernel also has this issue for the Windows VM? [0] https://support.microsoft.com/en-us/topic/error-codes-in-device-manager-in-windows-524e9e89-4dee-8883-0afa-6bca0456324e