Windows 11 installation breaks Proxmox

[unnamed]

Hey everyone,

I would like to ask for some help. In the last days, i tried to install an Windows 11 maschine on my ProxMox Server.

> For the settings iam using this tutorial: https://pve.proxmox.com/wiki/Windows_11_guest_best_practices

The installtion works pretty well. But after the installation was finshed and Windows tries to boot up, The whole Server freezes ...

Does anyone got an idea, where i can start to search for the failure ?
After switching the Network interface, the Server cames up again, without rebooting it.

Jan 05 12:56:42 SpProxNg01 systemd[1]: Activating swap dev-pve-swap.swap - /dev/pve/swap...
Jan 05 12:56:42 SpProxNg01 systemd[1]: Starting systemd-fsck@dev-disk-by\x2duuid-54B3\x2dFE15.service - File System Check on /dev/disk/by-uuid/54B3-FE15...
Jan 05 12:56:42 SpProxNg01 systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
Jan 05 12:56:42 SpProxNg01 kernel: Adding 8388604k swap on /dev/mapper/pve-swap.  Priority:-2 extents:1 across:8388604k SS
Jan 05 12:56:42 SpProxNg01 systemd[1]: Activated swap dev-pve-swap.swap - /dev/pve/swap.
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: fsck.fat 4.2 (2021-01-31)
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: There are differences between boot sector and its backup.
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: This is mostly harmless. Differences: (offset:original/backup)
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]:   65:01/00
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]:   Not automatically fixing this.
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]:  Automatically removing dirty bit.
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: *** Filesystem was changed ***
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: Writing changes.
Jan 05 12:56:42 SpProxNg01 systemd-fsck[607]: /dev/nvme0n1p2: 13 files, 2984/261628 clusters
Jan 05 12:56:42 SpProxNg01 systemd[1]: Found device dev-disk-by\x2duuid-c1874022\x2d38fe\x2d4d25\x2da84d\x2d4e8910784b65.device - CT1000MX500SSD1 1.
Jan 05 12:56:42 SpProxNg01 systemd[1]: Finished systemd-fsck@dev-disk-by\x2duuid-54B3\x2dFE15.service - File System Check on /dev/disk/by-uuid/54B3-FE15.
Jan 05 12:56:42 SpProxNg01 systemd[1]: Reached target swap.target - Swaps.
Jan 05 12:56:42 SpProxNg01 systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 05 12:56:42 SpProxNg01 systemd[1]: Started systemd-fsckd.service - File System Check Daemon to report status.

the output of "journalctl -p err -f" is

root@SpProxNg01:~# journalctl -p err -f
Jan 05 12:56:42 SpProxNg01 kernel: snd_hda_intel 0000:00:1f.3: no codecs found!

Maybe it could be a Filesystem problem ?

Tanks a lot.

Mario

 

[l.leahu-vladucu]

Hello unnamed! Just to be sure: what do you mean by "the whole server freezes"? If I understand you correctly, you're saying that not just the VM freezes, but the host and all other VMs as well. So just to get a better understanding of the situation: is the server (host with PVE) just not reachable anymore over the network, while it still works if you connect a monitor to it? I'm asking because under normal circumstances, the host should not be influenced by any changes in the VM. What I'm rather thinking is whether both the host and the VM have an IP conflict that prevents you from connecting over the internet, but the server still works if you connect a monitor to it. Can you please check that first?