[SOLVED] Migrating a virtual machine from one server to another


New Member
Jul 30, 2021
Hello everyone, I want to migrate an entire virtual machine from one Proxmox VE server to another

On the server where the virtual machine is located, I execute the command
vzdump 106 --dumpdir /root --mode stop

after using scp

I am transferring this image to a server where I want to deploy a copy of this virtual machine

scp /root/vzdump-qemu-106-2022_11_30-21_56_04.vma root@

Next on the server where I want to restore the copy I execute

qmrestore /var/lib/vz/dump/vzdump-qemu-106-2022_12_01-01_42_48.vma 103

root@Debian-1101-bullseye-amd64-base ~ # qmrestore /var/lib/vz/dump/vzdump-qemu-106-2022_12_01-01_42_48.vma 103 restore vma archive: vma extract -v -r /var/tmp/vzdumptmp15808.fifo /var/lib/vz/dump/vzdump-qemu-106-2022_12_01-01_42_48.vma /var/tmp/vzdumptmp15808 CFG: size: 433 name: qemu-server.conf CTIME: Wed Nov 30 23:42:48 2022 vma archive contains no image data rescan volumes...

I get this error, I have completely cloned the virtual machine, but there is no virtual machine disk image from which it should be launched

Server from where I want to make a copy:

root@pve:/var/lib/vz/dump# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-12 pve-kernel-5.13: 7.1-7 pve-kernel-5.13.19-4-pve: 5.13.19-9 pve-kernel-5.13.19-2-pve: 5.13.19-4 ceph-fuse: 15.2.15-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve2 libproxmox-acme-perl: 1.4.1 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.1-6 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.1-3 libpve-guest-common-perl: 4.1-1 libpve-http-server-perl: 4.1-1 libpve-storage-perl: 7.1-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.11-1 lxcfs: 4.0.11-pve1 novnc-pve: 1.3.0-2 proxmox-backup-client: 2.1.5-1 proxmox-backup-file-restore: 2.1.5-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.4-6 pve-cluster: 7.1-3 pve-container: 4.1-4 pve-docs: 7.1-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.3-5 pve-ha-manager: 3.3-3 pve-i18n: 2.6-2 pve-qemu-kvm: 6.1.1-2 pve-xtermjs: 4.16.0-1 qemu-server: 7.1-4 smartmontools: 7.2-1 spiceterm: 3.2-2 swtpm: 0.7.0~rc1+2 vncterm: 1.7-1 zfsutils-linux: 2.1.2-pve1 root@pve:/var/lib/vz/dump#

Server where I want to make a copy:

root@Debian-1101-bullseye-amd64-base /var/lib/vz/dump # pveversion -v proxmox-ve: 7.3-1 (running kernel: 5.15.64-1-pve) pve-manager: 7.3-3 (running version: 7.3-3/c3928077) pve-kernel-5.15: 7.2-14 pve-kernel-helper: 7.2-14 pve-kernel-5.15.74-1-pve: 5.15.74-1 pve-kernel-5.15.64-1-pve: 5.15.64-1 ceph-fuse: 16.2.9-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown: residual config ifupdown2: 3.1.0-1+pmx3 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve2 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-5 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.3-1 libpve-guest-common-perl: 4.2-3 libpve-http-server-perl: 4.1-5 libpve-storage-perl: 7.3-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.3.1-1 proxmox-backup-file-restore: 2.3.1-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.3 pve-cluster: 7.3-1 pve-container: 4.4-2 pve-docs: 7.3-1 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-7 pve-firmware: 3.5-6 pve-ha-manager: 3.5.1 pve-i18n: 2.8-1 pve-qemu-kvm: 7.1.0-4 pve-xtermjs: 4.16.0-1 qemu-server: 7.3-1 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.8.0~bpo11+2 vncterm: 1.7-1 root@Debian-1101-bullseye-amd64-base /var/lib/vz/dump


  • 1669852761639.png
    326 bytes · Views: 5
  • 1669852775363.png
    326 bytes · Views: 5


New Member
Jul 30, 2021
what does "qm config 106" show on source server? what does the vzdump log look like? Is this VM using pass-through disks perhaps?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
root@pve:~# qm config 106 agent: 1 boot: order=scsi0;ide2;net0 cores: 4 ide2: local:iso/debian10_x64.iso,media=cdrom memory: 7000 meta: creation-qemu=6.1.1,ctime=1660557214 name: Exchange.Cyber.x64 net0: virtio=52:32:8B:8B:E7:12,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 scsi0: local-lvm:vm-106-disk-0,backup=0,size=32G,ssd=1 scsihw: virtio-scsi-pci smbios1: uuid=cbf5023e-29de-40c7-9f86-d01cd22bb0cb sockets: 2 vmgenid: 0f30ae13-32a2-4fbf-93e5-61d3d420c29d root@pve:~#

INFO: starting new backup job: vzdump 106 --storage local --mode snapshot --remove 0 --node pve --compress 0 INFO: Starting Backup of VM 106 (qemu) INFO: Backup started at 2022-12-01 22:00:25 INFO: status = stopped INFO: backup mode: stop INFO: ionice priority: 7 INFO: VM Name: Exchange.Cyber.x64 INFO: exclude disk 'scsi0' 'local-lvm:vm-106-disk-0' (backup=no) INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-qemu-106-2022_12_01-22_00_25.vma' INFO: backup contains no disks INFO: starting template backup INFO: /usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-106-2022_12_01-22_00_25.tmp/qemu-server.conf exec:cat > /var/lib/vz/dump/vzdump-qemu-106-2022_12_01-22_00_25.dat INFO: archive file size: 13KB INFO: Finished Backup of VM 106 (00:00:00) INFO: Backup finished at 2022-12-01 22:00:25 INFO: Backup job finished successfully TASK OK


Famous Member
Nov 20, 2020
Last edited:


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 your own in 60 seconds.

Buy now!