flight 122623 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122623/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen e38e285a51c805cfeee4693962df23e39b3c3bd7
baseline version:
xen 0306
flight 122606 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122606/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm broken
test-amd64-amd64-
flight 122611 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122611/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-qcow2 broken
test-arm64-arm64-libvirt
flight 122608 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122608/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
Hi Marek,
On Sat, May 05, 2018 at 01:03:15AM +0200, Marek Marczykowski-Górecki wrote:
> On Fri, May 04, 2018 at 06:13:25PM -0400, Rich Persaud wrote:
> > > On May 1, 2018, at 08:53, Jason Cooper wrote:
> > >
> > > add the link to xen-users thread of me talking to myself. :-))
> > >
> > >> On T
flight 122613 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122613/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt broken
build-arm64-pvops
flight 122615 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122615/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm broken
test-arm64-arm64-xl
When I'm performing some hypercalls with some "unexpected" parameters
(robustness test) sometimes the guest is explicitly "killed" by xen
calling the domain_crash(), but sometimes the guest just crash without any
explicit message on dmesg or logs.
Are those "plain crashes" an expected behavior by
From: DavidWang
Zhaoxin is a x86 IC designer. Its SOC products support both CPU
virtualization and I/O virtualization, which are compatible with Intel
VMX and VT-d respectively. Zhaoxin has 'Shanghai' CPU vendor ID.
Signed-off-by: DavidWang
---
Delete an unnecessary variable.
xen/arch/x86/cpu/
flight 122618 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122618/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-xsm broken
test-arm64-arm64-xl-credit2
flight 122621 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122621/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-xsm broken
test-arm64-arm64-xl
On Fri, 4 May 2018 15:38:49 +
Lars Kurth wrote:
[...]
>Julien: where would the reset code live then?
>Christopher: would want to avoid Dom0 having access to the config space. The
>VM hosting
>the toolstack will need to exercise control over access to the config space.
>Roger: Another option w
On 04/05/18 19:28, Andrew Cooper wrote:
> We don't advertise SVM in CPUID so a PV guest shouldn't be under the
> impression that it can use SVM functionality, but despite this, it really
> shouldn't see SVME set when reading EFER.
>
> Introduce EFER_KNOWN_MASK to whitelist the features Xen knows a
On 04/05/18 17:10, Jan Beulich wrote:
> While the main problem to be addressed here is the issue of what so far
> was named "vmcb_in_sync" starting out with the wrong value (should have
> been true instead of false, to prevent performing a VMSAVE without ever
> having VMLOADed the vCPU's state), go
On 04/05/18 17:11, Jan Beulich wrote:
> Neither the register values copying nor the trace entry generation need
> doing in assembly. The VMLOAD invocation can also be further deferred
> (and centralized). Therefore replace the svm_asid_handle_vmrun()
> invocation with one of the new helper.
>
> Si
15 matches
Mail list logo