Recent content by reto

I've seen the same for my PBS running in a VM hosted on a Synology NAS. the gabarge-collection ttimes for a large dataset went up from 1-2h to 6-12h during the update from 3.2 to 3.3. Now with 4.0 it looks like the times went back down to sub 2h -> maybe other affected users can test the...

FYI; here some recent experience with PVE running ZFS Solution: ZFS Pool was full Symptoms: All VMs froze, reboot didn't help, shutdown stuck kernel log: Buffer I/O error on dev zd224, logical block 0, lost async page write zd224 pointed to cloud init device, error got only printed for them...

The following ansible role snippet works for Ubuntu 24.04 - name: Add pbs repo deb822_repository: name: pbs types: deb uris: http://download.proxmox.com/debian/pbs-client suites: bookworm components: - main signed_by: |- -----BEGIN PGP PUBLIC KEY...

Situation: This weekend I installed TrueNas for some tests in proxmox vm and attached a 1 TB disk to the VM. Unfortunately I forgot to disable backups on this disk and my nightly backup2pbs job filled up the storage a few hours later. At the same time, as the backup crashed, the Guest VM...

@fweber FYI, I just had the same issue, a restore task was running but was not visible in the GUI. Thank you for these instructions, I was able to check the state no visible via API root@mercury:/var/log/pve/tasks# pvesh ls /nodes/mercury/tasks | grep restore root@mercury:/var/log/pve/tasks#...

@fabian this is still very frustrating Again today I tried to install the pbs client on ubuntu 22.04. Now more than 1.5 y after the release and i still needs googeling to get it running.

some more notes to get all vmids # pvesh get /cluster/resources --type vm --output-format json | jq '.[] .vmid' -r or name and vmid as a TSV # pvesh get /cluster/resources --type vm --output-format json | jq '.[] | [.vmid, .name] | @tsv' -r 9001 ubuntu2204-templ

Ubuntu 22.04 has been out for 7 months now, this dependency is quite annoying. Would it be difficult to provide client packages for Ubuntu?

@fabian it happened again, this time after restarting some vms on the node. I think I will just remove cloud-init after the initial boot, this is too annyoing.

@fabian i've installed 7.1, set everything up, did the upgrade to pve 7.2 (plus/minus as yesterday) and did a reboot. But no luck, no host key regeneration... Very strange, but at this point I just wait for it to happen again (or you have more affected users). But thanks anyway!

@fabian all my ubuntu 22.04 and 20.04 vms were affected, but not my single debian host

@fabian sorry, yes, the link to the other issue is probably misleading (it was late) and yes, I tried both restarting the host AND the guest, and in both cases the ssh key was NOT regenerated. So the issue it self seems to be 'solved', but I'm really wondering what caused it.

@fabian Ive extended my answer, I can provide more logs if you like

@fabian nope, just the VMs have cloud-init installed. # on one of the vms ii cloud-init 22.1-14-g2e17a0d6-0ubuntu1~22.04.5 all initialization and customization tool for cloud instances # on the host un cloud-init <none> <none> (no description available)...

@Docop2 do you use a cloud-init image? Today cloud-init was run on all my vms and all ssh host keys were regenerated (https://forum.proxmox.com/threads/warning-remote-host-identification-has-changed.110186/). Just an idea, but maybe your interfaces got reconfigured due to the same issue? I'