| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| other:win10wsl [2022/08/26 17:55] – [Updating WSL 1 to WSL 2] Improved jypeter | other:win10wsl [2022/08/29 17:01] – [After the base installation] Improved jypeter |
|---|
| |
| ==== Hyper-V requirements ==== | ==== Hyper-V requirements ==== |
| | |
| | <WRAP center round tip 60%> |
| | You can skip reading this WSL //requirement// if you are installing WSL for the first time, and are therefor directly installing WSL 2 |
| | |
| | Come back later if you have problems |
| | </WRAP> |
| | |
| |
| WSL 2 needs the //Virtual Machine Platform// to be enabled on your computer. If you have never used WSL before, you can probably go directly to the [[other:win10wsl#base_installation|Base installation]] section and ''wsl'' should install everything correctly | WSL 2 needs the //Virtual Machine Platform// to be enabled on your computer. If you have never used WSL before, you can probably go directly to the [[other:win10wsl#base_installation|Base installation]] section and ''wsl'' should install everything correctly |
| |
| If you have problems, or if you are updating WSL 1 to WSL 2, use ''systeminfo'' to check the [[https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements?source=recommendations#verify-hardware-compatibility|Hyper-V requirements]] | If you have problems (e.g. [[https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#error-0x80370102-the-virtual-machine-could-not-be-started-because-a-required-feature-is-not-installed|The virtual machine could not be started because a required feature is not installed]]), or if you are updating WSL 1 to WSL 2, type ''systeminfo'' in a PowerShell to check if your machine meets the [[https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements?source=recommendations#verify-hardware-compatibility|Hyper-V requirements]] |
| | |
| | If you get a ''No'' for one of the ''Hyper-V requirements'', check the //virtualization// settings in your [[other:bios#entering_the_bios|computer BIOS]].\\ You can have a look at the [[https://en.wikipedia.org/wiki/X86_virtualization|x86 virtualization]] wikipedia page if you are wondering what ''VT-x'' and ''VT-d'' means for //Intel// processors (''AMD-v'' and ''AMD IOMMU'' for //AMD//) |
| |
| If you get a ''No'' for one of the ''Hyper-V requirements'', check the //virtualization// settings in your [[other:bios#entering_the_bios|computer BIOS]] | Example: HP laptop with an **Intel** CPU, and **virtualization not activated in the BIOS** |
| | * //Hyper-V// section of the ''systeminfo'' output |
| | * <code>Configuration requise pour Hyper-V: Extensions de mode du moniteur d’ordinateur virtuel : Oui |
| | Virtualisation activée dans le microprogramme : Non |
| | Traduction d’adresse de second niveau : Oui |
| | Prévention de l’exécution des données disponible : Oui</code> |
| | * //Virtualization// section of the [[other:bios#entering_the_bios|HP BIOS]]: you need to **enable ''Virtualization Technology (VTx)'' and ''Virtualization Technology for Directed I/O (VTd)''** in the BIOS, save the settings and finish booting |
| | * {{ :other:hp_bios_vtx_vtd.png?direct&600 |}} |
| | * //Hyper-V// section of the ''systeminfo'' output with **virtualization activated in the BIOS** (after activation and reboot) |
| | * <code> Virtualisation activée dans le microprogramme : Oui</code> |
| |
| ===== Base installation ===== | ===== Base installation ===== |
| ===== After the base installation ===== | ===== After the base installation ===== |
| |
| Once you have completed the base installation steps, you'll get a Ubuntu machine, with a //root// and user account (pre-configured to use ''sudo'' for commands that need root access) and lots of pre-installed applications (but no graphics). | After completing the base installation steps, you get a //Ubuntu// machine with: |
| | * a //root// and //user// account |
| | * the //user// account is pre-configured to use ''sudo'' for commands that need root access |
| | * pre-installed base Linux applications |
| | * **no** graphics |
| | * enough to play a bit with a Linux computer and test that the installation is working, but not enough to do some real work |
| |
| ==== Opening a terminal ==== | ==== Opening a terminal ==== |
| ===== Miscellaneous ===== | ===== Miscellaneous ===== |
| |
| ==== Updating WSL 1 to WSL 2 ==== | ==== Upgrading WSL 1 to WSL 2 ==== |
| | |
| | <WRAP center round tip 60%> |
| | You will be able to run existing WSL 1 installations with WSL 2, so upgrading should not be a problem! |
| | </WRAP> |
| |
| === Am I using WSL 1 or WSL 2 ? === | === Determining which version of WSL is installed === |
| |
| If you have never used WSL on this computer (and for **this user**), WSL 2 will be installed directly when you follow the [[other:win10wsl#base_installation|Base installation]] steps | If you have never used WSL on a computer, WSL 2 will be installed directly when you follow the [[other:win10wsl#base_installation|Base installation]] steps |
| |
| If you are not sure if you are currently using WSL 1 or WSL 2, you can check [[https://github.com/MicrosoftDocs/WSL/issues/1599|Is there an easy (PowerShell?) way to get more information about WSL?]] has been answered, or make the following checks | You can determine if your installed Linux distributions are running on WSL 1 or WSL 2 by typing ''wsl -l -v'' in a PowerShell, but if you are not sure if you are currently using WSL 1 or WSL 2 for running Linux, you can check if [[https://github.com/MicrosoftDocs/WSL/issues/1599|Is there an easy (PowerShell?) way to get more information about WSL?]] has been answered, or make the following checks |
| |
| * ''wsl --update'' will give the same output (i.e. the installed Linux kernel version) for both WSL 1 and WSL 2 | * ''wsl --update'' will give the same output (i.e. the installed Linux kernel version) for both WSL 1 and WSL 2 |
| Version du noyau : 5.10.102.1</code> | Version du noyau : 5.10.102.1</code> |
| |
| * ''wsl --status'' will display again the kernel version if you already have WSL 2, but will display a link to the WSL installation page if you are running WSL 1: https://aka.ms/wsl2-install | * ''wsl --status'' will display again the kernel version if you already have WSL 2, but **will display a link to the WSL installation page if you are running WSL 1**: https://aka.ms/wsl2-install |
| * <code>PS C:\Users\jypeter> wsl --status | * <code>PS C:\Users\jypeter> wsl --status |
| Distribution par défaut : Ubuntu | Distribution par défaut : Ubuntu |
| * For WSL 2, you also need to meet the [[other:win10wsl#hyper-v_requirements|Hyper-V requirements]] | * For WSL 2, you also need to meet the [[other:win10wsl#hyper-v_requirements|Hyper-V requirements]] |
| |
| === Updating! === | === Upgrading WSL === |
| |
| |
| [[https://docs.microsoft.com/en-us/windows/wsl/install-manual#step-3---enable-virtual-machine-feature|Activate the Virtual Machine Platform]] (just the //Step 3// instructions) and reboot the computer | [[https://docs.microsoft.com/en-us/windows/wsl/install-manual#step-3---enable-virtual-machine-feature|Activate the Virtual Machine Platform]] (just the //Step 3// instructions) and **reboot the computer** |
| |
| After rebooting, go back to the [[other:win10wsl#updating_wsl_1_to_wsl_2|Am I using WSL 1 or WSL 2 ?]] section above, and check that you are now using WSL 2 | After rebooting, go back to the [[other:win10wsl#determining_which_version_of_wsl_is_installed|Determining which version of WSL is installed]] section above, and check that you are now using WSL 2 |
| |
| ==== Potentially useful stuff ==== | ==== Potentially useful stuff ==== |
