Search results

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.

the password is only handled when creating a new container, but this could also be extended to work when restoring. could you file an issue in our bugzilla? https://bugzilla.proxmox.com/show_bug.cgi?id=7158 is tangentially related..

understood. if you do run into this issue more often, I would recommend switching to 6.14 - please report back if the problem goes away then! so far we've only had reports of the issue triggering with PBS connections.

das ist ja schonmal gut! die fehlermeldung klingt tatsaechlich nach einem einfachen verbindungsabbruch.. wieviel platz hast du denn auf PBS seite? eventuell kannst du dort lokal restoren und anderweitig transferieren, falls das netzwerk problem sich nicht loesen laesst..

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

die fehlermeldung besagt nur dass das enterprise repository konfiguriert ist, aber keine subscription aktiv. siehe doku ;)

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

bitte repositories einschalten, "apt update" machen und den output hier posten (in code tags)

wie vermutet - du hast die Debian repositories disabled.. bitte die doku lesen!