Tags: microsoft/igvm-tooling
Tags
igvm: acpi: Fix the incorrect CPU count in DSDT table (#51) Current ACPI tables for CloudHypervisor assumes that there are 4 vcpus in the system. But that is not the case always and we were seeing spurious warning emitted by CloudHypervisor during guest boot if the number of vcpus were less than 4. cloud-hypervisor: 36.005812s: <vcpu0> WARN:vmm/src/cpu.rs:514 -- Out of range vCPU id: 1 cloud-hypervisor: 36.005982s: <vcpu0> WARN:vmm/src/cpu.rs:514 -- Out of range vCPU id: 2 cloud-hypervisor: 36.006146s: <vcpu0> WARN:vmm/src/cpu.rs:514 -- Out of range vCPU id: 3 The fix is very similar just remove the hardcoded limit of 4vcpus. Signed-off-by: Jinank Jain <jinankjain@microsoft.com>
Add crc32 checksum to the fixed header (#50) * Add crc32 checksum to the fixed header New igvm crate enforces checksum validation. This patch calculates checksum of the headers and add the checksum to the fixed header. Signed-off-by: Muminul Islam <muislam@microsoft.com> * Update test file with checksums Signed-off-by: Muminul Islam <muislam@microsoft.com> --------- Signed-off-by: Muminul Islam <muislam@microsoft.com>
acpi: clh: Remove multiple ACPI table for CLH guest (#44) On the CVM guest kernel side we have figured out a way to unify multiple IGVMs for different CPU configuration into one. Thus, it is about time that we can remove multiple directories that we have under acpi-clh for different CPU configuration and have a single set of ACPI table for CLH guests. Signed-off-by: Jinank Jain <jinankjain@microsoft.com>