Microsoft Windows 10 Version 21H2 Build 19044.1889
WSL Version
[X] WSL 2
[ ] WSL 1
Kernel Version
5.10.102.1
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Build Windows 10 21H2 multisession instance in Azure VDI. copy Ubuntu 20.04.tar down to system and run wsl --import Ubuntu install locationtar location --version 2
Vmem in task manager starts to ramp up and the ext4.vhdx starts to increase in size and then both stall. Able to kill wsl and Ctrl+C out of the powershell instance but after this unable to interact with wsl at all, cannot do wsl --shutdown. vmem still shows up in processes, no memory usage fluctuation. Have to fully shutdown the Azure VM which takes ages to deallocate due to the lock up.
We are currently using FSLogix Profile containers but have experienced this issue with and without FSLogix utilisation.
Expected Behavior
Expecting the import to finish which on the odd occasion it does but more often than not, it stalls and becomes unresponsive.
Actual Behavior
there is no failure message, if left (Which we have done for 24 hours) the process is still just sat there doing absolutely nothing.
Version
Microsoft Windows 10 Version 21H2 Build 19044.1889
WSL Version
Kernel Version
5.10.102.1
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Build Windows 10 21H2 multisession instance in Azure VDI. copy Ubuntu 20.04.tar down to system and run wsl --import Ubuntu install location tar location --version 2
Vmem in task manager starts to ramp up and the ext4.vhdx starts to increase in size and then both stall. Able to kill wsl and Ctrl+C out of the powershell instance but after this unable to interact with wsl at all, cannot do wsl --shutdown. vmem still shows up in processes, no memory usage fluctuation. Have to fully shutdown the Azure VM which takes ages to deallocate due to the lock up.
We are currently using FSLogix Profile containers but have experienced this issue with and without FSLogix utilisation.
Expected Behavior
Expecting the import to finish which on the odd occasion it does but more often than not, it stalls and becomes unresponsive.
Actual Behavior
there is no failure message, if left (Which we have done for 24 hours) the process is still just sat there doing absolutely nothing.
Diagnostic Logs
No response