Bit more on this:
I created a different VBD-backed VM, containing an Ubuntu 14045 install,
on a CentOS 6.10 host, with Xen 4.10, and a 4.9.127 kernel, where the VM
boots up fine.
Back in my LinuxFromScratch environment I still see the bootloader lig
error message as before
Using to parse /boot/
flight 137719 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137719/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-migrupgrade 22 guest-migrate/src_host/dst_host fail REGR. vs.
127792
test-am
flight 137720 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137720/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-prev 6 xen-buildfail REGR. vs. 133596
build-amd64-pre
Hi Stefano,
On 6/14/19 9:53 PM, Stefano Stabellini wrote:
On Wed, 12 Jun 2019, Julien Grall wrote:
(Moving from xen-users to xen-devel).
On 11/06/2019 23:18, Stefano Stabellini wrote:
I managed to reproduced the issue, and I know how to get past it. Try
using the raw kernel Image (arch/arm64
flight 137721 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137721/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-prev 6 xen-buildfail REGR. vs. 132889
build-amd64-pre
Hi Amit,
Sorry for the late answer.
Title: "xen/arm: domain_build: Black list devices using PPIs"
On 6/2/19 7:04 PM, Amit Singh Tomar wrote:
XEN should not forward PPIs to Dom0 as it only support SPIs.
Reading this sentence, it leads to think that Xen does not support PPIs
at all. However,
Hi,
On 6/12/19 8:44 AM, Jan Beulich wrote:
On 11.06.19 at 20:52, wrote:
Julien Grall writes:
Volodymyr was going to resend the series with documentation (as a
separate patch). But I would be happy to take #1 and #2 assuming that
documentation patch is going to be sent.
Yes, sorry for the de
(+ Lars)
Hi,
On 6/11/19 7:46 PM, Volodymyr Babchuk wrote:
diff --git a/xen/include/asm-arm/tee/optee_msg.h
b/xen/include/asm-arm/tee/optee_msg.h
new file mode 100644
index 00..fe743dbde3
--- /dev/null
+++ b/xen/include/asm-arm/tee/optee_msg.h
@@ -0,0 +1,310 @@
+/* SPDX-License-Identifi
Hi Volodymyr,
On 6/11/19 7:46 PM, Volodymyr Babchuk wrote:
This enumeration controls TEE type for a domain. Currently there is
two possible options: either 'none' or 'optee'.
'none' is the default value and it basically disables TEE support at
all.
'optee' enables access to the OP-TEE running
flight 137723 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137723/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd 4fd6fe044c7407d68435d36c51e2413ba39d6a3a
baseline version:
freebsd 1f3b25e11df
flight 137722 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137722/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-prev 6 xen-buildfail REGR. vs. 130965
build-i386-prev
flight 137724 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137724/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-examine 11 examine-serial/bootloaderfail like 137670
test-amd64-amd64-xl-qemut-win7-amd64
flight 137725 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137725/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 6 kernel-build fail REGR. vs. 129313
Tests which did not
13 matches
Mail list logo