From b30c2e4798f1911fea3a7520752e68c4e7a35fdf Mon Sep 17 00:00:00 2001
From: pbarbuda <100234375+pbarbuda@users.noreply.github.com>
Date: Thu, 14 Nov 2024 09:45:26 -0800
Subject: [PATCH] [Docs] Exporting env variables through WSL (#327)

Adds a note about exporting the environment variables for the kernel,
initrd and UEFI firmware through WSL.
---
 Guide/src/dev_guide/getting_started/suggested_dev_env.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Guide/src/dev_guide/getting_started/suggested_dev_env.md b/Guide/src/dev_guide/getting_started/suggested_dev_env.md
index b9c3731849..beea35c81d 100644
--- a/Guide/src/dev_guide/getting_started/suggested_dev_env.md
+++ b/Guide/src/dev_guide/getting_started/suggested_dev_env.md
@@ -333,6 +333,13 @@ You can then run the windows version of OpenVMM by running:
 cargo winrun
 ```
 
+OpenVMM configures some environment variables that specify the default Linux kernel,
+initrd, and UEFI firmware. To make those variables available in Windows, run the following:
+
+```bash
+export WSLENV=$WSLENV:X86_64_OPENVMM_LINUX_DIRECT_KERNEL:X86_64_OPENVMM_LINUX_DIRECT_INITRD:AARCH64_OPENVMM_LINUX_DIRECT_KERNEL:AARCH64_OPENVMM_LINUX_DIRECT_INITRD:X86_64_OPENVMM_UEFI_FIRMWARE:AARCH64_OPENVMM_UEFI_FIRMWARE
+```
+
 ### Speeding up Windows OpenVMM launch
 
 Due to filesystem limitations on WSL, launching OpenVMM directly will be somewhat