commit | ebb6efe266068994b203e1254b9194db6e7f6f62 | [log] [tgz] |
---|---|---|
author | Noah Gold <nkgold@google.com> | Fri May 20 11:13:59 2022 -0700 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 20 21:06:04 2022 +0000 |
tree | e5df2a80c8490fb3e6f6725b5d1f745e112710e1 | |
parent | 953670c3eaec0a2d0818c757c6bb0f707c35a7f7 [diff] |
x86_64: set reset vector when using bios BIOS expect all the cpus to be pointed at the i386 reset vector before boot. We can't guarantee that a fresh vcpu will be pointed to the reset vector by default, so we should set the reset vector when we're configuring the vcpu when we're using a BIOS. Cherrypick from downstream branch. Actual author: Colin Downs-Razouk <colindr@google.com>. TEST=builds BUG=b:213152505 Change-Id: Idf4e0a200c8141adf5cbb83856cbd57362d84716 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3657811 Reviewed-by: Colin Downs-Razouk <colindr@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Noah Gold <nkgold@google.com> Tested-by: kokoro <noreply+kokoro@google.com>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the Chrome OS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on Chrome OS devices.