Search results

es gibt aktuell einen bug im 6.17er kernel der manche PBS setups betrifft und aehnliche symptome hat: https://forum.proxmox.com/threads/super-slow-timeout-and-vm-stuck-while-backing-up-after-updated-to-pve-9-1-1-and-pbs-4-0-20.176444/page-9#post-823736 falls du auf PBS seite schon auf 4.1 mit...

we will fix it. but if you provide the full chain, then you don't need a fingerprint. if you use a fingerprint, you don't need the full chain.

that is tracked in https://bugzilla.proxmox.com/show_bug.cgi?id=6195

falls du kein ZFS verwendest, koenntest du das ganze mit einem stock 6.17 kernel von https://kernel.ubuntu.com/mainline/v6.17/amd64/ reproduzieren und dann einen bug report im kernel bugzilla aufmachen? falls du es dir antun willst/kannst gerne auch gleich die versionen davor zurueckgehen bis es...

that depends what kind of actions you want to do over PDM. you can give it audit access only, then it will only be able to see things but not change them. if you want to start/stop/.. guests, you need to give it power management privileges on those guests. for migration, you need to give it...

could you please post: - VM config - migration task log - VM start task log on the target node (if one exists) - journalctl for both source and target node covering the full duration of the attempted migration and 2mins before and after

this is a bug in1.0.0, please update to 1.0.1 (via no-subscription). @FloRe could you try restarting "pdm-daily-update-service"? if it still doesn't work afterwards, please open an enterprise support ticket (you can provide sensitive config data there)

do you meet the requirements for PDM enterprise repo access? https://pdm.proxmox.com/docs/faq.html#is-there-a-dedicated-subscription-for-the-proxmox-datacenter-manager

eventuell hilft auch ein system firmware update, falls es eins gibt..

if there are no further traces than this means that the migration didn't even start..

die meldungen gehen wahrscheinlich mit "acpi=off" in der kernel commandline weg (allerdings disabled dass auch einige power management features des kernels). https://github.com/acpica/acpica/commit/53fc0220 koennte related sein, dann sollte eines der naechsten kernel updates das problem beheben..

the logs are maybe incomplete or of the wrong nodes? please limit them to the relevant timespan and also indicate when the problem happened..

yes, these are the commands that PVE also uses for the file restore UI, for VM backups they spawn a small recovery VM in the background that gives access to the directory tree and contents, if possible.

you can only export those backups using "proxmox-backup-debug", which has a flag to replace corrupt chunks with zero bytes. you can then import the raw disk extracted that way using "qm disk import", or recover your data via other means.

no, because the two nodes are not in a cluster, thus there is no knowledge about the storage being shared. even worse, giving access to the same storage to two clusters (or standalone nodes) without any sort of separation/namespacing/.. is really really dangerous, since both PVE systems will...

it will convert on the fly.. please provide more details about your storage and a full task log.

yes, there are plans for this. PDM 1.0.0 has node shell access using xterm.js, we plan to extend this to support noVNC and spice as well to allow guest terminal access as well. with xterm.js, it would be limited to containers and VMs with serial console, we wanted to support the full range from...

https://pve.proxmox.com/wiki/Proxmox_VE_API has some pointers to existing API clients, PVE/PBS/PDM mostly work the same modulo cookie / auth header names/formats.

yes, guests using root-only features cannot be migrated to another cluster at the moment, because the remote migration uses a token that cannot have full root privileges. see https://bugzilla.proxmox.com/show_bug.cgi?id=2582 and https://bugzilla.proxmox.com/show_bug.cgi?id=6213

im sekundentakt klingt seltsam, normalerweise werden solche ACPI issue einmal am anfang des boots gelogged.. text ist immer gleich?