moving Windows11 from one PVE to a new PVE does not work

MathiasD

New Member
Sep 8, 2024
4
1
3
Hi,

i am trying to move Windows 11 VM from one PVE to my new PVE (both running 8.2.4). Simple Backup on the old one and restore on the new PVE does not work. Windows is starting and running into diagnosis cycle. I have already removed TPM disk and added a new one but w/o success.

Anyone aware of the steps to be taken to get Windows 11 running successfully on the new PVE with backup/restore?

Thanks in advance,

Mathias
 
22 x Intel(R) Core(TM) Ultra 7 155H (1 Socket)


root@pve:/etc/pve/nodes/pve/qemu-server# cat 101.conf
agent: 1
bios: ovmf
boot: order=virtio0;ide0;ide2;net0
cores: 4
cpu: host
efidisk0: local-lvm:vm-101-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/virtio-win-0.1.248.iso,media=cdrom,size=715188K
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1716744108
name: Win11-M
net0: virtio=AC:24:11:68:C5:B4,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
parent: vor_update
scsihw: virtio-scsi-single
smbios1: uuid=71264e2b-db4c-4a11-8182-401c01ea73a7
sockets: 1
tpmstate0: local-lvm:vm-101-disk-1,size=4M,version=v2.0
vga: virtio
virtio0: local-lvm:vm-101-disk-2,iothread=1,size=64G
vmgenid: 7ed674ce-d8b3-44b7-98f7-42558205a160
 
You have to define another cpu-type in the config of the vm - a common qemu-type like x86-64-v2-AES. And then you must repair Windows inside the vm with this cpu.
 
Thanks Ralli, makes total sense if i switch to new CPU architecture the CPU settings has to be adopted accordingly (to the one you suggested). Now everything is fine and VM up and running. Repair was not required.

Mathias
 
Last edited:
  • Like
Reactions: Ralli