Search results

is this a cluster? this sounds like that one of the nodes is on a newer version that includes the gui changes but you have a vm on a node selected where that api parameter is not there yet. can you check (and post) the output of 'pveversion -v' on all nodes ? if it's not a cluster, are you in...

yes, you simply have to use the output of zfs list instead of zpool list

ah ok sorry, the output wasn't actually necessary to see the issue^^ when you look at your config, you can see that the zpool01 entry does not have the 'sparse 1' option, so the space for each vm volume is reserved upfront: so while the vm disk reserves the space from the point of view of...

so we take the info from 'zfs list' which shows: which shows ~82% used (USED/(USED+AVAIL)) ok, one additional command output would be helpful to see the geometry of the zpool (which might explain the big difference in output) zpool status

can you post the full output of dmesg? that may reveal some more information what is happening here

mhmm to find that out, could you please post the output of zpool list zfs list cat /etc/pve/storage.cfg

this signal (11) is a "SIGSEGV" which means there was a segmentation fault somewhere. I'd guess it's either some corrupted file (you could check this with the 'debsums' package+command) or faulty hardware (like e.g. faulty memory) since it happened after an upgrade i'd assume the first option

setting the '+i' (immutable) flag is only a further protecting layer. It's set to prevent accidental modification of template base file (since it could have linked clones). everything should continue to work even without that flag, but now an admin could modify that image without first removing...

i agree it's not optimal. If you have a (in the best case concrete) improvement suggestion, please open an enhancement request on https://bugzilla.proxmox.com . that way we can better keep track of these requests :)

this is meant as a bar over time (left is older, right is newer) where the color indicates the usage (100% red, 0% green). I agree it's not the best visualization, but nothing better did come up yet. e.g. see the example screenshot in the docs...

mhmm? not sure i get what you mean. which documentation is "behind fake walled gardens" ? every piece of the software and docs are out in the open. Yes, we don't have any detailed guide ourselves on e.g. how you to run jellyfin with a gpu, because there is already the guide i linked to?

this seems suspicious, can you post the /etc/network/interfaces of the host that returns that?

there are no artifical limits in pdm itself, so the only limit is what the system can give. mostly this is * network latency/throughput (e.g. for remotes with many vms updating the metrics, etc. can be quite large) * memory: from what i can remember a single resource with metrics (e.g. a...

while migration tasks should show on the pdm, i can confirm that the maintenance status of nodes is currently not shown on PDM Would you mind opening a feature request/bug on https://bugzilla.proxmox.com/ ?

sadly that path alone does not really say where it comes from or anything else. can you see which device (e.g. pci id) id belongs to? what does it show? you can print it by doing, e.g. cat /sys/class/hwmon/hwmon1/temp1_input

yes, it should be the same as passing through any other gpu note that passing through integrated gpus is a bit more complicated usually, and not as well supported as passing through "proper" pci devices.

how does your remote config on the pdm look like? is it possible that the nodename <-> ip address mapping is wrong there? (that would explain it)

i guess sometimes the sensors that are available in linux via drivers/etc are not the same that are available via the ipmi so it might be a different sensor. do you know how beszel retrieves the sensor info? if the package 'lm-sensors' is installed, you could post the output of 'sensors' here...

well, sr-iov is the 'pci standard' way to do multiple vgpus on a single pci card. nvidia takes a slightly different approach (you have to "activate" a profile on the virtual function and need a specialized driver) for normal passthrough, nothing is changing here, so if you're not interested in...

nur um ein bisschen Klarheit zu schaffen (die Doku page kann man hier sicher noch verbessern!): grundsätzlich sind die angegebenen Versionen miteinander kompatibel weil explizit getestet, bzw. beim expliziten durchtesten von neuen NVIDIA Treiber Versionen kamen diese Versionen zum Einsatz...