Migration VM /LXC from proxmox 5.4 to 6.2 (from ext to zfs)

[gusto]

I am currently using proxmox. I have it all installed on 1x SSD EXT4.

proxmox-ve: 5.4-2 (running kernel: 4.15.18-26-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-14
pve-kernel-4.15.18-26-pve: 4.15.18-54
pve-kernel-4.15.18-25-pve: 4.15.18-53
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-41
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-55
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

I recently bought an MB Odroid H2, 2x 16GB Ram and 2x SSD. I installed Proxmox 6.2 on RAID1 ZFS. Now I need to migrate VMs and LXCs to the new Proxmox 6.2.
On Proxmox 5.4 I did a VM and LXC backup. I copied backups to the new Proxmox 6.2 to /var/lib/vz/dump /. On the new Proxmox 6.2 I already have 1x VM installed and the configuration file looks like this

bootdisk: virtio0
cores: 2
ide2: local:iso/pfSense-CE-2.4.5-RELEASE-p1-amd64.iso,media=cdrom
memory: 2048
name: pfsense
net0: virtio=E6:39:42:D1:DA:48,bridge=vmbr1
net1: virtio=4A:43:8B:0C:E5:1E,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=3800b785-7edc-4dd5-a9ff-84789a22d527
sockets: 1
virtio0: local-zfs:vm-100-disk-0,size=10G
vmgenid: 5cfb2311-360f-41e4-b811-d0eaa600195f
#qmdump#map:virtio0:drive-virtio0:local-zfs::

If I look at the configuration file in Proxmox 5.4, I see some differences there

balloon: 512
bootdisk: scsi0
cores: 1
ide2: local:iso/debian-9.3.0-amd64-netinst.iso,media=cdrom
memory: 1024
name: debian
net0: virtio=D6:61:D2:2C:36:2A,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-100-disk-1,size=8G
scsihw: virtio-scsi-pci
smbios1: uuid=687f7e5c-8b3e-43de-8a81-31db4ee4316b
sockets: 1
usb0: host=0403:6010
#qmdump#map:scsi0:drive-scsi0:local-lvm:raw:

I haven't tried to migrate VMs yet, but I want to ask if there will be problems with migration?

 

[aaron]

What exactly is the problem? Do you plan to restore a VM to the same VMID as the one you have already configured on the new host?
You can change the VMID of the restored VM if you start the restore procedure from the storage panel. Select the backup you want to restore and the dialog should offer you a field to set a different VMID.