Search results

Well, not really, at least for me. On a 7.1-12 PVE cluster, 3 nodes, full flash ceph storage. 3 VMs. Windows 2019 VMs. Exactely the same, excepted saize of data disk. 2 of them have never had a problem during backup. Third one has same issue (backup mode = snapshot), nealy 2 days on 3... Same...

Hi, Same problem here. It seems rebooting every node after a kernel upgrade solves or at least mitigates the problem. Not clearly, from my point of view… Christophe.

No, in a cluster environment, you can have, on one node, a VM with "start/shutdown order" set to "10" starting BEFORE a VM on another node with a "start/shutdown order" set to "2". This is NOT what we need. Christophe.

Hi, This an important feature request, a cluster wide "start at boot" and "startup / suthdonw order". Any hope on such a feature? A global restart of cluster becomes easier and straightforward. Thanks, Christophe.

Thanks for your reply. We are here massively using Firefox 78.11.0esr, may be it's a web browser problem. Will try again with a chromium based browser. Christophe.

Hi all, (Thanks again and again proxmox team PVE and now PBS are really great and unique products.) When looking at task history of a given VM, or "tasks" panel at the bottom of a PVE window, if ONE guy forget to close a console window, then a line appear each 15 minutes. Is it possible to...

Yep, seems better now : INFO: starting new backup job: vzdump 31107 --mode snapshot --storage Backup-pbs-r --remove 0 --node px2 INFO: Starting Backup of VM 31107 (qemu) INFO: Backup started at 2021-09-16 10:09:48 INFO: status = running INFO: VM Name: *****-s-st4***7 INFO: include disk 'scsi0'...

A new bakup is in progress, so looking at the logs from PBS side. Errors are arising since sept. 6 : 2021-09-06T21:29:03+02:00: starting new backup on datastore 'data': "vm/31107/2021-09-06T19:28:53Z" 2021-09-06T21:29:03+02:00: download 'index.json.blob' from previous backup...

My bad : neither restart, nor move... Doing a live migration now... Tank you, Christophe.

And a move disk fails in a similar manner : create full clone of drive scsi0 (Disques-VMs-2:31107/vm-31107-disk-0.raw) Wiping dos signature on /dev/Disques-VMs-1/vm-31107-disk-0. Logical volume "vm-31107-disk-0" created. drive mirror is starting for drive-scsi0 drive-scsi0: transferred...

Hi, Problem occured one more after a "backup now", and again last night with a scheduled backup : INFO: Starting Backup of VM 31107 (qemu) INFO: Backup started at 2021-09-15 22:23:12 INFO: status = running INFO: VM Name: *****-s-st4***7 INFO: include disk 'scsi0'...

Sure. Upgrade done, new backup in progress... Christophe.

Here : [root@px1:~]# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.4.78-2-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-5.11: 7.0-6 pve-kernel-helper: 7.0-6 pve-kernel-5.4: 6.4-5 pve-kernel-5.11.22-3-pve: 5.11.22-7 pve-kernel-5.4.128-1-pve: 5.4.128-2...

Hi, Before a storage rebuild, I launched backups manually. PVE 7.0-11, PBS 2.0-9. A VM with 2 disks. Got this : INFO: starting new backup job: vzdump 31107 --storage Backup-pbs-r --remove 0 --mode snapshot --node px1 INFO: Starting Backup of VM 31107 (qemu) INFO: Backup started at 2021-09-15...

Sorry, ignore my question : RTFM!! https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_virtual_machines_settings, chapter 10.2.15. Christophe.

Hi, And for VMs WITHOUT "order" field, do they start after any VM with an "order"? (I would like to avoid specifying VM3 order and VM4 order in the previous example, I only care VM1 and VM2 starting first) Thank you, Christophe.

Yes, it was running for some weeks, then we updated PVE stack, and suffered from lastest qemu PCI changes (https://forum.proxmox.com/threads/warning-latest-patch-just-broke-all-my-windows-vms-6-3-4-patch-inside.84915/) so we installed intermediary pve-qemu-kvm...

[root@px3-c:~]# pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-7 pve-kernel-helper: 6.3-7 pve-kernel-5.4.103-1-pve: 5.4.103-1 pve-kernel-5.4.101-1-pve: 5.4.101-1 pve-kernel-5.4.98-1-pve: 5.4.98-1...

Hi, Strange behaviour here (pve 6.3-6, pbs 1.0-9) where a virtual machine crashed (no console, no ping, no guest agent, no more CPU, disk or network graph, but RAM usage graph flat) but reported alive by PVE gui) at 21h22, 38s, a few seconds before first error message from PBS. This VM are not...

Hi, you don’t need pbs to do that if i understand. You need a cluster, and a shared storage. you could setup HA, and a node failure will trigger vm start on another note. Christophe.