PM 6.0 + Win2016 VM - unable to snapshot (with RAM included)


Well-Known Member
May 28, 2018
Hi there.
I performed a fresh installation of PM on a brand new Fujitsu RX2520 server.
Then, after some PM setup and tweak I performed a Win2016 VM installation.
After few days of work (updates, installing windows software etc.) I let the VM go in production environment.
Config as folows:

:~# qm config 100
agent: 1
balloon: 32768
boot: cd
bootdisk: scsi1
cores: 8
hostpci0: 65:00
hotplug: disk,usb
ide0: none,media=cdrom
ide2: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
memory: 49152
name: Win2016
numa: 0
onboot: 1
ostype: win10
scsi1: local-lvm:vm-100-disk-1,size=150G
scsi2: local-lvm:vm-100-disk-0,size=300G
scsi4: backup_storage:100/vm-100-disk-0.qcow2,backup=0,size=200G
scsihw: virtio-scsi-pci
smbios1: uuid=xxxxxxxxxxxxxxx
sockets: 1
startup: up=5
vmgenid: xxxxxxxxxxxxxxxxxx

Pretty much only interesting feature is pci passthrough setup for entire device 65:00 (dedicated PCI-E NIC). Established with intel_iommu=on on GRUB.

Everything works like a charm... except I can't make a VM's snapshot with RAM included :rolleyes:
I get the error:
VM 100 qmp command 'savevm-start' failed - State blocked by non-migratable device '0000:00:10.0/vfio-pci'

Now, I admit I wasn't using snapshot that often so I wonder if including RAM is a general issue or it matters with ballooning for example? Or is it a VM OS dependency? If not, perhapse 'include RAM' is not recommended anyway?


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!