Boot failure on imported VM

hermannw · Saturday at 11:45

I face problems booting an imported VM on pve, origin an Hyper-V Gen. 2 vhdx.
The VM (Server 2025) starts, then "Display initialisation" appears, followed by "Automatic repair" from Windows resulting "Windows Boot Manager 0xc0000225".
Because even booting from the Server2025-Iso is not successful, I suspect the Problem is caused by "something in pve".

The bahavior is the same, importing the vhdx directly:
qm importdisk <vmid> <vm.vhdx> local-lvm
or via raw:
qemu-img convert -f vhdx vm.vhdx -O raw vm.raw
qm importdisk <vmid> <vm.raw> local-lvm

I tried several settings in the VM, different BIOS, w/o VirtIO etc.

Strange thing. On another setting which I used as PoC for pve, pbs and automount the imported VM start without any problem.
Its the same hardware except the SSD.

This is quite a problem, as Hyper-V is already overwritten by pve.

This is a subset of the System Log. I cannot find any obvious errors.

Code:

Jul 25 11:32:25 pve login[1586]: ROOT LOGIN ON pts/0
Jul 25 11:32:31 pve login[1586]: pam_unix(login:session): session closed for user root
Jul 25 11:32:31 pve pvedaemon[1151]: <root@pam> end task UPID:pve:0000062F:00003A27:6A6482A8:vncshell::root@pam: OK
Jul 25 11:32:31 pve systemd[1]: session-3.scope: Deactivated successfully.
Jul 25 11:32:31 pve systemd-logind[781]: Session 3 logged out. Waiting for processes to exit.
Jul 25 11:32:31 pve systemd-logind[781]: Removed session 3.
Jul 25 11:32:32 pve chronyd[762]: Selected source 91.98.156.7 (2.debian.pool.ntp.org)
Jul 25 11:32:42 pve systemd[1]: Stopping user@0.service - User Manager for UID 0...
Jul 25 11:32:42 pve systemd[1594]: Activating special unit exit.target...
Jul 25 11:32:42 pve systemd[1594]: Stopped target default.target - Main User Target.
Jul 25 11:32:42 pve systemd[1594]: Stopped target basic.target - Basic System.
Jul 25 11:32:42 pve systemd[1594]: Stopped target paths.target - Paths.
Jul 25 11:32:42 pve systemd[1594]: Stopped target sockets.target - Sockets.
Jul 25 11:32:42 pve systemd[1594]: Stopped target timers.target - Timers.
Jul 25 11:32:42 pve systemd[1594]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Jul 25 11:32:42 pve systemd[1594]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 25 11:32:42 pve systemd[1594]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Jul 25 11:32:42 pve systemd[1594]: Stopping gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
Jul 25 11:32:42 pve systemd[1594]: Stopping gpg-agent.socket - GnuPG cryptographic agent and passphrase cache...
Jul 25 11:32:42 pve systemd[1594]: Closed keyboxd.socket - GnuPG public key management service.
Jul 25 11:32:42 pve systemd[1594]: Stopping ssh-agent.socket - OpenSSH Agent socket...
Jul 25 11:32:42 pve systemd[1594]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Jul 25 11:32:42 pve systemd[1594]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Jul 25 11:32:42 pve systemd[1594]: Closed ssh-agent.socket - OpenSSH Agent socket.
Jul 25 11:32:42 pve systemd[1594]: Removed slice app.slice - User Application Slice.
Jul 25 11:32:42 pve systemd[1594]: Reached target shutdown.target - Shutdown.
Jul 25 11:32:42 pve systemd[1594]: Finished systemd-exit.service - Exit the Session.
Jul 25 11:32:42 pve systemd[1594]: Reached target exit.target - Exit the Session.
Jul 25 11:32:42 pve (sd-pam)[1596]: pam_unix(systemd-user:session): session closed for user root
Jul 25 11:32:42 pve systemd-logind[781]: Removed session 4.
Jul 25 11:32:42 pve systemd[1]: user@0.service: Deactivated successfully.
Jul 25 11:32:42 pve systemd[1]: Stopped user@0.service - User Manager for UID 0.
Jul 25 11:32:42 pve systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Jul 25 11:32:42 pve systemd[1]: run-user-0.mount: Deactivated successfully.
Jul 25 11:32:42 pve systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Jul 25 11:32:42 pve systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Jul 25 11:32:42 pve systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Jul 25 11:32:42 pve systemd[1]: user-0.slice: Consumed 1.073s CPU time, 11.8M memory peak.
Jul 25 11:33:35 pve pvedaemon[1150]: <root@pam> update VM 100: -boot order=sata0
Jul 25 11:33:50 pve pvedaemon[1940]: start VM 100: UPID:pve:00000794:00005BAC:6A6482FE:qmstart:100:root@pam:
Jul 25 11:33:50 pve pvedaemon[1149]: <root@pam> starting task UPID:pve:00000794:00005BAC:6A6482FE:qmstart:100:root@pam:
Jul 25 11:33:51 pve systemd[1]: Created slice qemu.slice - Slice /qemu.
Jul 25 11:33:51 pve systemd[1]: Started 100.scope.
Jul 25 11:33:54 pve kernel: tap100i0: entered promiscuous mode
Jul 25 11:33:54 pve kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jul 25 11:33:54 pve kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jul 25 11:33:54 pve kernel: fwpr100p0: entered allmulticast mode
Jul 25 11:33:54 pve kernel: fwpr100p0: entered promiscuous mode
Jul 25 11:33:54 pve kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jul 25 11:33:54 pve kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jul 25 11:33:55 pve kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jul 25 11:33:55 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jul 25 11:33:55 pve kernel: fwln100i0: entered allmulticast mode
Jul 25 11:33:55 pve kernel: fwln100i0: entered promiscuous mode
Jul 25 11:33:55 pve kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jul 25 11:33:55 pve kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jul 25 11:33:55 pve kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jul 25 11:33:55 pve kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jul 25 11:33:55 pve kernel: tap100i0: entered allmulticast mode
Jul 25 11:33:55 pve kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jul 25 11:33:55 pve kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jul 25 11:33:55 pve pvedaemon[1940]: VM 100 started with PID 1998 using pve-qemu-kvm_11.0.2-1.
Jul 25 11:33:55 pve pvedaemon[1149]: <root@pam> end task UPID:pve:00000794:00005BAC:6A6482FE:qmstart:100:root@pam: OK
Jul 25 11:33:55 pve pvedaemon[2061]: starting vnc proxy UPID:pve:0000080D:00005DA5:6A648303:vncproxy:100:root@pam:
Jul 25 11:33:55 pve pvedaemon[1149]: <root@pam> starting task UPID:pve:0000080D:00005DA5:6A648303:vncproxy:100:root@pam:
Jul 25 11:38:02 pve pvedaemon[1149]: <root@pam> end task UPID:pve:0000080D:00005DA5:6A648303:vncproxy:100:root@pam: OK
Jul 25 11:39:56 pve pvedaemon[3352]: starting vnc proxy UPID:pve:00000D18:0000EA9A:6A64846C:vncproxy:100:root@pam:
Jul 25 11:39:56 pve pvedaemon[1150]: <root@pam> starting task UPID:pve:00000D18:0000EA9A:6A64846C:vncproxy:100:root@pam:
Jul 25 11:40:08 pve pvedaemon[3405]: stop VM 100: UPID:pve:00000D4D:0000EF69:6A648478:qmstop:100:root@pam:
Jul 25 11:40:08 pve pvedaemon[1149]: <root@pam> starting task UPID:pve:00000D4D:0000EF69:6A648478:qmstop:100:root@pam:
Jul 25 11:40:09 pve kernel: tap100i0: left allmulticast mode
Jul 25 11:40:09 pve kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jul 25 11:40:09 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jul 25 11:40:09 pve kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jul 25 11:40:09 pve kernel: fwln100i0 (unregistering): left allmulticast mode
Jul 25 11:40:09 pve kernel: fwln100i0 (unregistering): left promiscuous mode
Jul 25 11:40:09 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jul 25 11:40:09 pve kernel: fwpr100p0 (unregistering): left allmulticast mode
Jul 25 11:40:09 pve kernel: fwpr100p0 (unregistering): left promiscuous mode
Jul 25 11:40:09 pve kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jul 25 11:40:09 pve qmeventd[780]: read: Connection reset by peer
Jul 25 11:40:09 pve systemd[1]: 100.scope: Deactivated successfully.
Jul 25 11:40:09 pve systemd[1]: 100.scope: Consumed 6min 37.821s CPU time, 903.4M memory peak.
Jul 25 11:40:09 pve pvedaemon[1149]: <root@pam> end task UPID:pve:00000D4D:0000EF69:6A648478:qmstop:100:root@pam: OK
Jul 25 11:40:09 pve pvedaemon[1150]: <root@pam> end task UPID:pve:00000D18:0000EA9A:6A64846C:vncproxy:100:root@pam: OK
Jul 25 11:40:13 pve qmeventd[3428]: Starting cleanup for 100
Jul 25 11:40:13 pve qmeventd[3428]: Finished cleanup for 100

j.theisen · 2026-07-27T12:40:27+0200

Hi @hermannw

thanks for posting on the forum!

hermannw said:
I tried several settings in the VM, different BIOS, w/o VirtIO etc

What is the current configuration of the VM and how was it configured on Hyper-V?
You can gather the whole config with the following command:

Code:

cat /etc/pve/qemu-server/<VM-ID>.conf

In general the recommended migration path includes:

migrating and attaching the VM disks as SATA disks for native Windows Support
Mount a dummy SCSI disk with a VirtIO SCSI Single disk controller
Install the VirtIO drivers
Remove the dummy disk and detach and reattach the disks as SCSI disks
Windows should properly pick up the change and boot normally

That's just a short version and is just for reference.
In your case we have to have closer look at the current and originating VM config.

Best regards
Jonas

Francois Baillargeon · 2026-07-27T13:40:59+0200

I agree with @j.theisen here, we usually see stuff with "Inacessible boot device" upon import, hence why we ended up baking a VirtIO préinstall script for VMWare to make it smoother.

It's probably just that

Boot failure on imported VM

hermannw

New Member

j.theisen

Active Member

Francois Baillargeon

New Member

We value your privacy