Skip to content

v4.1.2
Compare
Choose a tag to compare
@github-actions github-actions released this 16 Aug 01:00
· 308 commits to refs/heads/main since this release
v4.1.2
76bad20
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

  • QemuRunner: Use NVMe for OS boot @makubacki (#661)
    Change Details
      ## Description

    This section in the QEMU documentation provides an overview of block
    device options:

    https://www.qemu.org/docs/master/system/qemu-manpage.html#hxtool-1

    This change uses an NVMe device for the OS boot drive to exercise
    the NVMe driver stack during boot and better reflect more common
    modern use cases.

    Other block devices mapped are left unchanged as I did not see an
    obvious reason to change those right now.

    • Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • Impacts security?
      • Security - Does the change have a direct security impact on an application,
        flow, or firmware?
      • Examples: Crypto algorithm change, buffer overflow fix, parameter
        validation improvement, ...
    • Breaking change?
      • Breaking change - Will anyone consuming this change experience a break
        in build or boot behavior?
      • Examples: Add a new library class, move a module to a different repo, call
        a function in a new library class in a pre-existing module, ...
    • Includes tests?
      • Tests - Does the change include any explicit test code?
      • Examples: Unit tests, integration tests, robot tests, ...
    • Includes documentation?
      • Documentation - Does the change contain explicit documentation additions
        outside direct code modifications (and comments)?
      • Examples: Update readme file, add feature readme file, link to documentation
        on an a separate Web page, ...

    How This Was Tested

    • Build and boot to Windows with PATH_TO_OS set to a QCOW2 formatted image
    • Convert the QCOW2 image to VHD and boot again to Windows with PATH_TO_OS set
    • Verify the device is recognized as a NVMe device in UEFI shell
    • Verify the OS disk drive is reported as NVMe in the OS
      image

    Integration Instructions

    N/A - From a user perspective PATH_TO_OS works similar to before and
    NVMe support is already present in the firmware.



  • .azurepipelines: Centralize and update Windows QEMU version (2023.7.25) @makubacki (#658)
    Change Details
      ## Description

    Updates the Chocolatey package version to 2023.7.25:

    This maps to the following QEMU version:
    QEMU emulator version 8.0.91 (v8.1.0-rc1-12028-g4b7c24e862)

    Updated to move forward from a package almost a year old now
    (2022.8.31) and from QEMU 7.1.x to 8.0.x.

    Since the Windows QEMU installation is performed in two separate
    YAML files, this change places the version in a single JSON file.

    This was preferred to a pipeline variable to track the version in
    repo source control and make it easy to search for the version
    being used in repo source code searches.

    • Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • Impacts security?
      • Security - Does the change have a direct security impact on an application,
        flow, or firmware?
      • Examples: Crypto algorithm change, buffer overflow fix, parameter
        validation improvement, ...
    • Breaking change?
      • Breaking change - Will anyone consuming this change experience a break
        in build or boot behavior?
      • Examples: Add a new library class, move a module to a different repo, call
        a function in a new library class in a pre-existing module, ...
    • Includes tests?
      • Tests - Does the change include any explicit test code?
      • Examples: Unit tests, integration tests, robot tests, ...
    • Includes documentation?
      • Documentation - Does the change contain explicit documentation additions
        outside direct code modifications (and comments)?
      • Examples: Update readme file, add feature readme file, link to documentation
        on an a separate Web page, ...

    How This Was Tested

    Mu Tiano Platforms pipelines:

    Integration Instructions

    Review QEMU 8.0.91 release notes to determine if you're
    impacted by changes in this release.



Full Changelog: v4.1.1...v4.1.2

Contributors

makubacki
Assets 7
Loading