Closed rbreaves closed 3 years ago
I apologize... the revenge of wsl2 strikes again! 😅.. I thought I had downgraded wsl2 to wsl1 on everything I have but apparently not and that created the failure above. Hyper-V really sucks and I hate the direction wsl has gone in for the sake of raw performance.
Closing this issue as it was purely on my end. I did try setting the cpuid manually before seeing my wsl was on 2 and I simply undid that by specifying host on the cpu-profile.
What do I need to do to get this to boot normally? It is kernel panicing on the other system with "exit reason namespace 2 subcode 0x4".