From 17f3ebc4423bb03bee64b00cc57d7ada860225e3 Mon Sep 17 00:00:00 2001
From: Gianni Trevisiol <gtrevi@users.noreply.github.com>
Date: Thu, 21 Mar 2024 11:29:27 -0700
Subject: [PATCH] exclude doc

---
 docs/InstallEbpf.md | 35 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 20 deletions(-)

diff --git a/docs/InstallEbpf.md b/docs/InstallEbpf.md
index 6a665d2ded..56b3e78add 100644
--- a/docs/InstallEbpf.md
+++ b/docs/InstallEbpf.md
@@ -112,11 +112,11 @@ has already built the binaries for `x64/Debug` or `x64/Release`.
 
 ### Method 3 (Install files you built yourself, with a VM checkpoint)
 
-This method uses a machine that has already built the binaries for
- the desired build configuration, i.e., `\x64\[Debug|Release|NativeOnlyDebug|NativeOnlyRelease]`.
+This method uses a machine that
+has already built the binaries for `x64/Debug` or `x64/Release`.
 
-Copy the build output in `\x64\[Debug|Release|NativeOnlyDebug|NativeOnlyRelease]` to the host of the test VM and run the following in a Powershell
- command prompt:
+Copy the build output in `\x64\[Debug|Release]` to the host of the test VM and run the following in a Powershell
+command prompt:
 
 1. Create a snapshot of the test VM named **baseline**, by running:
 
@@ -134,37 +134,32 @@ Copy the build output in `\x64\[Debug|Release|NativeOnlyDebug|NativeOnlyRelease]
    New-StoredCredential -Target TEST_VM -Username <VM Administrator> -Password <VM Administrator account password> -Persist LocalMachine
    ```
 
-   > Note that "`TEST_VM`" is literal and is later used to look up the actual VM name; it need not be the name of any actual test VM.
-1. Enter the desired directory (`cd`) where the build artifacts are stored (i.e., `\x64\[Debug|Release|NativeOnlyDebug|NativeOnlyRelease]`).
-1. Modify `test_execution.json` to specify the name of the test VM under the `VMMap` attribute, e.g.:
+   > Note that "`TEST_VM`" is literal and is used in step 5 below; it need not be the name of any actual test VM.
+1. Enter the `\x64\[Debug|Release]` directory (`cd`) where the build artifacts are stored.
+1. Modify `.\vm_list.json` to specify the name of the test VM under `VMList`, eg:
 
     ```json
     {
         ...
 
-        "VMMap":
-        {
-            "MY_VM_RUNNERS":
-            [
-                {
-                    "Name": "<test-vm-name>"
-                }
-            ],
-            ...
-        }
-        ...
+        "VMList":
+        [
+            {
+                "Name": "<test-vm-name>"
+            }
+        ]
     }
     ```
 
 1. Run the following commands to setup to use the credentials saved with `TEST_VM` in step 2,
- for logging into each of the VMs named in `test_execution.json`:
+ for logging into each of the VMs named in `vm_list.json`:
 
     ```ps
     Set-ExecutionPolicy unrestricted -Force
     ```
 
     ```ps
-    .\setup_ebpf_cicd_tests.ps1 -SelfHostedRunnerName MY_VM_RUNNERS
+    .\setup_ebpf_cicd_tests.ps1
     ```
 
 ## Installing eBPF with host-process container