Search results

as i already wrote on the beginning of the thread, this is (at least it seems so) a tighter restriction that is requested by the hardware (in this case the mainboard) the linux kernel just enforces it now. I don't think it's a bug in the kernel per se, but if you think that, a bug report to...

hi, did you try to verify the corresponding snapshot once? maybe there are reused chunks that are corrupt/broken? indicates a problem with the underlying storage, so i'd check the journal/syslog/dmesg on the pbs host

hi, you probably already checked, but is there a firewall active (e.g. on the PVE host?) that would prevent this traffic? if not, wha'ts the output of traceroute google.com ?

i'd like at least the output of journalctl -b dmesg lspci -nnk and the start task log as well as any relevant logs from the guest (also journalctl, dmesg, lspci) no problem, just update the thread when you have the information

well the most interesting things would be the host logs in a not working state, else i cannot even start to search where the problem might be. As i said, a start would be to try the 6.14 kernel on the host, if that fails, we have a candidate to look where there might be a regression

thanks for the feedback! always nice to hear that users/customers are happy :) just fyi: if you have a subscription, you can enter it in your forum account under 'account details' and then you get a 'subscriber' badge here, so we (and others) know that you have a subscription no worries, we try...

sadly SMART data is not really standardized and some vendors use offsets or different units or formats for the temperature. Better monitoring for the temperature can be done by loading the 'drivetemp' module with `modprobe drivetemp` and using the `sensors` binary from the `lm-sensors` package...

Usually there are other monitoring solutions in place, either installed on the host directly or some don't need anything special installed, e.g. checkmk (these can often connect via ssh and check the system with standard tools or via the api)

i just want to point out that I'd like to help, but as I already said with the information at hand I cannot. You did not provide any of the information I asked for (journalctl, dmesg, lspci, etc.) from a clean state, so it's impossible to say why it's working on pve 8 vs pve 9 It might be that...

as i wrote, the journal from the host would be interesting. you can get that with 'journalctl' e.g. all the logs since the last boot would be 'journalctl -b' or if you want to specify a date you can do something like 'journalctl --since 2025-09-15'

ok thanks for testing, then i'll continue looking for the culprit

ah ok, if that version is the culprit, then I think the cause of the bug(s) should already be fixed in git by this commit: https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=c2e2559d2176062c44aab9fc934f67f047ac585b it's not yet bumped/packaged yet for the 8.4 branch but if some of you...

from the exceprt of the log, i guess that you're german speaking ("Herunterfahrtyp") so i guess you're currently in GMT+2 timezone? then that would somehow fit because the timestamp: is in UTC time, which would correspond to around 03:00 in GMT+2 yes, i'd assume that the shutdown would be...

could it be possible that somebody pressed on shutdown from the pve ui ? (or via the pve api/cli) ? if the guest-agent is configured and installed, it will be used when shutting down a vm from the PVE side EDIT: ah sorry, saw just now that you already looked in the task list maybe look...

coincidentally i recently had also a ryzen 1700 processor that seems to be defective. it ran without problems for years, but recently i changed the power supply (that is good & new) and the processor would hang or reset. i replaced it with a different processor and the issues are gone. there...

no, such hooks are currently not implemented, but i can see that triggering some things on some events in the cluster could make sense. you could open a feature request on https://bugzilla.proxmox.com (also maybe a colleague there has another idea to do what you want)

hi, what do you mean exactly with ? what happens when you do choose it?

not that i'm aware, but you can always open a feature request on https://bugzilla.proxmox.com (no promises though) in general, there speaks nothing against installing things like telegraf on the proxmox host directly, as long as you know what the packages do and can handle any problems or...

it seems this error comes from ansible itself, so has nothing to do with pve really, not sure why this only comes up on pve9 installs it looks like there is somewhere a \uDCE9 character in the text (https://www.compart.com/en/unicode/U+DCE9) maybe that happened with copy and paste ?

interesting, seems qemu believes this gpu is an itegrated one and tries to apply it's quirsk/requirements for it. can you open a bug on https://bugzilla.proxmox.com so we can track this better? (it's probably an upstream bug, but still good to keep a record on our bugtracker for it)