WSL 2 (Your Best Coding Environment)

Here is a concrete, step-by-step example of what setting up and using a WSL 2 Ubuntu image would look like on your MSI GE68Hx Raider. This walkthrough will take you from a standard Windows 11 desktop to a powerful, GPU-accelerated Python coding environment.

The End Result: A Seamless Development Workflow¶

Imagine this: You're sitting at your Windows 11 desktop. You open Visual Studio Code, and it automatically connects to a full Ubuntu environment running in the background. Your terminal is a true Linux Bash shell, your code is stored in the Linux filesystem for maximum speed, and when you run a machine learning script, it leverages your RTX 4070 for CUDA acceleration. All of this happens without ever leaving the Windows interface or needing to dual-boot.

This is the power of WSL 2. Here’s how you get there.

Step 1: Installing WSL 2 and the Ubuntu Image¶

This initial setup is remarkably simple and is the recommended starting point.

Open PowerShell as Administrator: Click your Start Menu, type "PowerShell", right-click on it, and select "Run as administrator".
Run the Magic Command: Type the following command and press Enter.
```
wsl --install
```
What This Command Does: This single command automates several steps:
- It enables the necessary Windows features ("Virtual Machine Platform" and "Windows Subsystem for Linux").
- It downloads and installs the latest Linux kernel.
- It downloads and installs the latest long-term support (LTS) version of Ubuntu by default.
Reboot Your Laptop: After the process is complete, you'll be prompted to restart your computer. Do this to finalize the installation.

Step 2: First Launch and Creating Your Ubuntu User¶

Once your laptop reboots, a terminal window will open automatically to complete the Ubuntu installation. If it doesn't, just find "Ubuntu" in your Start Menu and click it.

Installation: It will take a few moments to set up the files.
Create a UNIX User: You will be prompted to create a username and password. This is for your Ubuntu environment only and does not need to match your Windows credentials. Remember this password, as you'll need it for sudo commands.

You are now inside a genuine Ubuntu command-line environment running on your Windows machine.

Step 3: Setting Up Your Python Development Environment¶

Now, you'll use the Ubuntu terminal to install everything you need for Python coding.

Update Ubuntu's Package Lists: It's crucial to ensure all your packages are up-to-date.
```
sudo apt update && sudo apt upgrade -y
```
Install Python Essentials: Ubuntu comes with Python, but you'll want to ensure you have the tools to manage packages and create virtual environments.
```
sudo apt install python3-pip python3-venv -y
```
Create a Project Folder: It is critical for performance to store your code inside the WSL filesystem. You can access it easily from Windows, but it runs much faster from within Linux.
```
mkdir ~/projects
cd ~/projects
```
Set Up a Virtual Environment:
```
python3 -m venv my_project_env
source my_project_env/bin/activate
```
Your command prompt will now show (my_project_env) indicating the virtual environment is active.

Step 4: Enabling Your RTX 4070 for GPU Computing (CUDA)¶

This is the key step to leverage your powerful hardware for AI/ML or data science.

Install the NVIDIA Driver on Windows: Go to the NVIDIA driver website and install the latest "Game Ready" or "Studio" driver for your RTX 4070. This single Windows driver includes support for WSL 2, so you do not need to install any drivers inside Ubuntu itself.

Install the CUDA Toolkit in Ubuntu: With the Windows driver installed, you now install the CUDA development toolkit inside your Ubuntu environment. Follow the official NVIDIA instructions for "WSL-Ubuntu" to set up the correct repositories and install the toolkit. This typically involves running a series of commands provided by NVIDIA.

# Example commands (ALWAYS get the latest from NVIDIA's website)
wget https://developer.download.nvidia.com/compute/cuda/repos/wsl-ubuntu/x86_64/cuda-wsl-ubuntu.pin
sudo mv cuda-wsl-ubuntu.pin /etc/apt/preferences.d/cuda-repository-pin-600
wget https://developer.download.nvidia.com/compute/cuda/12.4.1/local_installers/cuda-repo-wsl-ubuntu-12-4-local_12.4.1-1_amd64.deb
sudo dpkg -i cuda-repo-wsl-ubuntu-12-4-local_12.4.1-1_amd64.deb
sudo cp /var/cuda-repo-wsl-ubuntu-12-4-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda-toolkit-12-4

Verify the Installation: After installation, you can run the following command inside Ubuntu. If it returns details about your RTX 4070, the GPU is successfully recognized within WSL.
```
nvidia-smi
```

Step 5: Integrating with Visual Studio Code¶

This final step creates a seamless workflow.

Install VS Code on Windows: Download and install VS Code for Windows as you normally would.
Install the WSL Extension: Open VS Code, go to the Extensions view (Ctrl+Shift+X), search for "WSL", and install the official extension from Microsoft.
Connect to Ubuntu: Open your Ubuntu terminal (from the Start Menu) and navigate to your project folder (cd ~/projects). Type the following command:
```
code .
```
What Happens: The first time you do this, VS Code will download a small server component inside your Ubuntu instance. Then, the main VS Code window will reload, and you'll be directly connected to your project folder inside WSL.
- The file explorer on the left shows your Linux files.
- The integrated terminal (Ctrl+`) is your Ubuntu Bash shell, already in the correct folder and with your virtual environment active.
- You can now write and run Python code that executes within Linux, with full access to your RTX 4070's CUDA cores, all from the comfort of a Windows application.

Here’s a breakdown of how WSL 2 manages CPU, RAM, and Disk for your Ubuntu image, and how you can configure it.

The Core Concept: Dynamic Resource Allocation¶

Unlike a traditional virtual machine (like VMware or VirtualBox) where you must pre-allocate a fixed amount of resources (e.g., "this VM gets exactly 4 cores and 8GB of RAM"), WSL 2 dynamically shares your laptop's resources with Windows.

CPU: By default, your Ubuntu instance can access all the CPU cores of your Intel i9 processor. The Windows Hypervisor dynamically schedules processes from both Windows and Ubuntu across all available cores.
RAM: This is the most important one to understand. When your Ubuntu instance starts, it uses a very small amount of RAM. As you run applications inside it (like a compiler, a database, or a web server), WSL 2 will automatically grow its memory usage as needed.

The default maximum limit for this memory growth on Windows 11 is 50% of your total host RAM. On your 32 GB machine, this means Ubuntu can use up to 16 GB of RAM.

How to Configure and Control Resources: The .wslconfig File¶

The primary way to set hard limits on your WSL 2 resources is by creating a special configuration file in your Windows user profile directory.

1. Locate or Create the File:
Open Windows File Explorer and navigate to your user folder, which is typically C:\Users\.
Inside this folder, you need to create a new text file named exactly .wslconfig (note the period at the beginning).

2. Edit the File:
You can open this file with any text editor, like Notepad. The configuration follows a simple INI format.

Here is an example .wslconfig tailored for your MSI GE68Hx Raider (i9, 32 GB RAM, RTX 4070), which balances high performance for development with plenty of resources left for Windows and gaming.

codeIni

# Settings for the WSL 2 virtual machine
[wsl2]

# Set a hard memory limit. 16GB is a powerful amount for development,
# leaving a full 16GB for Windows and gaming.
memory=16GB 

# Limit the number of CPU cores. Your i9 has many. Limiting to 12
# still provides massive power while ensuring Windows is always responsive.
processors=12

# Optional: Set the amount of swap space inside the Linux VM.
swap=4GB

# A newer feature that helps WSL return memory to Windows when it's idle.
# Recommended to set to 'gradual' for a good balance.
autoMemoryReclaim=gradual

Breakdown of the Recommended Configuration for Your Laptop:¶

memory=16GB: This is the most important setting. While the 50% default is sensible, setting a hard limit of 16 GB ensures that even a runaway process inside Ubuntu cannot consume more than half your system's memory, guaranteeing that your Windows applications (or a game running in the background) remain fast and responsive.
processors=12: Your 14^th Gen i9 has a high number of cores and threads. While letting WSL use all of them is fine, explicitly setting a limit like 12 provides more than enough power for even heavy compilation tasks, while guaranteeing that some cores are always prioritized for the Windows host OS. This can lead to a smoother overall desktop experience.
autoMemoryReclaim=gradual: This is a quality-of-life improvement. A common complaint about WSL 2 is that it's great at taking RAM but slow to give it back to Windows after a task is done. This setting tells WSL to be more proactive in releasing cached memory when the CPU is idle, preventing memory bloat over long sessions.

How to Apply the Changes¶

After you save your .wslconfig file, the changes do not apply immediately. You must completely shut down the WSL 2 virtual machine for it to read the new configuration on its next startup.

Open PowerShell or Command Prompt.
Run the shutdown command:

codePowershell
```
wsl --shutdown
```
Wait a few seconds. The next time you open your Ubuntu terminal, it will start up with the new resource limits you defined.

A Note on Disk Space Management¶

Disk space is managed differently. It is not configured in the .wslconfig file.

Your Ubuntu filesystem lives inside a virtual hard disk file, typically named ext4.vhdx.
This file grows automatically as you install software and add files inside Ubuntu.
However, it does not automatically shrink when you delete files from within Ubuntu.

If you find this ext4.vhdx file has become very large and you've since deleted a lot of data, you can manually reclaim the free space. Newer versions of WSL have made this easier:

Shut down WSL: wsl --shutdown
Open PowerShell and run: wsl.exe --manage --set-sparse true (For you, this would likely be wsl.exe --manage Ubuntu --set-sparse true). This command optimizes the virtual disk file.

In summary, for your high-end laptop, creating a .wslconfig file to cap memory at 16GB and processors at 12 is a proactive way to ensure a perfectly balanced system, giving you immense power for your Python work inside Ubuntu without ever compromising the performance of the Windows host.