Testing OVMF changes

Co-developing OVMF and NEMU

There is tight coupling between OVMF and NEMU. This page sets out the steps to correctly test OVMF changes with or without accompanying NEMU changes.

1. Make your OVMF changes and push them to a fork of intel/ovmf-virt
2. In your own fork of intel/nemu modify tools/CI/run_nats.sh modifying:

#OVMF_GIT_REV="2f16693ce32cbe0956ce2dcaa571a32966413855"
#OVMF_GIT_REPO="https://github.com/intel/ovmf-virt"

To point to your edk2 repo and the revision you want to test

3. Optional: Make any NEMU changes you want to test with your OVMF changes
4. Create a new PR with that change for the intel/nemu repository and mark that PR do-not-merge
5. Jenkins will build your OVMF source and run the NEMU test suite against it.
6. If everything works. Create a PR against intel/ovmf-virt and in the PR link to your successful test run.
7. Optional: If you have NEMU changes, update your PR to remove the changes to those variables which will now fetch the released OVMF binary.

Outside of PRs the NEMU source tree should never have those variables set