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)
it's definitely not the same issue, the OP could not passthrough at all for some reason. please open a new thread with a bit more info (e.g. the error code from the windows driver)
also try without viommu=intel on the machine and see here...
there is already an open bug on https://bugzilla.proxmox.com/show_bug.cgi?id=7374 but we don't currently know what's the underlying reason. (and we don't have the matching hardware here to try to bisect the kernel)
are you by any chance using a...
ok something caused the pdm to not reach the remotes though as seen by the journal.
has one of the migrated vm anything to do with networking/routing? is it maybe the pdm itself?
hi,
glaube zwar nicht dass es daran liegt, aber die zwei zeilen
hostpci0: 15:00.0,pcie=1,x-vga=1
hostpci1: 15:00.1,pcie=1
sollte man durch
hostpci0: 15:00,pcie=1,x-vga=1
ersetzen. Da werden dann auch beide devices durchgereicht aber als...