Hyper-V Machine no network

[DrillSgtErnst]

Hi. I just miograted a vm from hyper-V
At first i imaged it with veeam and created a new machine with veeam recovery DVD.

All fine

restart and i can not access network anymore.

then I exported a vhdx cleanly. No errors detected
start the machine. no network.
adapter is loaded but I cant connect. So two machines, exact same problem, I know no more ways to get my vm to the ethernet. I have attached a acreenshot of the Device Manager and you see the available drivers etc.

I have not experienced such problem with PVE before.

Spoiler: pveversion -v

root@pve:/mnt/pve/backup/images/MEDISTAR/Virtual Hard Disks# pve info
-bash: pve: command not found
root@pve:/mnt/pve/backup/images/MEDISTAR/Virtual Hard Disks# pveinfo
-bash: pveinfo: command not found
root@pve:/mnt/pve/backup/images/MEDISTAR/Virtual Hard Disks# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-5.15: 7.3-1
pve-kernel-helper: 7.3-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
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.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
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.2-1
proxmox-backup-file-restore: 2.3.2-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.6-2
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-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.7-pve2

I kinda think it's a windows problem. But why would it?
network device is my vmbr
Intel E1000
random MAC
no VLAN
no Firewall


Any ideas?

 

[alexskysilk]

that isnt indicative of anything- it could just be the windows default behavior for a new nic (put it in the public zone)

does your vm have an ip address? can it ping the gateway?

 

[DrillSgtErnst]

Yeah well. As you see. There is no NIC. it's detected by devicemgr, but that's it.

BUT
I was digging deep here.

My Server 2016 is german
https://forum.proxmox.com/threads/n...erver-after-upgrade-to-proxmox-7.92094/page-4
Proxmox seems to have had problems (or better windows had problems) and it's super tedious.


I had to set it to q35 v 5.1 specifically. Now I can see a NIC, sxet an IP and work with it.

But the second machine with the same error now shows BOOT_DEVICE_INACCESSIBLE BSOD on boot with a q 35 v 5.1 machine

My hair would turn grey if I wasn't bald.

 

[alexskysilk]

Yeah well. As you see. There is no NIC.

But the second machine with the same error now shows BOOT_DEVICE_INACCESSIBLE BSOD on boot with a q 35 v 5.1 machine

make sure you set your disk bus to SATA or IDE, and check your boot order to make sure the boot disk is in there.

 

[DrillSgtErnst]

Yeah I saw what you want to show with the mark. That's why i posted it.
But under Network Connections there is no tab.

Even from Baremetal the machine does not boot up. Dang this Q35 machine thing is exhausting

The boot process does start, but it won't follow through.

 

[DrillSgtErnst]

Sooo I have found out, that the machine is booting up, given I disable the enforcement of digitally signed drivers.

Then there were two things fishy.
firstly the shown and defective "HID Interrupt Driver" as seen above and a Microsoft Debugging network Interface.
I uninstalled the HID Interrupt thingy and deactivated the Debug Interface using bcdedit /debug off
As seen on answers[DOT]microsoft[DOT]com KB Article f72b8408-e4f7-4593-9e18-8cbb3e38a5ad
The machine is booting now. I hope it's fine now.