Open murtaza64 opened 1 year ago
We need a native Windows user to help out on this one.
WSL currently isn't supported in Parallels on arm Macs
WslRegisterDistribution failed with error: 0x80370102 Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/enablevirtualization
https://kb.parallels.com/129234
WSL 2 is currently supported in Parallels Desktop running only on Mac computers with Intel processors. To run WSL 2 inside a Windows virtual machine in Parallels Desktop, you need to enable nested virtualization. You can enable it as described in KB 116239.
On Mac computers with M series chips, nested virtualization isn't supported yet. That's why you can't run WSL 2 on these computers. We keep working together with our partners from Apple® to support nested virtualization for Mac computers with M series chips.
and also not supported on my amazon vm
@murtaza64 grab me on slack or discord if you want to set up a time to debug this together
ucm version d5e809b, Arch linux, WSL2, Windows 11 Home 22621.2428
I'm facing similar problem, getting following message when running ui
.
start : R}hAG[ߎsł܂� w肳ꂽt@C��B
ꏊ s:1 :1
+ start http?\127.0.0.1?38331\fiLN4qJT-Yon8SKD\ui\projects\gentle-narwh ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Start-Process]AInvalidOperationException
+ FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
Still I could access manually by url http://127.0.0.1:<port>/<hash>/ui/projects/<projects>/main/latest
Steps to reproduce:
ucm
in WSLui
Expected result: ui opens in browser
Observed result: browser is opened but page fails to load
Ubuntu 20.04.5 LTS in WSL2 on Windows 11 build 25281 (insider)
I made sure that networking between WSL and windows is working fine by running
jupyter-lab
, which opens in the browser as expected when running under WSL. I also tried replacing127.0.0.1
with the external IP reported by WSL, but this didn't work either.