rauc: add configuration for QEMU x86 and x86-64

The configuration files are very similar to what is available for
Raspberry Pi 4. In general all the files, except for COMPATIBLE
setting can become identical over time, as we move to GPT partition
identifiers to identify the slots.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

meta-oniro-core/recipes-core/rauc/files/qemux86-64/system.conf

+# SPDX-FileCopyrightText: Huawei Inc.
+#
+# SPDX-License-Identifier: Apache-2.0
+
+[system]
+compatible=QEMU x86-64
+# Use the custom boot loader backend. The handler program is set in the
+# [handlers] section below. This loops in SystemOTA into the update process and
+# delegates slot status and slot active flag responsibilities to it.
+bootloader=custom
+# Keep the RAUC status file in the system data partition, in a directory that
+# is common across revisions of the operating system. In other words, this file
+# is explicitly exempt from the A/B update process.
+statusfile=/run/mount/sysdata/common/status.raucs
+
+# Description of A/B slots used on QEMU.
+# Refer to meta-oniro-core/wic/x-gpt-efi-disk.wks.in for details.
+[slot.system.0]
+device=/dev/sda2
+bootname=A
+
+[slot.system.1]
+device=/dev/sda3
+bootname=B
+
+[keyring]
+path=/etc/rauc/oniro-insecure-cert.pem
+
+[handlers]
+# Use SystemOTA for RAUC pre-install and post-install handlers. This is
+# required for correct operation of the custom boot backend as well as for the
+# operation of the state management handlers as provided by SystemOTA.
+pre-install=/usr/libexec/sysota/rauc-pre-install-handler
+post-install=/usr/libexec/sysota/rauc-post-install-handler
+
+# Use SystemOTA to implement the custom RAUC boot backend. On platforms where
+# RAUC manages the boot loader directly remove this line and set the correct
+# bootloader= in the [system] section.
+bootloader-custom-backend=/usr/libexec/sysota/rauc-custom-boot-handler

meta-oniro-core/recipes-core/rauc/files/qemux86/system.conf

+# SPDX-FileCopyrightText: Huawei Inc.
+#
+# SPDX-License-Identifier: Apache-2.0
+
+[system]
+compatible=QEMU x86
+# Use the custom boot loader backend. The handler program is set in the
+# [handlers] section below. This loops in SystemOTA into the update process and
+# delegates slot status and slot active flag responsibilities to it.
+bootloader=custom
+# Keep the RAUC status file in the system data partition, in a directory that
+# is common across revisions of the operating system. In other words, this file
+# is explicitly exempt from the A/B update process.
+statusfile=/run/mount/sysdata/common/status.raucs
+
+# Description of A/B slots used on QEMU.
+# Refer to meta-oniro-core/wic/x-gpt-efi-disk.wks.in for details.
+[slot.system.0]
+device=/dev/sda2
+bootname=A
+
+[slot.system.1]
+device=/dev/sda3
+bootname=B
+
+[keyring]
+path=/etc/rauc/oniro-insecure-cert.pem
+
+[handlers]
+# Use SystemOTA for RAUC pre-install and post-install handlers. This is
+# required for correct operation of the custom boot backend as well as for the
+# operation of the state management handlers as provided by SystemOTA.
+pre-install=/usr/libexec/sysota/rauc-pre-install-handler
+post-install=/usr/libexec/sysota/rauc-post-install-handler
+
+# Use SystemOTA to implement the custom RAUC boot backend. On platforms where
+# RAUC manages the boot loader directly remove this line and set the correct
+# bootloader= in the [system] section.
+bootloader-custom-backend=/usr/libexec/sysota/rauc-custom-boot-handler

meta-oniro-core/recipes-core/rauc/rauc_%.bbappend

@@ -10,6 +10,8 @@
 # something that SystemOTA should be responsible for (make/model and remodel
 # operations). This should be addressed before re-model is supported.
 FILESEXTRAPATHS:prepend:raspberrypi4-64 := "${THISDIR}/files/raspberrypi4:"
+FILESEXTRAPATHS:prepend:qemux86 := "${THISDIR}/files/qemux86:"
+FILESEXTRAPATHS:prepend:qemux86-64 := "${THISDIR}/files/qemux86-64:"
 
 # Make the RAUC package machine-specific. This lets us put the specific configuration
 # file, which encodes the slot configuration, into it safely.