We upgraded PVE on older hardware from version 5.4 to latest 6.2-11 (latest) as in-place upgrade 2 days ago.
There are only 2 active VMs on that server currently, a Linux VM which seems to "behave" (perform) as before and an old Win7 VM (hopefully to be decommissioned within the next 4 week).
The nightly vzdump/snapshot for its 300GB virtual disk (ending in about 160GB .lzo file) was still running the next morning (after 8 hours) and we had to cancel this. It normally takes (took) less than 1 hour so something is extremely slow after this PVE (Debian) upgrade (?)
It's a very simple config (we believe):
qm config 200
boot: c
bootdisk: virtio0
cores: 2
description: Windows 7 Professional%0AHosting SQL Express for V6 Database
ide2: none,media=cdrom
memory: 8192
name: nlc005sv
net0: e1000=46:AE:42:A1:ED:26,bridge=vmbr0
onboot: 1
ostype: win7
sockets: 2
startup: order=3,up=20
virtio0: local:200/vm-200-disk-1.raw,format=raw,size=300G
There are only 2 active VMs on that server currently, a Linux VM which seems to "behave" (perform) as before and an old Win7 VM (hopefully to be decommissioned within the next 4 week).
The nightly vzdump/snapshot for its 300GB virtual disk (ending in about 160GB .lzo file) was still running the next morning (after 8 hours) and we had to cancel this. It normally takes (took) less than 1 hour so something is extremely slow after this PVE (Debian) upgrade (?)
It's a very simple config (we believe):
qm config 200
boot: c
bootdisk: virtio0
cores: 2
description: Windows 7 Professional%0AHosting SQL Express for V6 Database
ide2: none,media=cdrom
memory: 8192
name: nlc005sv
net0: e1000=46:AE:42:A1:ED:26,bridge=vmbr0
onboot: 1
ostype: win7
sockets: 2
startup: order=3,up=20
virtio0: local:200/vm-200-disk-1.raw,format=raw,size=300G