Search results

n5105. 5.15.64-1: pbs vm(with same latest kernel) and debian vm(cloud kernel 5.10.0-19) up for 7 days, still ok. these 2 vms up for 5 days with previous 5.15.60-2, until I upgrade kernel and reboot host. with 5.15.60-1 above VMs will hang up in 1 day.

get it. thanks. it's me missed the wiki detail.

no retention policy in pve/storage or pbs/storage. only setup retention in backup jobs. today notice job with keep 3 months will only keep the last one (previous one will be removed). then test 90 days, same behavior. now change to keep last xxx backup count, this option is horned by pbs. also...

pbs stores backup as "chunk" files, backups will process as incremental. just setup verify job and keep x backups.

just tested today, failed to restore whole pve host. (seems it's because this feature is not ready yet.) fyi: 1) login to pbs store proxmox-backup-client login --repository pbs-host:store-name <enter password> 2) specify pbs repo info to bashrc. export PBS_REPOSITORY=pbs-host:store-name 3) to...

Edge 5.19.8-1

this time, freezed within 24 hours, while the guest freezed, the traffic is about 900KB/s in and out. cpu is lower than 10%. migrate dockers to lxc container again.

with these combo, debian vm lives about 2 days now is still good. host kernel Edge 5.19.8-1 host os install latest cpu microcode install backports kernel 5.18 to guest debian vm

memory should be ok, it memory has problem, windows guest should die like debian guest.

after upgraded to 5.19.7-1, pve died once (cpu is not busy at that moment), debian guest vm freezed once in 8 hours. changed guest cpu type from 'host' to 'kvm64', hope that will last longer.

2 debian vms did not freeze in 24 hours, at before they won't make it. just upgraded to 5.19.7-1.

alright, I've just installed kernel 5.19.6-1, and started 2 debian VMs.

5.15.39-4-pve, but #206 said the problem still exist with edge kernel. and I've migrated all containers to a LXC container.

n5105 pve host running 3 vms: debian 11 with some containers in it. win 7 vm win10 vm win 7 & win 10 vm are very stable, while the debian vm keep freezed in randomly time. logged in kdump RIP: 0010:asm_exc_page_fault+0x0/0x30 while the same vm was very stable in previous j3455 pve host.

thanks, restart pvestat service makes it back to normal. reason might be concurrent backup jobs makes target storage too busy : https://forum.proxmox.com/threads/limit-concurrent-tasks.93120/#post-483297

thanks, can it be restore to normal stat without system reboot?

other 4 nodes did not have this problem, just node 3 . root@pve-3:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-6 pve-kernel-helper: 7.2-6 pve-kernel-5.15.39-1-pve: 5.15.39-1 pve-kernel-5.15.35-3-pve...

a node (pve-3,172.16.2.3) is marked as questioned in web UI. what is found: 1. ssh to the node is ok, and vm is not dead, can be migrate to other node with [qm migrate --live] command. 2. restart pveproxy service did not fix the problem. 3. access to the node's ui(https://172.16.2.3:8006) is ok...

when our pve nodes expanded from 3 to 5, the IO issue on target pbs goes much worse. (sometimes a small mount of VMs backup will failed)

just migrate a windows 2003 server from esxi to pve, using this article to prepare. (other methods I found all leads to 0x0000007b bsod) https://backdrift.org/converting-windows-guests-from-vmware-esx-to-kvm-with-virtio-drivers