[Xen-devel] [linux-3.16 baseline-only test] 37985: regressions - FAIL

This run is configured for baseline tests only. flight 37985 linux-3.16 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/37985/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-amd 9

[Xen-devel] [qemu-upstream-4.6-testing test] 62106: tolerable FAIL - PUSHED

flight 62106 qemu-upstream-4.6-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/62106/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-raw 3 host-install(3) broken in 62041 pass in 62106

[Xen-devel] [linux-linus test] 62110: regressions - FAIL

flight 62110 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/62110/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 59254

[Xen-devel] [linux-3.4 test] 62103: regressions - FAIL

flight 62103 linux-3.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/62103/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-winxpsp3 6 xen-bootfail REGR. vs. 30511

[Xen-devel] [linux-3.16 test] 62118: tolerable FAIL - PUSHED

flight 62118 linux-3.16 real [real] http://logs.test-lab.xenproject.org/osstest/logs/62118/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail in 61786 pass in 62118

[Xen-devel] [xen-4.3-testing test] 62128: regressions - FAIL

flight 62128 xen-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/62128/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-raw 9 debian-di-install fail REGR. vs. 60742 Tests which are

[Xen-devel] [qemu-mainline bisection] complete test-amd64-amd64-xl-pvh-intel

branch xen-unstable xen branch xen-unstable job test-amd64-amd64-xl-pvh-intel test xen-boot Tree: linux git://xenbits.xen.org/linux-pvops.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git Tree: qemuu

[Xen-devel] [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops

This demotes an OOPS and likely panic due to a failed non-"safe" MSR access to a WARN_ON_ONCE and a return of zero (in the RDMSR case). We still write a pr_info entry unconditionally for debugging. To be clear, this type of failure should *not* happen. This patch exists to minimize the chance of

[Xen-devel] [PATCH v2 2/2] x86/msr: Set the return value to zero when native_rdmsr_safe fails

This will cause unchecked native_rdmsr_safe failures to return deterministic results. Signed-off-by: Andy Lutomirski --- arch/x86/include/asm/msr.h | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/arch/x86/include/asm/msr.h b/arch/x86/include/asm/msr.h

[Xen-devel] [PATCH v2 0/2] x86/msr: MSR access failure changes

This applies on top of my earlier paravirt MSR series. Changes from v1: - Return zero instead of poison on bad RDMSRs. Andy Lutomirski (2): x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops x86/msr: Set the return value to zero when native_rdmsr_safe fails

[Xen-devel] [xen-4.2-testing test] 62129: tolerable FAIL - PUSHED

flight 62129 xen-4.2-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/62129/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-i386-i386-libvirt-vhd 17 guest-start/debian.repeat fail REGR. vs. 61955

Re: [Xen-devel] [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops

On Sep 20, 2015 5:15 PM, "Linus Torvalds" wrote: > > On Sun, Sep 20, 2015 at 5:02 PM, Andy Lutomirski wrote: > > This demotes an OOPS and likely panic due to a failed non-"safe" MSR > > access to a WARN_ON_ONCE and a return of zero (in the RDMSR

Re: [Xen-devel] [PULL 0/19] xen-2015-09-08-tag

Stefano, I have two questions, #1. Which qemu version is this igd stuff going into? 2.6? #2. Is this igd stuff going into qemu-xen inside xen? Any plan to go into xen 4.6? Thanks Tiejun On 9/9/2015 1:21 AM, Stefano Stabellini wrote: The following changes since commit

Re: [Xen-devel] [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops

On Sun, Sep 20, 2015 at 5:02 PM, Andy Lutomirski wrote: > This demotes an OOPS and likely panic due to a failed non-"safe" MSR > access to a WARN_ON_ONCE and a return of zero (in the RDMSR case). > We still write a pr_info entry unconditionally for debugging. No, this is wrong.

[Xen-devel] [qemu-upstream-4.3-testing test] 62112: tolerable FAIL - PUSHED

flight 62112 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/62112/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate.2 fail in 62045 pass in 62112

[Xen-devel] [linux-3.10 baseline-only test] 37987: trouble: broken/fail/pass

This run is configured for baseline tests only. flight 37987 linux-3.10 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/37987/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run:

[Xen-devel] [linux-3.14 baseline-only test] 37986: regressions - FAIL

This run is configured for baseline tests only. flight 37986 linux-3.14 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/37986/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-midway 11 guest-start

[Xen-devel] [xen-4.4-testing test] 62117: regressions - trouble: blocked/broken/fail/pass

flight 62117 xen-4.4-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/62117/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops 3 host-install(3) broken REGR. vs. 60727

Re: [Xen-devel] vTPM ownership problem

Hi Quan, Thank you in advance. I have set XSM_ENABLE ?=y in xen-4.3.0/Config.mk before install XEN. I remove the vtpmmgr / vtpm disk and build it again. But the problem still exists. Here is vtpmmgr / vtpm instance log. (Including executing tpm_takeownership in domU) *vtpmmgr:* Parsing

[Xen-devel] [ovmf baseline-only test] 37992: all pass

This run is configured for baseline tests only. flight 37992 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/37992/ Perfect :-) All tests in this flight passed version targeted for testing: ovmf 2f667c5488c81924861901d4d7c6f4bb170ffb69 baseline version:

[Xen-devel] [qemu-mainline bisection] complete test-armhf-armhf-xl-vhd

branch xen-unstable xen branch xen-unstable job test-armhf-armhf-xl-vhd test xen-boot Tree: linux git://xenbits.xen.org/linux-pvops.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemuu git://git.qemu.org/qemu.git Tree: xen git://xenbits.xen.org/xen.git *** Found

Re: [Xen-devel] [PATCH RFC] xen: if on Xen, "flatten" the scheduling domain hierarchy

On 09/15/2015 06:50 PM, Dario Faggioli wrote: On Thu, 2015-08-20 at 20:16 +0200, Juergen Groß wrote: On 08/18/2015 05:55 PM, Dario Faggioli wrote: Hey everyone, So, as a followup of what we were discussing in this thread: [Xen-devel] PV-vNUMA issue: topology is misinterpreted by the guest

[Xen-devel] [PATCH] MAINTAINERS: Update VT-x maintainers

MAINTAINERS: Update VT-x maintainers Eddie will not act as a VT-x maintainer anymore. So remove him from the list. Signed-off-by: Kevin Tian CC: Jun Nakajima CC: Eddie Dong diff --git a/MAINTAINERS b/MAINTAINERS index

Re: [Xen-devel] [PATCH v6 16/18] vmx: Add some scheduler hooks for VT-d posted interrupts

> -Original Message- > From: Wu, Feng > Sent: Thursday, September 17, 2015 2:16 PM > To: George Dunlap; Jan Beulich > Cc: Tian, Kevin; Keir Fraser; Andrew Cooper; Dario Faggioli; > xen-devel@lists.xen.org; Wu, Feng > Subject: RE: [Xen-devel] [PATCH v6 16/18] vmx: Add some scheduler hooks

Re: [Xen-devel] [PATCH net-next v2] xen-netfront: always set num queues if possible

From: "Charles (Chas) Williams" <3ch...@gmail.com> Date: Wed, 16 Sep 2015 16:28:25 -0400 > If netfront connects with two (or more) queues and then reconnects with > only one queue it fails to delete or rewrite the multi-queue-num-queues > key and netback will try to use the wrong number of

Re: [Xen-devel] rdmsr_safe in Linux PV (under Xen) gets an #GP:Re: [Fedora-xen] Running fedora xen on top of KVM?

On Fri, Sep 18, 2015 at 12:04 PM, Borislav Petkov wrote: > On Fri, Sep 18, 2015 at 08:20:46AM -0700, Andy Lutomirski wrote: >> In any event, Borislav, you must have typed rdmsr_safe for a reason :) > > Wasn't me: > > 6c62aa4a3c12 ("x86: make amd.c have 64bit support code") > > I

Re: [Xen-devel] [PATCH v7 15/17] vmx: VT-d posted-interrupt core logic handling

> -Original Message- > From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of George > Dunlap > Sent: Friday, September 18, 2015 10:34 PM > To: Dario Faggioli > Cc: Jan Beulich; George Dunlap; Tian, Kevin; Keir Fraser; Andrew Cooper; > xen-devel@lists.xen.org; Wu, Feng >

[Xen-devel] [linux-3.4 baseline-only test] 37988: tolerable FAIL

This run is configured for baseline tests only. flight 37988 linux-3.4 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/37988/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemut-winxpsp3 9 windows-install