linux/meta-virtualization.git/classes, branch kirkstone

containers: introduce container-host class

2023-03-02T21:25:47+00:00

Introducing a small (at the moment) class that represents configuration and processing required to prepare a target image to be a container host. A recipe that requires container configuration should inherit this class, and the container-host-config package will be added as a RDEPENDS, and install common configuration files. In the future, additional functionality or dependencies will be added here to synchronize the configuration of multiple container host packages. Signed-off-by: Bruce Ashfield

image-oci-umoci: add parameter for stop signal

2022-07-18T12:44:32+00:00

Add an optional parameter that allows to override the stop signal that is used. Signed-off-by: Vasileios Anagnostopoulos Signed-off-by: Bruce Ashfield

image-oci-umoci: properly handle tags other than latest

2022-07-18T12:44:15+00:00

Signed-off-by: Pascal Bach Signed-off-by: Bruce Ashfield

xen: Disable highmem on qemuarm

2022-06-20T16:08:58+00:00

By default, highmem option is enabled for machine types later than virt-2.12. This allows qemu to place devices and RAM in physical address space above 32-bits. This can cause issues as according to the documentation Xen supports up to 12GiB of physical address space. Recently the issue was observed using runqemu, that was causing Linux running on top of Xen to stall when trying to access ECAM space placed by qemu at 256GiB mark. Even though this issue is most probably related to QEMU and not Xen (the investigation showed that it can map ECAM space correctly), it is best to avoid such issues by disabling highmem on qemuarm. Signed-off-by: Michal Orzel Reviewed-by: Bertrand Marquis Reviewed-by: Christopher Clark Signed-off-by: Bruce Ashfield

Revert "xen: Disable PCI on qemuarm with Xen"

2022-06-20T16:08:58+00:00

This reverts commit fb0a7b97db4f419b82309f98a4944ae3330d1e2e. Justification: Commit fb0a7b97db4f removed the PCI node from the qemu device tree due to the issue when trying to access PCI configuration space that was causing Linux running on top of Xen to end up in an infinite loop. The investigation showed that the problem occurs due to qemu placing ECAM space at 256GiB mark. Even though Xen officially supports on arm32 up to 12GiB of physical address space, it is able to map it correctly for dom0. However, when Linux tries to access the ECAM space and the stage2 translation fault occurs, HPFAR register contains incorrect IPA. We can say it is incorrect because using hardware AT instruction or software lookup, we can obtain the correct IPA from the same VA. This can suggest that the problem is related to QEMU fault handling. Instead of removing the PCI node the follow-up commit will disable highmem option in qemu which will cause placing ECAM space in the 32-bit space. Signed-off-by: Michal Orzel Reviewed-by: Bertrand Marquis Reviewed-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen: Disable PCI on qemuarm with Xen

2022-05-18T17:56:43+00:00

Remove the pci node from the qemu device tree when runqemu is used with xen-qemuboot. Linux is ending up in an infinite loop when trying to access PCI configuration space when running on top of Xen on arm32. As we do not need or support any of the devices on PCI on arm32 at the moment, just remove the node from the device tree generated by qemu. The problem does not appear at the moment without Xen and it is unclear why it is with Xen. This will be investigated but in the meantime provide a working configuration for users. Signed-off-by: Bertrand Marquis Signed-off-by: Bruce Ashfield

xen: enable qemuboot for arm32

2022-05-18T17:56:43+00:00

Add required variables to generate a qemuboot devicetree for qemuarm. With this change, Xen and dom0 can be started using runqemu. Xen is started using qemu kernel argument and the devicetree is modified to properly boot dom0 (which is loaded in memory). This is using the same system as qemuarm64. At this stage dom0 is hanging on PCI device scanning. This patch is also using qemuarm64 as machine for arm64 bit instead of aarch64 to allow adding support for other machine (an example a Xilinx board that can be emulated with using an other xen machine). Signed-off-by: Bertrand Marquis Signed-off-by: Bruce Ashfield

qemuboot: Fix command line and enable other machines

2022-05-18T17:56:43+00:00

Fix qemuboot-xen-dtb to properly add dom0 bootargs by using a parameter instead of directly using the QB_XEN_DOM0_BOOTARGS inside the function. When not done, the variable is empty and dom0 bootargs are wrong in the device tree. Use QB_MACHINE to generate a device tree with qemu instead of always using the armv8 machine. This will allow this class to be used for other machines later. Signed-off-by: Bertrand Marquis Signed-off-by: Bruce Ashfield

Revert "qemuboot, xen-image-minimal: enable runqemu for qemuarm Xen images"

2022-05-18T17:56:43+00:00

This reverts commit 1c746a976830ebaf85c7c8c25612bea349b0a7c5. Signed-off-by: Bruce Ashfield

xen images, qemuboot: configure xenbr0 bridge for runqemu, testimage

2022-05-18T17:56:43+00:00

Networking for Xen guest virtual machines is commonly configured via bridging in the host system between a physical interface and the guest virtual interfaces. To make it easier to test networking and use testimage with Xen guest virtual machines, extend the bbclass that provides network configuration for qemu machines for the Xen images to configure a Xen bridge and put eth0 onto it when QB_XEN_HOST_BRIDGE is set. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield