Search results

Another VM on this host hangs for a few moments when starting the backup but doesn't go to read only: May 22 05:12:35 vps1 kernel: [442137.812027] INFO: rcu_sched detected stalls on CPUs/tasks: May 22 05:12:35 vps1 kernel: [442137.812171] 0-...: (1 GPs behind) idle=a73/2/0...

We are experiencing this with more vm's on this node now. Some extra info: All VM's use local directory storage with raw as disk format. The problem occured when we upgraded to Proxmox 6.2. The VM's are not using the qemu-agent. Not all vm's on this node have this problem. pveversion -v...

We upgraded one of our nodes to the latest Proxmox version (pve-manager/6.2-4/9824574a (running kernel: 5.4.34-1-pve)) and now we encounter an issue during backup of one specific VM (Linux guest). The backup starts: INFO: Starting Backup of VM 123 (qemu) INFO: Backup started at 2020-05-19...

Thanks! Then we'll add a new disk and won't shrink the lvm-thin volume.

We are using a local backup for all our Proxmox nodes and with a hook script we scp the backup to an external backupserver. Now we have one node which uses lvmthin as storage for the VM images. To make a local backup we need a local backup storage because we can't backup to a lvmthin storage...

Thanks @BloodyIron! We still have the same problem but we can fix it by starting the VM without the ,+kvm_pv_unhalt option. What do you mean by kernel version pinning? We are using kernel 4.4.49-1-pve at the moment.

Sure :) args: -vnc 127.0.0.1:853,password boot: cdn bootdisk: virtio0 cores: 4 ide2: local:iso/gparted-live-0.20.0-2-i486.iso,media=cdrom,size=219M kvm: 1 memory: 16384 name: mta2.hix.nl net0: e1000=3A:AB:CA:4B:A0:39,bridge=vmbr0,firewall=1 net1: e1000=5A:C9:47:94:64:CA,bridge=vmbr1 onboot: 1...

Here's the output: proxmox-ve: 4.4-86 (running kernel: 4.4.49-1-pve) pve-manager: 4.4-13 (running version: 4.4-13/7ea56165) pve-kernel-4.2.2-1-pve: 4.2.2-16 pve-kernel-4.4.19-1-pve: 4.4.19-66 pve-kernel-4.4.49-1-pve: 4.4.49-86 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-2~pve4+1 libqb0: 1.0.1-1...

We encounter the same problem on several Proxmox 4.4 servers with kernel 4.4.49-1-pve. The same VM's keep crashing and on the host you can find the following data in dmesg: [ 326.151126] WARNING: CPU: 1 PID: 2865 at arch/x86/kvm/emulate.c:5581 x86_emulate_insn+0xbb2/0xe30 [kvm]() [...

Converting to raw did fix our problems. You can convert live by selecting 'move disk'.

We still have this problem, with Intel network cards. Looks like changing the disk image format to raw fixes the problem :confused:

Everyone has access to all the data backupped to this service. Are you aware of that? So, do not use this service.

We have the same problem with a few VM's on Proxmox 3.4. We are using local storage on an Areca-RAID-set. We are also using backup to NFS and the 'blocked for more than 120 seconds' problems occur mostly during a backup. However, we did have some problems with a few VM's when there was no backup...