Akira Moroo

It downloads over 50 MB of JavaScript. Check if it is downloaded in the Developer Console.

I confirmed the problem on my environment.

I noticed that Linux boot on CH/aarch64 has been broken since 88d7dd2301fa35b8aa806b59922c216a56d0a5b5. It seems to be a PCI related bug.

I test it with CH only.

Here is output: ``` cloud-hypervisor/target/release/cloud-hypervisor --kernel rust-hypervisor-firmware/target/aarch64-unknown-none/debug/hypervisor-fw.bin --disk path=/home/retrage/workloads/bionic-server-cloudimg-arm64.raw --cpus boot=1 --memory size=4G --console off --serial tty -v -v -v --log-file ch-debug.log Booting with FDT Found PCI device vendor=8086 device=d57...

It also needs `InstallMultipleProtocolInterfaces()`, which has variadic arguments. Recent nightly Rust has varargs support for "efiapi", but the pinned version of Rust is too old.

I'm working on adding support for EFI protocol installation here: https://github.com/retrage/rust-hypervisor-firmware/tree/protocol-manager-v2. The existing integration test targets work fine, but Ubuntu 24.04 Noble and Windows don't.

Thank you for reporting the issue. The root cause is that the ImageBase points to unmapped memory address. By PR #85, the firmware tries to load the PE to the...

I tried to reproduce it on Neoverse-N1, with current (20231207) Ubuntu 22.04 Jammy cloud image (sha256sum: d74dc6f9bc92da4dff973bab1b6dab411c7b6a5219fcdbec25413832cb4b23ba), but cannot. Here is a part of the log: ``` Found bootloader: \EFI\BOOT\BOOTAA64.EFI...

I have no idea why we cannot reproduce the issue. We can close this issue when your PR #346 is merged.