thanks for reporting, we forgot to pass the endtime from the list to the task viewer and then it takes the current time to calculate the duration.
sent a patch for it...
hi, thanks for reporting again, it seems there was a problem with indexing it. a colleague fixed the issue and uploaded a new version of the arch template. should be available after a 'pveam update'
anything in the logs of the guest? if really nothing changed on the hypervisor side (no updates/no bios/firmware update, etc.) then it's possible a guest update broke it?
in the past, such things happened in other browsers (e.g. firefox) when there was 'fingprinting resisting' enabled, so that a website couldn't fingerprint a user with e.g. drawing characters on a canvas (which is exactly what happens in xtermjs)...
not sure how the url decoder decode this, but when i do it on the command line i get similarly garbled output:
printf $(echo "%C3%AB%C2%8C%C2%80%C3%AD%C2%98%C2%84" | sed 's/%/\\x/g')"
output:
ëí
( i replace the '%' symbol with '\x' so that...
did you try to install the nvidia driver? does the card work in the guest? the screenshot only shows that the card shows up in linux and the nouveau driver is used...
sadly we don't have the hardware here to test, but one thing that might help is the output of 'dmesg' after you plug in the enclosure (without running lspci)
this sounds especially worrying as the pve ui does not touch this part of the system at all, even when adding a new user.
i'd first try to re-establish a successful login via ssh, and then look in the journal/syslog to further diagnose the...
answered in your other thread: https://forum.proxmox.com/threads/proxmox-vgpu-configuration-troubleshooting.182337/
please don't double post in the future
hi,
since this is an english forum, please write your posts in english.
here the translated post:
is that the correct ip range for your network? did you enter 'https://192.168.1.110:8006' as your url in the browser?
hi,
did you try with other linux flavors too?
only found https://community.frame.work/t/0x08000800-uncorrected-error-causing-a-data-fabric-sync-flood-event/79286
which points to a kernel issue
(it's different hardware though)
interesting, did you do more than that? because there should be no difference between activating the 'ALL' service vs activating all 3 individually (nvidias script basically first finds all nvidia cards with 'ALL' and then does the same for each...
i did not have access to such systems, but i think you could either do vgpu via ai enterprise, or passthrough everything, see this note in the nvidia docs...
you should be able to gzip it , e.g. by piping it into gzip
journalctl <your journalctl parameters go here> | gzip > journal.log.gz
a good start would be to use the '--since' and '--until' flags to limit the journal to a specific timerange...
please don't double/cross post your issue across various threads. instead open your own when the issue is not the same (as i told you in the other thread)