diff --git a/docs/InstallEbpf.md b/docs/InstallEbpf.md index 48c53dc770..f827976c15 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 `x64/Debug` or `x64/Release`. +This method uses a machine that has already built the binaries for + the desired build configuration, i.e. `\x64\[Debug|Release|NativeOnlyDebug|NativeOnlyRelease]`. -Copy the build output in `\x64\[Debug|Release]` to the host of the test VM and run the following in a Powershell -command prompt: +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: 1. Create a snapshot of the test VM named **baseline**, by running: @@ -134,20 +134,25 @@ command prompt: New-StoredCredential -Target TEST_VM -Username -Password -Persist LocalMachine ``` - > 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: + > Note that "`TEST_VM`" is literal and is later used to lookup 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.: ```json { ... - "VMList": - [ - { - "Name": "" - } - ] + "VMMap": + { + "TEST_VM": + [ + { + "Name": "" + } + ], + ... + } + ... } ```