[SOLVED] New network card "Device instance id" after VM restore

[n1kt0]

Hei!

Problem.
After the old server died, I restored the virtual machine, but the network didn't work!
It turned out the machine's old network card had disappeared and a new one had appeared.

Since the IP address was set manually, the network didn't work.

Old "Red Hat VirtIO Ethernet Adapter"
PCI\VEN_1AF4&DEV_1000&SUBSYS_00011AF4&REV_00\5&97B8697&0&9008F0

Device instance id: 5&97B8697&0&9008F0

New "Red Hat VirtIO Ethernet Adapter #2"
PCI\VEN_1AF4&DEV_1000&SUBSYS_00011AF4&REV_00\5&2490727A&0&9008F0

Device instance id: 5&2490727A&0&9008F0

Question: Is it possible to return the old card and lock it so that the ID is always 5&97B8697&0&9008F0?

 

[fiona]

Hi,
please share the output of pveversion -v and qm config ID with the numerical ID of your VM as well as the config inside the backup, i.e. Show Configuration button when selecting the backup.

 

[n1kt0]

Hei!

An error occurred, the virtual machine was "machine: q35"
Before launching, we changed it to q35-10.1, and then the old network adapter disappeared and a new one appeared!

We deployed the server again, but this time we didn't change the machine version; the adapter, 5&97B8697&0&9008F0, remained.

What should I do when support for pc-q35-5.1 ends?

Thanks in advance.



pveversion -v

Spoiler

proxmox-ve: 9.1.0 (running kernel: 6.17.4-2-pve)
pve-manager: 9.1.4 (running version: 9.1.4/5ac30304265fbd8e)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.4-2-pve-signed: 6.17.4-2
proxmox-kernel-6.17: 6.17.4-2
proxmox-kernel-6.17.4-1-pve-signed: 6.17.4-1
proxmox-kernel-6.17.2-2-pve-signed: 6.17.2-2
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
proxmox-kernel-6.14.11-5-pve-signed: 6.14.11-5
proxmox-kernel-6.14: 6.14.11-5
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx11
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.5
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.1.4
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.4
libpve-rs-perl: 0.11.4
libpve-storage-perl: 9.1.0
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.1.1-1
proxmox-backup-file-restore: 4.1.1-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.5
pve-cluster: 9.0.7
pve-container: 6.0.18
pve-docs: 9.1.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.1.0
pve-i18n: 3.6.6
pve-qemu-kvm: 10.1.2-5
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.3
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1

Backup config:

Spoiler

balloon: 0
boot: c
bootdisk: virtio0
cores: 4
machine: q35
memory: 8192
name: y-SRV-CFSW19
net0: virtio=66:B4:DB:B7:2D:CC,bridge=vmbr200,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=a699ed21-111a-4896-8338-65f33aec1b1f
sockets: 1
vga: virtio
virtio0: data_ssd_samsung_512g_970Pro:vm-500518-disk-0,cache=writeback,size=64G
vmgenid: 275e6192-caf0-4ac0-80aa-e52e8b475b4c
#qmdump#map:virtio0:drive-virtio0:data_ssd_samsung_512g_970Pro:raw:

 

[fiona]

Yes, there was a bug fix in QEMU's ACPI implementation with machine version 5.2 that affects the device enumeration in Windows: https://pve.proxmox.com/wiki/QEMU_Machine_Version_Upgrade

If you do change the machine version to a newer one, you'll have to adapt the configuration inside the VM. This is recommended. Otherwise, you would need to avoid upgrading to QEMU 11.1 when it comes out (that version will remove support for 5.1 and will likely land in Proxmox VE in late 2026 or early 2027).