Search results

Hi, sorry yes. It seems the way we parse does not match the output you posted, which is very probably related to this version would you mind opening a bug on https://bugzilla.proxmox.com/ with the smarctl output posted from above and additionally the output of smartctl -H -A -f brief...

Just fyi: i just sent a patch to silence those (informational) perl warnings: https://lore.proxmox.com/pve-devel/20250519144357.3515197-1-d.csapak@proxmox.com/T/#u as for your migration speed problem, even if you have much free memory, it might be heavily fragmented which can impact allocating...

please don't simply bump without new information, this will not make answering any faster... that said, what kernel version do you currently use? this sounds like an issue that more recent bios+efi versions brought in and should be mostly fixed in current kernels, so a current 'pveversion -v'...

as I said, proxmox ve does not modify the disk contents. If the guest os changed some config after migration, you have to investigate inside the guest to find out why the config is not carried over

Hi, can you post your vm config and output of `lspci` (and mapping config, if any) ? this would mean that the pci device under that path does not exist

HI, if i understand you correctly, you ask if we'll integrate a vm console directly in the datacenter manager? Yes this is something we're wanting to do. why do you believe that? Are there better (open-source) alternatives available (that I don't know of) ? not really sure what you're trying...

hi, can post the complete task log output from a failed start and maybe from a restart too? also the output of e.g. lspci nvidia-smi vgpu nvidia-smi vgpu -s nvidia-smi vgpu -c would be helpful

Hi, how did you migrate? the disk contents (and thus the internal guest configuration) is not touched normally

hi, no by default we filter some things out in the 'raw device' view to not clutter it too much. I can see that such ai processors would be handy to have also in that view, so if you can post the output of lspci -nn the we can check if we can easily add it too to work around it, you can set...

Hi, the actual command we use to parse out the data is smartctl -H -A -f brief /dev/sda could you maybe run that command and post it's output here? also, do you see any error in the journal/syslog on the host while you're trying to display the smart values on the gui?

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...