Win7 migrated from hyperv boot only first time, then bsod

garnoux

Member
Apr 7, 2023
23
0
6
France
garnx.fr
Hello,
I need to migrate two W7 hyperv machines to proxmox. I tried several ways to import them into proxmox: (proxmox wizard included in veeam, vmdk export, vhdx export).
Then I configured the VM and imported the disks on the proxmox server.

The first machine presents no problems. On the other hand, the second machine boots correctly the first time but, for one reason or another, refuses to boot after its first shutdown. After the Windows logo, I get a BSOD with the error. The system repair tool doesn't work

1751371312294.png

IF I re-import the disk, it boots correctly the first time, and then again.

VM Config :
Code:
root@mox-resto:~# cat /etc/pve/qemu-server/9002.conf
bios: ovmf
boot: order=ide0;ide2;net0
cores: 4
cpu: x86-64-v2-AES
efidisk0: data:9002/vm-9002-disk-3.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: data:9002/vm-9002-disk-0.raw,size=60G
ide1: data:9002/vm-9002-disk-1.raw,size=100G
ide2: local:iso/virtio-win-0.1.189.iso,media=cdrom,size=488766K
ide3: data:9002/vm-9002-disk-2.raw,size=500G
machine: pc-i440fx-9.2+pve1
memory: 16384
meta: creation-qemu=9.2.0,ctime=1750319773
name: srv-dao-2
net0: e1000=00:15:5d:00:3c:01,bridge=vmbr0,firewall=1,tag=99
numa: 0
ostype: win7
scsihw: virtio-scsi-single
smbios1: uuid=b49b817b-e420-4452-9636-94ac39b2be82
sockets: 2
tags: cao-2
vmgenid: cd8141a7-b53f-4bde-bd2d-843faa72c2e6

Proxmox version :
Code:
proot@mox-resto:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.8.12-11-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8: 6.8.12-11
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.11
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.1
pve-firmware: 3.15-4
pve-ha-manager: 4.0.7
pve-i18n: 3.4.4
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2

Tried different things like change CPU type, disk controller, machine version, ...
There is no "guests" installed on VM instead of HyperV integrations. I would like to not install guests on production VM (hyperv)

If someone has an idea
Thank's
 
I manage to start the machine by pressing F8 then “last known good configuration”. it starts without any problem.

i tried to change the boot configuration with msconfig but i still get the blue screen. so i don't know what changes with LKGC

furthermore, the machine doesn't detect DVDs (I can't install virtio from here) and I can't connect it to the internet