Search results

Yes. It is not a Beta any more. Running production quite a while now. But you can still order the free 150GB version. Just go to https://www.tuxis.nl/en/proxmox-backup-server/ and click on: Create an account. Choose the free 150GB version.

It might work, it might not work. That's as clear as it might get with a host-cpu. IIRC it also depends on the instructions a VM uses (or starts using after migration). If the original CPU supports it, and the to-migrated-to CPU doesn't, you're screwed as well.

INFO: 5% (3.0 GiB of 60.0 GiB) in 20s, read: 160.0 MiB/s, write: 158.7 MiB/s Tadaaaa.wav

/usr/bin/kvm \ -id 146 \ -name 'XXX,debug-threads=on' \ -no-shutdown \ -chardev 'socket,id=qmp,path=/var/run/qemu-server/146.qmp,server=on,wait=off' \ -mon 'chardev=qmp,mode=control' \ -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' \ -mon...

When I put $drive in the exit line: ERROR: on...

I get: ERROR: attaching TPM drive failed - drive_add: string expected ERROR: Try "help drive_add" for more information INFO: aborting backup job

Sure: agent: 1 bios: ovmf boot: order=scsi0;ide2;net0 cores: 4 efidisk0: ceph02:vm-146-disk-0,efitype=4m,pre-enrolled-keys=1,size=528K ide2: none,media=cdrom machine: pc-q35-6.2 memory: 8192 meta: creation-qemu=6.2.0,ctime=1657723669 name: XYZ net0...

Not sure if this should be in PVE or PBS, but I installed a new Windows server with all bells and whistles, and I am unable to backup the guest: INFO: starting new backup job: vzdump 146 --remove 0 --notes-template '{{guestname}}' --node proxmox2-6 --mode snapshot --storage pbs_extra INFO...

Hehe, we understand you can't guarantee any Windows success. :)

Ergo, it pretty safe to assume this issue is fixed if we start upgrading next week?

Still valid, i guess i overlooked your e-mail. You should have a e-mail in ~5min.

Ok, so now the question: Did Ubuntu upgrade four days ago or did Proxmox? :)

Is it running (proxmox) backups by any chance? Any other VM's on that node that suffer from issues?

Please post the full config of the VM. The 25% CPU usage is 'normal' on a crash. You probably have 4 cpu's configured, upon crashing, one vCPU is using 100%. Do you get something on the console when you keep it open, waiting for it to crash?

I just upgraded pbs003 to 2.2.5-1 (from no-sub) and rebooted the box. @apollo13, are you on that one?

I think it's just not possible, other than the dummy VM option. I created a feature request for it: https://bugzilla.proxmox.com/show_bug.cgi?id=4166

Hi, I have a user that is restricted to a pool. The user wants to restore a backup, but is not able to select a pool where the vm needs to be created in. How can the user restore into a pool? I can only think if 'create a dummy vm in a pool, and overwrite it', but I think the vmid needs to be...

I think I located the issue: https://lists.proxmox.com/pipermail/pbs-devel/2022-July/005332.html Proxmox is looking into it, I assume.

I tend to agree with this. We have not upgraded customer cluster only because of this bug. Also not complaining that the bug exists, but I now get customers asking why we haven't upgraded yet since they see a notification in the GUI. :)

> Well you tickled it well enough. I am now getting routed via nextlayer in vienna. That's what we hoped :). > Is that change persistent (or can you keep it persistent) or will the router loose it again once it stops laughing? > Is there anything I could do on my end to improve this (talk to...