Search results

I mean "pct config XXX", where XXX is the container's ID

please post the config(s) nevertheless..

could you post the config of the affected container?

it does sound like the error is coming from the storage, maybe it doesn't like renaming the file while it's still being flushed? hard to say from the distance.. if you have the space, you might try switching the backup target to a local disk and see if the problem disappears then..

I don't think this is exposed yet via the CLI, feel free to file an enhancement request in our bugzilla!

could you file an issue in our bugzilla? please include "pveversion -v", the config and the task log! this should be possible to fix.. recreating the TPM state is an option, but it will possibly require recovering bitlocker inside the VM using recovery codes, so it is a bit dangerous.

well it is already - if you want to test the fix, upgrade to the fixed version (the diff between -4 and -5 is only that fix).

klingt nach nem plan. etwaige fehler im journal waeren auch interessant!

there are multiple issues, the io_uring is only fixed in 10.1.2-5 which is currently on pve-test

what kind of storage are you using? anything visible in the system logs when it fails?

yes, in this case you need to either create new pools, setup ACLs and then move guests and storages over (safe variant), or carefully edit user.cfg and jobs.cfg (unsafe, but quicker variant).

please open an issue in our bugzilla! thanks

There is an API that backup providers can use to integrate backup and restore into PVE. It is also possible to import disk images in various formats, but then you need to create the guest configuration yourself.

there will be an announcement once packages are available for testing ;)

bitte schick mal "zfs get all rpool/data/subvol-103-disk-0" (falls du ein nicht standard ZFS setup hast, dataset entsprechend anpassen).

could you try with the 6.14 kernel as well, and then open a bugzilla entry with the results (working/broken kernel version and full "journalctl -b" for both would be great!)

we've so far had one instance that might indicate that PVE could potentially also trigger a TCP connection stall, but haven't had any further reports or confirmation. if you see behaviour that indicates you can trigger the problematic behaviour, please open a new thread and include relevant...

okay, das klingt nach einem problem im initrd stadium. gibt es irgendwelche fehlermeldungen am bildschirm? landest du in einer "shell" wenn das system nicht booted?

a 6.17.4-2 kernel is now also available on pve-test and pbs-test - it is identical to the last test kernel mentioned above by chris, except for the changelog and kernel name (-test vs regular build). if you are already on the 6.17.4-test-2 kernel you don't need to boot into this one, if you are...

https://bugzilla.proxmox.com/show_bug.cgi?id=4379 planned, but not yet implemented.