Search results

thanks for the report, the issue is that the device is on the second pci domain '0001' which is a bit uncommon i can see our code does not handle that correctly, and tries to prefix it with the first pci domain '0000' which leads obviously to a wrong pci id would you mind reporting this on our...

hi, thanks for reporting this bug! i can verify this behavior when the account is 'unset' (and it should take the 'default' account) it should work when you manually select your account on the top right (the 'pencil' icon)

normally you would not install manually the .run package or .deb package but use the built in package manager, e.g. apt install <some-package> this will download the package automatically you can't install both the package and the .run file simultaneously since those will conflict with each...

aside from that article being a mess in certain parts (e.g. showing a screenshot of 7.1 iso, then the 6.0 installer...) i don't get how they did arrive at that conclusion, PVE could add (external) storages far longer than 6.0 (even before i started here ;) ) LVM/ZFS/Ext4/Xfs creation on the gui...

you can't AFAIK, the client terminal program can't tell the terminal environment in the vm it's size since it's over a serial connection (even if it's just virtual) and this has no mechanism to do so as i said, it's much more ergonomic to just use ssh to connect to the vm instead it's possible...

that's kinda expected since the connection with `qm terminal` is only via serial interface, which has no way of exchanging information about the terminal size (in contrast to a local terminal) you can show the size with stty size and set it with stty cols <columns> rows <rows> also i did...

no the link says install the 470-tesla variant, since it's listed on this page for the 470 driver: https://us.download.nvidia.com/XFree86/Linux-x86_64/535.183.01/README/supportedchips.html did you use the nvidia-detect script? what was it's output? also this is also only necessary if you use...

if you want the card to use for transcoding, you have to install the correct nvidia driver on the host, you can use e.g. this debian guide: https://wiki.debian.org/NvidiaGraphicsDrivers if you have successfully installed that, there are a few devices you have to give to the jellyfin container...

you can either directly modify the config file in /etc/proxmox-datacenter-manager/remotes.cfg or you can use proxmox-datacenter-manager-admin remote update <id>

Hi, just to make sure: the base load of the system was the same during the two tests? (so no garbage collect/verify/sync/backup running ?) but yes, I can imagine that depending on the cpu/disk adding more thread to a possibly already loaded system will make things worse, that's one of the...

Hi, what does that mean exactly? Where would you expect to see the vGPU models? depending on the model, you have to activate sr-iov for the card and use the virtual functions, see https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE for a detailed guide what does lspci show on the host...

no that's the right command, but there is no indication what might be wrong check the status of the pvestatd daemon with: systemctl status pvestatd journalctl -b -u pvestatd the first command shows the current status and the second should print the logs of pvestatd since the last boot of...

this usually happens if the 'pvestatd' daemon hangs or crashed. The most common cause for this is a hanging or not working nfs mount. I'd check the journal/syslog of the host for errors/warnings

ok this is fully intended (and works here) there is a 'spiceproxy' running on each node that forwards the connection to the correct one, reasoning is this: if you connect to the webui of x.y.z.1 you have a working connection to that node (not necessarily to the others) if you now open the...

not sure if you mean this, but you can already host the pdm instance on a pve cluster with ha enabled. that way the pdm instance should always be reachable

i meant from the host while the vm is trying to start

did anything else change in your system/environment? these lines: are only warnings. The behavior is the same as before but now we print these warnings, so i doubt this is the actual cause is there anything in the syslog/journal?

sorry, but the whole post does not make sense to me neither these commits, nor the links exist this is wrong, this does not exist on debian 12 (nor anywhere else AFAICS) this option (vfio-display) does not exist in qemus configure script (and never did) This whole post smells like it's...

hi, can you explain more on where you got this information? i could not find any info on this, not in the source or anywhere else the flag does not seem to exist (google search only lead me to this thread again) and the output of is empty on a fresh debian 12 install also i could not find...

it would be interesting what the exact api call is with all parameters, otherwise it's hard to say what exactly is wrong here