does it also crash with a current version? e.g. currently there should be 156 in the arch repos: https://archlinux.org/packages/extra/x86_64/firefox/ ?
do you have any extensions etc installed? if yes, could you try in private mode?
looks weird, we request 262144 byte but only get 10240 back...
is there some transfer size limit on the lio side maybe?
EDIT: did you format the tape beforehand? (this is necessary for labeling)
yep seems like it:
says : 'ExpXferLen: 16' so 'expected transfer len 16' which would match our code before the patch
and then
which is exactly that ITT
in the meantime the package was bumped (should be included in proxmox-backup-server...
IMO the ui looks nice and i get why this is a feature that some want. but there is currently a big caveat: for each pbs snapshot that is mounted there will be an extra helper vm that consumes memory and cpu resources. these will be auto cleanup...
ok reading the errors from the target side, it seems this is an issue in our code that was recentyl fixed:
https://lore.proxmox.com/pbs-devel/20260817123128.2813924-1-d.csapak@proxmox.com/T/#t
the patch is applied, but not yet in a bumped...
aside from using the tape drive/changers via iscsi there is no other possibility at the moment. we only do datastore-> tape backup, not direct to tape, nor can we 'mount' a foreign pbs datatstore (e.g. for locking reasons)
using it via iscsi...
Hi,
not sure what is happening, but we'll hopefully find out :)
no manually adding will not help since the labeling also includes writing the first block to the tape (our 'media' header)
can you post the output of dmesg after a failed (manual)...
mhmm can you try to open a `journalctl -f` or `dmesg -w` on the host while trying to boot the vm so you can see the messages live when it starts to hang (could also work over ssh, but directly on the machine would be best) maybe there can be seen...
usb hotplug is implemented since quite a while..
if it does not work for you, can you post your vm config (qm config ID) and versions (pveversion -v) ?
Hi Everyone,
Every few months someone asks some version of "why can't I use LVM-thin on my shared SAN LUN?" Thick LVM works fine as shared storage, but has no native snapshots. LVM-thin has snapshots but is local-only... it's natural to wonder...
it's a bit of a narrow use case IMO, but at least worth discussing. would you mind opening a feature request on our bugtracker (https://bugzilla.proxmox.com) ? there we can track it better and other devs can also chime in
do you have a working ipv6 connection? it seems apt resolves the ip to ipv6 and tries with that, but it says that this is unreachable.
maybe because your client does not try to use ipv6?
does 'lspci -nnk' after a reboot show 'vfio-pci' as a driver? if not you might need to order vfio-pci before ahci fot it to work
excerpt from our docs:
https://pve.proxmox.com/wiki/PCI(e)_Passthrough
so in your case there should be a file...
Recent security findings and fixes in Ceph make it necessary to upgrade ceph and migrate authentication keys from the aes to the aes256k cipher. This is to address weaknesses in the old Cephx authentication method, especially if your Ceph service...
hi,
i hope you did disable the vgpu frame limiter? (https://docs.nvidia.com/vgpu/20.0/grid-vgpu-user-guide/installing-configuring-grid-vgpu.html#setting-vgpu-plugin-parameters-on-red-hat-el-kvm ) this is currently not possible with PVE...
We are pleased to share two major milestones that will help us better serve our customers and partners worldwide.
Global 24/7 enterprise support
Starting October 19, 2026, Proxmox Enterprise Support will be available around the clock, 365 days a...
from another post from me:
https://forum.proxmox.com/threads/on-limitations-and-maximums.179850/#post-834673
so currently there is a memory requirement of ~1MiB per resource + some overhead for the base system
there is also the disk space...
correct, the token does not use/inherit the users tfa. in fact, tokens can't have a second factor at all.
This kind of use case is exactly why tokens exist in the first place to give access to users resources in an automated fashion that can be...
note that historic rrd/task data (etc.) will not be migrated over, so you might loose some rrd/task history (though i'm not sure if it's safe to just simply rename those folder/filenames too, they would be in /varlib/proxmox-datacenter-manager/ )