[ovmf test] 175920: regressions - FAIL

flight 175920 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175920/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

Re: [PATCH 0/2] x86/xen: don't return from xen_pv_play_dead()

On 25.11.22 07:32, Juergen Gross wrote: All play_dead() functions but xen_pv_play_dead() don't return to the caller. Adapt xen_pv_play_dead() to behave like the other play_dead() variants. Juergen Gross (2): x86/xen: don't let xen_pv_play_dead() return x86/xen: mark xen_pv_play_dead() as

Re: [PATCH v3 5/8] x86/iommu: make code addressing CVE-2011-1898 no VT-d specific

On 1/16/23 09:04, Xenia Ragiadakou wrote: The variable untrusted_msi indicates whether the system is vulnerable to CVE-2011-1898 due to the absence of interrupt remapping support. AMD iommus with interrupt remapping disabled are also exposed. Therefore move the definition of the variable to

[PATCH v3 7/8] x86/dpci: move hvm_dpci_isairq_eoi() to generic HVM code

The function hvm_dpci_isairq_eoi() has no dependencies on VT-d driver code and can be moved from xen/drivers/passthrough/vtd/x86/hvm.c to xen/drivers/passthrough/x86/hvm.c, along with the corresponding copyrights. Remove the now empty xen/drivers/passthrough/vtd/x86/hvm.c. Since the function is

[PATCH v3 8/8] x86/iommu: make AMD-Vi and Intel VT-d support configurable

Provide the user with configuration control over the IOMMU support by making AMD_IOMMU and INTEL_IOMMU options user selectable and able to be turned off. However, there are cases where the IOMMU support is required, for instance for a system with more than 254 CPUs. In order to prevent users from

[PATCH v3 6/8] x86/iommu: call pi_update_irte through an hvm_function callback

Posted interrupt support in Xen is currently implemented only for the Intel platforms. Instead of calling directly pi_update_irte() from the common hvm code, add a pi_update_irte callback to the hvm_function_table. Then, create a wrapper function hvm_pi_update_irte() to be used by the common hvm

[PATCH v3 5/8] x86/iommu: make code addressing CVE-2011-1898 no VT-d specific

The variable untrusted_msi indicates whether the system is vulnerable to CVE-2011-1898 due to the absence of interrupt remapping support. AMD iommus with interrupt remapping disabled are also exposed. Therefore move the definition of the variable to the common x86 iommu code. Also, since the

[PATCH v3 3/8] x86/iommu: snoop control is allowed only by Intel VT-d

The AMD-Vi driver forces coherent accesses by hardwiring the FC bit to 1. Therefore, given that iommu_snoop is used only when the iommu is enabled, when Xen is configured with only the AMD iommu enabled, iommu_snoop can be reduced to a #define to true. No functional change intended.

[PATCH v3 1/8] x86/iommu: amd_iommu_perdev_intremap is AMD-Vi specific

Move its definition to the AMD-Vi driver and use CONFIG_AMD_IOMMU to guard its usage in common code. Take the opportunity to replace bool_t with bool and 1 with true. No functional change intended. Signed-off-by: Xenia Ragiadakou --- Changes in v3: - the second arg of no_config_param()

[PATCH v3 0/8] Make x86 IOMMU driver support configurable

This series aims to provide a means to render the iommu driver support for x86 configurable. Currently, irrespectively of the target platform, both AMD and Intel iommu drivers are built. This is the case because the existent Kconfig infrastructure does not provide any facilities for finer-grained

[PATCH v3 4/8] x86/acpi: separate AMD-Vi and VT-d specific functions

The functions acpi_dmar_init() and acpi_dmar_zap/reinstate() are VT-d specific while the function acpi_ivrs_init() is AMD-Vi specific. To eliminate dead code, they need to be guarded under CONFIG_INTEL_IOMMU and CONFIG_AMD_IOMMU, respectively. Instead of adding #ifdef guards around the function

[PATCH v3 2/8] x86/iommu: iommu_igfx and iommu_qinval are Intel VT-d specific

Use CONFIG_INTEL_IOMMU to guard the usage of iommu_igfx and iommu_qinval in common code. No functional change intended. Signed-off-by: Xenia Ragiadakou --- Changes in v3: - handle iommu_snoop case in a different patch and update commit msg - use no_config_param() to print a warning when

Re: [PATCH] x86/acpi: fix suspend with Xen

On 13.01.23 20:40, Rafael J. Wysocki wrote: On Fri, Jan 13, 2023 at 3:06 PM Juergen Gross wrote: Commit f1e525009493 ("x86/boot: Skip realmode init code when running as Xen PV guest") missed one code path accessing real_mode_header, leading to dereferencing NULL when suspending the system

Re: [PATCH] x86/paravirt: merge activate_mm and dup_mmap callbacks

On 16.01.23 05:27, Srivatsa S. Bhat wrote: Hi Juergen, On 1/12/23 7:21 AM, Juergen Gross wrote: The two paravirt callbacks .mmu.activate_mm and .mmu.dup_mmap are sharing the same implementations in all cases: for Xen PV guests they are pinning the PGD of the new mm_struct, and for all other

[PATCH v2] x86/hotplug: Do not put offline vCPUs in mwait idle state

From: "Srivatsa S. Bhat (VMware)" Under hypervisors that support mwait passthrough, a vCPU in mwait CPU-idle state remains in guest context (instead of yielding to the hypervisor via VMEXIT), which helps speed up wakeups from idle. However, this runs into problems with CPU hotplug, because the

Re: [PATCH] x86/paravirt: merge activate_mm and dup_mmap callbacks

Hi Juergen, On 1/12/23 7:21 AM, Juergen Gross wrote: > The two paravirt callbacks .mmu.activate_mm and .mmu.dup_mmap are > sharing the same implementations in all cases: for Xen PV guests they > are pinning the PGD of the new mm_struct, and for all other cases > they are a NOP. > I was

[qemu-mainline test] 175911: regressions - trouble: blocked/broken/fail/pass

flight 175911 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/175911/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvopsbroken build-arm64

[xen-unstable-smoke test] 175912: regressions - trouble: blocked/broken/fail

flight 175912 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175912/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 broken build-arm64-xsm

[xen-unstable test] 175907: regressions - FAIL

flight 175907 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/175907/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm6 xen-buildfail REGR. vs. 175734 build-amd64-prev

[qemu-mainline test] 175908: regressions - FAIL

flight 175908 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/175908/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 175743 build-amd64-xsm

[xen-unstable-smoke test] 175910: regressions - trouble: blocked/fail

flight 175910 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175910/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 175746

[PATCH 3/3] xen/arm: Clean-up in p2m_init() and p2m_final_teardown()

With the change in previous patch, the initial 16 pages in the P2M pool is not necessary anymore. Drop them for code simplification. Also the call to p2m_teardown() from arch_domain_destroy() is not necessary anymore since the movement of the P2M allocation out of arch_domain_create(). Drop the

[PATCH 2/3] xen/arm: Defer GICv2 CPU interface mapping until the first access

Currently, the mapping of the GICv2 CPU interface is created in arch_domain_create(). This causes some troubles in populating and freeing of the domain P2M pages pool. For example, a default 16 P2M pages are required in p2m_init() to cope with the P2M mapping of 8KB GICv2 CPU interface area, and

[PATCH 1/3] xen/arm: Reduce redundant clear root pages when teardown p2m

Currently, p2m for a domain will be teardown from two paths: (1) The normal path when a domain is destroyed. (2) The arch_domain_destroy() in the failure path of domain creation. When tearing down p2m from (1), the part to clear and clean the root is only needed to do once rather than for every

[PATCH 0/3] P2M improvements for Arm

There are some clean-up/improvement work that can be done in the Arm P2M code triggered by [1] and [2]. These were found at the 4.17 code freeze period so the issues were not fixed at that time. Therefore do the follow-ups here. Patch#1 addresses one comment in [1]. It was sent earlier and

[xen-unstable-smoke test] 175906: regressions - trouble: blocked/fail

flight 175906 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175906/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 175746

[xen-unstable test] 175890: regressions - FAIL

flight 175890 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/175890/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-prev 6 xen-buildfail REGR. vs. 175734 build-i386-xsm

[qemu-mainline test] 175880: regressions - trouble: blocked/broken/fail/pass

flight 175880 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/175880/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt-qcow2 broken test-armhf-armhf-libvirt-raw

[xen-unstable-smoke test] 175904: regressions - trouble: blocked/fail

flight 175904 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175904/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 175746

[xen-unstable-smoke test] 175900: regressions - trouble: blocked/fail

flight 175900 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175900/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 175746

[ovmf test] 175902: regressions - FAIL

flight 175902 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175902/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175901: regressions - FAIL

flight 175901 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[PATCH] x86/xen: Set MSI_FLAG_PCI_MSIX support in Xen MSI domain

The Xen MSI → PIRQ magic does support MSI-X, so advertise it. (In fact it's better off with MSI-X than MSI, because it's actually broken by design for 32-bit MSI, since it puts the high bits of the PIRQ# into the high 32 bits of the MSI message address, instead of the Extended Destination ID

[ovmf test] 175899: regressions - FAIL

flight 175899 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175899/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175897: regressions - FAIL

flight 175897 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175897/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[xen-unstable-smoke test] 175886: regressions - trouble: blocked/broken/fail/pass

flight 175886 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175886/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl broken build-amd64 6

[ovmf test] 175892: regressions - FAIL

flight 175892 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175892/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

Re: [patch V2 30/46] x86/xen: Wrap XEN MSI management into irqdomain

On Sun, 2023-01-15 at 14:12 +, David Woodhouse wrote: > On Wed, 2020-08-26 at 13:16 +0200, Thomas Gleixner wrote: > > From: Thomas Gleixner > > > > To allow utilizing the irq domain pointer in struct device it is necessary > > to make XEN/MSI irq domain compatible. > > > > While the right

[xen-unstable test] 175861: regressions - FAIL

flight 175861 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/175861/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-prev 6 xen-buildfail REGR. vs. 175734 build-i386-xsm

[ovmf test] 175889: regressions - FAIL

flight 175889 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175889/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[linux-linus test] 175859: regressions - FAIL

flight 175859 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/175859/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-examine 8 reboot fail REGR. vs. 173462

[ovmf test] 175888: regressions - FAIL

flight 175888 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175888/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175887: regressions - FAIL

flight 175887 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175887/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175884: regressions - FAIL

flight 175884 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175884/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[xen-unstable-smoke test] 175874: regressions - FAIL

flight 175874 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175874/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 175746 Tests which

[ovmf test] 175883: regressions - FAIL

flight 175883 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175883/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175882: regressions - FAIL

flight 175882 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175882/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175881: regressions - FAIL

flight 175881 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175881/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175879: regressions - FAIL

flight 175879 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175879/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[qemu-mainline test] 175858: regressions - trouble: blocked/broken/fail/pass

flight 175858 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/175858/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 broken build-amd64-pvops

[ovmf test] 175878: regressions - FAIL

flight 175878 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175878/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

Re: [patch V2 30/46] x86/xen: Wrap XEN MSI management into irqdomain

On Wed, 2020-08-26 at 13:16 +0200, Thomas Gleixner wrote: > From: Thomas Gleixner > > To allow utilizing the irq domain pointer in struct device it is necessary > to make XEN/MSI irq domain compatible. > > While the right solution would be to truly convert XEN to irq domains, this > is an

[ovmf test] 175877: regressions - FAIL

flight 175877 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175877/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

Re: [PATCH v2 5/6] efi: xen: Implement memory descriptor lookup based on hypercall

On Mon, Oct 03, 2022 at 08:01:03PM +0200, Marek Marczykowski-Górecki wrote: > On Mon, Oct 03, 2022 at 01:57:14PM -0400, Demi Marie Obenour wrote: > > On Mon, Oct 03, 2022 at 07:04:02PM +0200, Marek Marczykowski-Górecki wrote: > > > On Mon, Oct 03, 2022 at 06:37:19PM +0200, Ard Biesheuvel wrote: >

[ovmf test] 175876: regressions - FAIL

flight 175876 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175876/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175875: regressions - FAIL

flight 175875 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175875/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175872: regressions - FAIL

flight 175872 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175872/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[RFC PATCH v3 10/10] tools/libs/light: pcid: implement write_bdf command

From: Dmytro Semenets Signed-off-by: Dmytro Semenets --- tools/include/pcid.h | 17 + tools/libs/light/libxl_pci.c | 67 ++- tools/libs/light/libxl_pcid.c | 38 3 files changed, 90 insertions(+), 32 deletions(-) diff --git

[RFC PATCH v3 09/10] tools/libs/light: pcid: implement resource_list command

From: Dmytro Semenets Signed-off-by: Dmytro Semenets --- tools/include/pcid.h | 26 tools/libs/light/libxl_pci.c | 63 ++- tools/libs/light/libxl_pcid.c | 110 + tools/libs/light/libxl_vchan.c | 8 +++

[RFC PATCH v3 04/10] tools/libs/light: pcid: implement list_assignable command

From: Oleksandr Andrushchenko Signed-off-by: Oleksandr Andrushchenko --- tools/include/pcid.h | 19 tools/libs/light/libxl_pci.c | 54 ++--- tools/libs/light/libxl_pcid.c | 56 ++- 3 files changed, 103

[RFC PATCH v3 06/10] tools/light: pci: move assign/revert logic to pcid

From: Volodymyr Babchuk Implement commands MAKE_ASSIGNABLE and REVERT_ASSIGNABLE in pcid in the same way as they were implemented in libxl_pci.c Replace original logic in libxl_pci.c by calling appropriate functions from pcid. This is quite huge patch, as lots of code were moved from

[RFC PATCH v3 02/10] tools/libs/light: Add vchan support to libxl

From: Dmytro Semenets Add possibility to send commands from libxl and execute them on server side. Libxl vchan adds support for JSON messages processing. The using of libxl vchan is preventing the client from libxl from reading and writing from / to the local sysfs directly.To do this, the

[RFC PATCH v3 00/10] PCID server

From: Dmytro Semenets PCID server used if domain has passthrough PCI controller and we wants assign some device to other domain. pcid server should be launched in domain owns the PCI controller and process request from other domains. pcid server needs if domain which owns the PCI controller is

[RFC PATCH v3 01/10] tools: allow vchan XenStore paths more then 64 bytes long

From: Oleksandr Andrushchenko Current vchan implementation, while dealing with XenStore paths, allocates 64 bytes buffer on the stack which may not be enough for some use-cases. Make the buffer longer to respect maximum allowed XenStore path of XENSTORE_ABS_PATH_MAX. Signed-off-by: Oleksandr

[RFC PATCH v3 08/10] tools/libs/light: pcid: implement reset_device command

From: Dmytro Semenets Signed-off-by: Dmytro Semenets --- tools/include/pcid.h | 15 tools/libs/light/libxl_pci.c | 52 +++ tools/libs/light/libxl_pcid.c | 66 +++ 3 files changed, 102 insertions(+), 31 deletions(-)

[RFC PATCH v3 03/10] tools/xl: Add pcid daemon to xl

From: Dmytro Semenets Add draft version of pcid server (based on vchan-node2), which can receive messages from the client. Add essential functionality to handle pcid protocol: - define required constants - prepare for handling remote requests - prepare and send an error packet Signed-off-by:

[RFC PATCH v3 07/10] tools/libs/light: pcid: implement is_device_assigned command

From: Dmytro Semenets Signed-off-by: Dmytro Semenets --- tools/include/pcid.h | 19 tools/libs/light/libxl_pci.c | 43 +++ tools/libs/light/libxl_pcid.c | 34 ++- 3 files changed, 75 insertions(+), 21

[RFC PATCH v3 05/10] tools/light: pci: describe [MAKE|REVERT]_ASSIGNABLE commands

From: Volodymyr Babchuk Add protocol for two more commands, one to make a PCI device assignable, and other - to revert its state back. Signed-off-by: Volodymyr Babchuk --- tools/include/pcid.h | 38 ++ 1 file changed, 38 insertions(+) diff --git

[xen-unstable-smoke test] 175857: regressions - trouble: blocked/broken/pass

flight 175857 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175857/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 broken build-arm64-xsm

[ovmf test] 175871: regressions - FAIL

flight 175871 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175871/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175870: regressions - FAIL

flight 175870 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175870/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175869: regressions - FAIL

flight 175869 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175869/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175868: regressions - FAIL

flight 175868 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175868/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175865: regressions - FAIL

flight 175865 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175865/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386

[ovmf test] 175862: regressions - FAIL

flight 175862 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175862/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 175747 build-i386