Search results

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.

you need to do that manually per tmpfs instance inside the container. tmpfs has no notion of cgroups unfortunately.

if "tar" segfaults, that would indicate either memory or disk problems usually.. maybe try installing "debsums" and running "debsums -c", and run SMART and memtest (note that absence of failure in those tests doesn't mean there is no HW issue, it just means none was detected!)

the next time a migration hangs with these symptoms, could you please collect ss -tim 'dport 22' on the source and ss -tim 'sport 22' on the target node, before canceling the migration? thanks a lot!

each package comes with its own changelog, which you can also view on the Updates UI.

und wie genau auessert sich das nicht booten? in dem log bootet die maschine naemlich und startet auch nen haufen gaeste.. einzig fehler im bezug auf ssd, sowie ein haufen warnings wegen docker in LXC sind zu sehen..

that sounds like you are booting from an old ESP maybe? did you previously have PVE installed on a different disk that is still in the system?

no. but it has been reviewed upstream, so I think we can pull in the fix in our Qemu build now!

welche netzwerkkarte ist denn verbaut? wenn du schreibst sie hat nicht (sauber) gebootet, was genau meinst du damit? kannst du bitte von einem dieser boots das journal posten? danke!

yes. restore and create share a common API endpoint, and in this case, --password is currently only handled for create. it should either error out or be supported when set via restore.