Search results

Hi guys, i have a single debian with guest-agent, running as a VM on a 3 node-cluster (each node has 2 OSD's building the ceph-cluster (rpool1)). When i tried to online-migrate the VM i got (you'll notice later that the disk does not lay on the local-storage but on the ceph (pool1), and this...

Yes, we normally run kvm64 and switched to host but the problem persists with host type enabled.

Nothing special in the logs on both sides. We have this on different hosts, with different Win11 machines (But only Win11). CPU History is looking like this (Drops in load are while and after restart):

has already been updated to win11.

Hi everyone, we have multiple Windows 11 VMs on different PVE's with sometime 100% CPU load after hours of inactivity. The only solution to return to normal CPU load is to restart the VM. Any ideas or improvements recommendations? VM Config: root@pve:~# qm config 905 agent: 1 balloon: 0 bios...

Hi Guys, i have a question related to updates on PBS, i have one (Main) PBS with an Enterprise Repo and a (Slave) with the No-Subscription Repo, the datastore is fully synced to the slave (sync-job initiated via slave). I guess it's not recommended to have these differences on the repos when...

Problem und Lösung: Hier fehlte der Mountpoint für rpool /rpool. # mount [...] rpool/ROOT/pbs-1 on / type zfs (rw,relatime,xattr,noacl) [...] rpool on / type zfs (rw,noatime,xattr,noacl) # zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 7.46T 24.1T 163K /...

Ja das ist ausgeschlossen.

Der PBS ist eine baremetal Installation. Das root FS ist ZFS. Ein weiterer PBS synct sich den Datastore. Der betroffene PBS hat auch eine aktive Basic Subscription, vielleicht gehe ich den Weg des Support-Tickets.

Here you go.

Output attached due to length.

Meine Datei sieht korrekt aus: root@server:~# cat /usr/lib/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support"...

Ich habe alle Updates eingespielt und bin demnach auf der neusten Version 2.1-5 : root@server:~# proxmox-backup-manager versions --verbose proxmox-backup 2.1-1 running kernel: 5.13.19-5-pve proxmox-backup-server 2.1.5-1 running version: 2.1.5 pve-kernel-helper...

Der PBS ist eine bare-metal Installation und das Problem besteht erst seit Upgrade von Buster auf Bullseye.

Erledigt, wieder ohne Änderung.

root@server:~# proxmox-backup-manager versions --verbose proxmox-backup 2.1-1 running kernel: 5.11.22-5-pve proxmox-backup-server 2.1.5-1 running version: 2.0.10 pve-kernel-5.11 7.0-10 pve-kernel-helper 7.1-12 pve-kernel-5.11.22-5-pve 5.11.22-10...

Hallo Dominik, leider ohne Erfolg.

Hallo Zusammen, ich habe nach einem PBS Upgrade von Buster auf Bullseye das Problem, dass ich beim aufrufen des Repository Tabs, 400 - Bad Request erhalte. Updates können ohne Probleme weiterhin via CLI durchgeführt werden. root@server:~# proxmox-backup-manager versions...

hey dietmar, thank you, solved it by changing backup mode from snapshot to stop because container is running on raw format. Best Regards,

Hey Guys, i have a fresh PVE 6.3-6 installed and can't backup my Container through the Backup Job. When turning off the Container and run the Backup Job, it works. The Storage is a PBS 1.0-1 and encryption is enabled. log from backup-job: INFO: starting new backup job: vzdump --quiet 1...