Search results

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

Hi, thanks for the feedback. Can you give an example of what you mean exactly? (E.g. a comparison video ?) What kind of activity did you test? there are no real configuration knobs for either spice or vnc really. In my experience, using some guest controlled remote software (like rdp for...

what do you mean by this exactly? the timeframe specifies from which timeframe the data is returned that we have... also 'hour' and 'day' is both supported since a long time

Hi, first, if you think you found a security issue, please report according to https://pve.proxmox.com/wiki/Security_Reporting so it can go through the proper channels second, as @EllerholdAG already mentioned, it seems there is no cookie injection at all we return a 500 error with no explicit...

just give a bit of background: we use fixed pci addresses for devices managed with our config so that we don't run into problems with live migration, since for that the hardware layout must be identical on the source and the target and since qemu dynamically assigns pci slots/ports when adding...

this is just the maximum, we query the drive in regular intervals, and as soon as it's done, we continue (we won't wait the full 2 hours every time)

hi, maybe there is also a bios setting for the bar size? e.g. somebody here solved it with such a setting: https://forum.proxmox.com/threads/pcie-passtrough-problems-msix-pba-outside-of-specified-bar.140573/

yes, that also our experience, don't forget to update the guest drivers afterwards

great to hear that it works! glad to help and bring pbs/pve to more people ;) (i guess you won't be the only one that requires FIPS compliant backups) as for the import/export slot loading, it could be done, but as you said it's a separate issue (a bug report would help to triage and track...

note that this is only a warning, and this behavior did not change, it was just silent in the past, now we log that it did not work. Whatever happens with your pass-through, it probably has nothing to do with this warning

for your info: i sent a patch to increase the timeout if we detect calibrating: https://lore.proxmox.com/pbs-devel/20250415114043.2389789-1-d.csapak@proxmox.com/ but it could be a while before this lands in any repository, so for now it's still recommended to initialize beforehand with your...