flight 62015 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62015/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 61745
On 17.09.2015 00:31, Andrew Cooper wrote:
> On 16/09/2015 22:59, Konrad Rzeszutek Wilk wrote:
>> On September 16, 2015 5:41:26 PM EDT, Andrew Cooper
>> wrote:
>>> On 16/09/2015 22:01, Konrad Rzeszutek Wilk wrote:
From: Martin Pohlack
The mechanism to get this is via the XSPLICE_OP
> -Original Message-
> From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of George
> Dunlap
> Sent: Thursday, September 17, 2015 1:08 AM
> To: Wu, Feng
> Cc: Jan Beulich; Tian, Kevin; Keir Fraser; Andrew Cooper; Dario Faggioli;
> xen-devel@lists.xen.org
> Subject: Re: [Xen-deve
> -Original Message-
> From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of George
> Dunlap
> Sent: Thursday, September 17, 2015 12:57 AM
> To: Jan Beulich
> Cc: Wu, Feng; Tian, Kevin; Keir Fraser; Andrew Cooper; Dario Faggioli;
> xen-devel@lists.xen.org
> Subject: Re: [Xen-dev
This run is configured for baseline tests only.
flight 37940 xen-4.5-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37940/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 16 guest-
> -Original Message-
> From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> Sent: Wednesday, September 16, 2015 10:37 PM
> To: Hu, Robert
> Cc: xen-devel@lists.xen.org; ian.campb...@citrix.com; wei.l...@citrix.com;
> Jin, Gordon; Zheng, Di
> Subject: Re: [OSSTest Nested v12 00/21] Introdu
flight 62012 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62012/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate
fail REGR. vs. 60666
tes
> -Original Message-
> From: Xu, Quan
> Sent: Wednesday, September 16, 2015 9:24 PM
> To: andrew.coop...@citrix.com; Dong, Eddie; ian.campb...@citrix.com;
> ian.jack...@eu.citrix.com; jbeul...@suse.com; Nakajima, Jun; k...@xen.org;
> Tian, Kevin; t...@xen.org; Zhang, Yang Z; george.dun...
flight 62021 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62021/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 5 kernel-build fail REGR. vs. 60684
build-amd6
flight 62004 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62004/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate
fail REGR. vs. 61627
t
This run is configured for baseline tests only.
flight 37939 xen-4.4-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37939/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 16 guest-
These hooks match the _safe variants, so name them accordingly.
This will make room for unsafe PV hooks.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/paravirt.h | 33 +
arch/x86/include/asm/paravirt_types.h | 8
arch/x86/kernel/paravirt.
Enabling CONFIG_PARAVIRT had an unintended side effect: rdmsr turned
into rdmsr_safe and wrmsr turned into wrmsr_safe, even on bare
metal. Undo that by using the new unsafe paravirt MSR hooks.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/paravirt.h | 9 +++--
1 file changed, 3 in
Setting CONFIG_PARAVIRT=y has an unintended side effect: it silently
turns all rdmsr and wrmsr operations into the safe variants without
any checks that the operations actually succeed.
This is IMO awful: it papers over bugs. In particular, KVM gueests
might be unwittingly depending on this behav
This adds paravirt hooks for unsafe MSR access. On native, they
call native_{read,write}_msr. On Xen, they use
xen_{read,write}_msr_safe.
Nothing uses them yet for ease of bisection. The next patch will
use them in rdmsrl, wrmsrl, etc.
I intentionally didn't make them OOPS on #GP on Xen. I th
On 16/09/2015 22:59, Konrad Rzeszutek Wilk wrote:
> On September 16, 2015 5:41:26 PM EDT, Andrew Cooper
> wrote:
>> On 16/09/2015 22:01, Konrad Rzeszutek Wilk wrote:
>>> From: Martin Pohlack
>>>
>>> The mechanism to get this is via the XSPLICE_OP and
>>> we add a new subsequent hypercall to retr
On September 16, 2015 5:41:26 PM EDT, Andrew Cooper
wrote:
>On 16/09/2015 22:01, Konrad Rzeszutek Wilk wrote:
>> From: Martin Pohlack
>>
>> The mechanism to get this is via the XSPLICE_OP and
>> we add a new subsequent hypercall to retrieve the
>> binary build-id. The hypercall allows an arbirar
On 16/09/2015 22:01, Konrad Rzeszutek Wilk wrote:
> From: Martin Pohlack
>
> The mechanism to get this is via the XSPLICE_OP and
> we add a new subsequent hypercall to retrieve the
> binary build-id. The hypercall allows an arbirarty
> size (the buffer is provided to the hypervisor) - however
> by
From: Martin Pohlack
The mechanism to get this is via the XSPLICE_OP and
we add a new subsequent hypercall to retrieve the
binary build-id. The hypercall allows an arbirarty
size (the buffer is provided to the hypervisor) - however
by default the toolstack will allocate it up to 128
bytes.
We al
The underlaying toolstack code to do the basic
operations when using the XEN_XSPLICE_op syscalls:
- upload the payload,
- get status of an payload,
- list all the payloads,
- apply, check, and revert the payload.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxc/include/xenctrl.h | 17 ++
The implementation does not actually do any patching.
It just adds the framework for doing the hypercalls,
keeping track of ELF payloads, and the basic operations:
- query which payloads exist,
- query for specific payloads,
- check*1, apply*1, and unload payloads.
*1: Which of course in this
A mechanism is required to binarily patch the running hypervisor with new
opcodes that have come about due to primarily security updates.
This document describes the design of the API that would allow us to
upload to the hypervisor binary patches.
This document has been shapped by the input from:
Changelog (since the RFC and the Seattle Xen presentation)
- Finished off some of the work around the build-id.
- Settled on the preemption mechanism.
- Cleaned the patches a lot up, broke them up to easy
review for maintainers.
*What is xSplice?*
A mechanism to binarily patch the running
A simple tool that allows an system admin to perform
basic xsplice operations:
- Upload a xsplice file (with an unique id)
- List all the xsplice payloads loaded.
- Apply, revert, unload, or check the payload using the
unique id.
- Do all three - upload, check, and apply the
payload in o
flight 61995 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61995/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-vhd9 debian-di-install fail REGR. vs. 60577
test-am
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 queues.
Always write the num-queues field if the backend has multi-queue support.
Signed-off-by: Chas
On Fri, 2015-09-11 at 04:03 -0600, Jan Beulich wrote:
> >>> On 10.09.15 at 18:20, wrote:
> > On Wed, 2015-09-09 at 00:48 -0600, Jan Beulich wrote:
> >> >>> On 08.09.15 at 18:02, wrote:
> >> > I believe the driver does support use of multiple interrupts based on
> >> > the previous explanation
flight 62000 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62000/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 61803
Tests which did not succeed, but a
policydb.c: In function ‘user_read’:
policydb.c:1443:26: error: ‘buf[2]’ may be used uninitialized in this function
[-Werror=maybe-uninitialized]
usrdatum->bounds = le32_to_cpu(buf[2]);
^
cc1: all warnings being treated as errors
Which (as Andrew mentioned) is b
On 16/09/2015 09:47, Ross Lagerwall wrote:
> Since commit 191b3f3344ee ("p2m/ept: enable PML in p2m-ept for
> log-dirty"), the A and D bits of EPT paging entries are set
> unconditionally, regardless of whether PML is enabled or not. This
> causes a regression in Xen 4.6 on some processors due to I
This run is configured for baseline tests only.
flight 37937 xen-4.3-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37937/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 15 gues
On 16/09/2015 18:12, Konrad Rzeszutek Wilk wrote:
> policydb.c: In function ‘user_read’:
> policydb.c:1443:26: error: ‘buf[2]’ may be used uninitialized in this
> function [-Werror=maybe-uninitialized]
> usrdatum->bounds = le32_to_cpu(buf[2]);
> ^
> cc1: all warn
On 16/09/2015 18:19, Anthony PERARD wrote:
> Hi all,
>
> I've start to look at loading the BIOS and the ACPI tables via the
> toolstack instead of having them embedded in the hvmloader binary. This is
> done by using the same mechanics as the one used to load extra ACPI tables
> or SMBIOS.
>
> - li
flight 61996 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61996/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 60869
test-amd64-i386-xl-qemuu-ovm
On Wed, 2015-09-16 at 19:18 +0200, Dario Faggioli wrote:
> On Fri, 2015-09-11 at 16:29 +0800, Feng Wu wrote:
> > One remaining item:
> > Jan has concern about calling vcpu_unblock() in vmx_pre_ctx_switch_pi(),
> > need Dario or George's input about this.
> >
> Hi,
>
> Sorry for the delay in reply
On 09/16/2015 11:34 AM, David Vrabel wrote:
On 16/09/15 16:26, Boris Ostrovsky wrote:
On 08/10/2015 01:16 PM, David Vrabel wrote:
On 10/08/15 17:47, li...@eikelenboom.it wrote:
On 2015-08-10 16:24, David Vrabel wrote:
Commit fcdf31a7c162de0c93a2bee51df4688ab0a348f8 (xen/events/fifo:
Handle li
---
tools/libxc/include/xenguest.h | 4
tools/libxc/xc_hvm_build_x86.c | 46 +-
2 files changed, 41 insertions(+), 9 deletions(-)
diff --git a/tools/libxc/include/xenguest.h b/tools/libxc/include/xenguest.h
index 1a1a185..42acbfd 100644
--- a/tools/li
---
tools/firmware/hvmloader/config.h| 2 +-
tools/firmware/hvmloader/hvmloader.c | 9 -
tools/firmware/hvmloader/seabios.c | 9 +++--
3 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/tools/firmware/hvmloader/config.h
b/tools/firmware/hvmloader/config.h
index 0ddd
Hi all,
I've start to look at loading the BIOS and the ACPI tables via the
toolstack instead of having them embedded in the hvmloader binary. This is
done by using the same mechanics as the one used to load extra ACPI tables
or SMBIOS.
- libxl load the blob into it's memory and add it to
struct
---
tools/firmware/Makefile| 20 +++-
tools/firmware/hvmloader/acpi/Makefile | 8 +---
2 files changed, 24 insertions(+), 4 deletions(-)
diff --git a/tools/firmware/Makefile b/tools/firmware/Makefile
index 6cc86ce..3912a9d 100644
--- a/tools/firmware/Makefile
---
tools/firmware/hvmloader/config.h| 9 +
tools/firmware/hvmloader/hvmloader.c | 25 +
tools/firmware/hvmloader/seabios.c | 24 ++--
3 files changed, 28 insertions(+), 30 deletions(-)
diff --git a/tools/firmware/hvmloader/config.h
b/to
---
tools/libxl/libxl_dom.c | 80 +
1 file changed, 80 insertions(+)
diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
index c2518a3..6c0a257 100644
--- a/tools/libxl/libxl_dom.c
+++ b/tools/libxl/libxl_dom.c
@@ -790,6 +790,32 @@ static
On Fri, 2015-09-11 at 16:29 +0800, Feng Wu wrote:
> This patch includes the following aspects:
> - Handling logic when vCPU is blocked:
> * Add a global vector to wake up the blocked vCPU
> when an interrupt is being posted to it (This part
> was sugguested by Yang Zhang ).
> *
policydb.c: In function ‘user_read’:
policydb.c:1443:26: error: ‘buf[2]’ may be used uninitialized in this function
[-Werror=maybe-uninitialized]
usrdatum->bounds = le32_to_cpu(buf[2]);
^
cc1: all warnings being treated as errors
Which makes no sense, as :
1).
On Thu, Sep 10, 2015 at 9:59 AM, Wu, Feng wrote:
>> >> >> Calling vcpu_unblock() in the middle of context_switch()? Why? And
>> >> >> is this safe?
>> >> >
>> >> > I cannot see anything unsafe so far, can some scheduler maintainer
>> >> > help to confirm it? Dario? George?
>> >>
>> >> But first an
On Mon, Sep 7, 2015 at 1:54 PM, Jan Beulich wrote:
On 25.08.15 at 03:57, wrote:
>> --- a/xen/arch/x86/domain.c
>> +++ b/xen/arch/x86/domain.c
>> @@ -1573,6 +1573,22 @@ static void __context_switch(void)
>> per_cpu(curr_vcpu, cpu) = n;
>> }
>>
>> +static inline void pi_ctxt_switch_from(
On Fri, 2015-09-11 at 16:29 +0800, Feng Wu wrote:
> CC: Keir Fraser
> CC: Jan Beulich
> CC: Andrew Cooper
> CC: Kevin Tian
> CC: George Dunlap
> CC: Dario Faggioli
> Sugguested-by: Dario Faggioli
> Signed-off-by: Feng Wu
> Reviewed-by: Dario Faggioli
>
Ehm, just one thing, for now...
> -
On Tue, Sep 15, 2015 at 5:19 AM, Razvan Cojocaru
wrote:
> A previous version of this patch dealing with support for skipping
> the current instruction when a vm_event response requested it
> computed the instruction length in the hypervisor, adding non-trivial
> code dependencies. This patch allo
On Wed, Sep 16, 2015 at 03:39:18PM +0800, Tiejun Chen wrote:
> Since commit 3848058e7dd6 (vtd/iommu: permit group devices to
> passthrough in relaxed mode) is introduced, we always print
> message as XENLOG_G_WARNING but its not correct in the case of
> strict mode. So here is making this message d
On Wed, Sep 16, 2015 at 04:14:27PM +0100, Julien Grall wrote:
> Hi Konrad,
>
> On 16/09/15 14:45, Konrad Rzeszutek Wilk wrote:
> > policydb.c: In function ‘user_read’:
> > policydb.c:1443:26: error: ‘buf[2]’ may be used uninitialized in this
> > function [-Werror=maybe-uninitialized]
> >
On 09/16/2015 06:57 PM, Tamas K Lengyel wrote:
>
>
> On Tue, Sep 15, 2015 at 5:19 AM, Razvan Cojocaru
> mailto:rcojoc...@bitdefender.com>> wrote:
>
> A previous version of this patch dealing with support for skipping
> the current instruction when a vm_event response requested it
> c
Ian Campbell writes ("Re: [OSSTEST PATCH 00/27] xen.git#staging smoke tests"):
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > One outstanding bikeshed question about naming: I have called the job
> > `xen-unstable-smoke' and the output ref xen.git#smoked. I tripped
> > over the presen
On 16/09/15 16:26, Boris Ostrovsky wrote:
> On 08/10/2015 01:16 PM, David Vrabel wrote:
>> On 10/08/15 17:47, li...@eikelenboom.it wrote:
>>> On 2015-08-10 16:24, David Vrabel wrote:
Commit fcdf31a7c162de0c93a2bee51df4688ab0a348f8 (xen/events/fifo:
Handle linked events when closing a port
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> One outstanding bikeshed question about naming: I have called the job
> `xen-unstable-smoke' and the output ref xen.git#smoked. I tripped
> over the presence or absence of the `d' a few times. Should one of
> these two be renamed, and if so
On 08/10/2015 01:16 PM, David Vrabel wrote:
On 10/08/15 17:47, li...@eikelenboom.it wrote:
On 2015-08-10 16:24, David Vrabel wrote:
Commit fcdf31a7c162de0c93a2bee51df4688ab0a348f8 (xen/events/fifo:
Handle linked events when closing a port) did not handle closing a
port bound to a PIRQ because t
On Wed, Sep 16, 2015 at 04:17:29PM +0100, Ross Lagerwall wrote:
> On 09/16/2015 03:46 PM, Wei Liu wrote:
> >On Wed, Sep 16, 2015 at 09:47:51AM +0100, Ross Lagerwall wrote:
> >>Since commit 191b3f3344ee ("p2m/ept: enable PML in p2m-ept for
> >>log-dirty"), the A and D bits of EPT paging entries are
Hi Konrad,
On 16/09/15 14:45, Konrad Rzeszutek Wilk wrote:
> policydb.c: In function ‘user_read’:
> policydb.c:1443:26: error: ‘buf[2]’ may be used uninitialized in this
> function [-Werror=maybe-uninitialized]
> usrdatum->bounds = le32_to_cpu(buf[2]);
> ^
> cc1
On 09/16/2015 03:46 PM, Wei Liu wrote:
On Wed, Sep 16, 2015 at 09:47:51AM +0100, Ross Lagerwall wrote:
Since commit 191b3f3344ee ("p2m/ept: enable PML in p2m-ept for
log-dirty"), the A and D bits of EPT paging entries are set
unconditionally, regardless of whether PML is enabled or not. This
cau
On Wed, 2015-09-16 at 15:57 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 23/27] make-flight: Provide xen
> -unstable-smoke branch"):
> > On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > > This contains a very limited set of jobs:
> > > build-amd64
> > > buil
On Wed, 2015-09-16 at 15:51 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 23/27] make-flight: Provide xen
> -unstable-smoke branch"):
> > On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > > This contains a very limited set of jobs:
> > > build-amd64
> > > buil
On Wed, Sep 16, 2015 at 10:01:45AM +0100, Andrew Cooper wrote:
> There is no current problem, as both NCAPINTS and pi->hw_cap are 8 entries,
> but the limit should be calculated appropriately so as to avoid hypervisor
> stack corruption if the two do get out of sync.
>
> Signed-off-by: Andrew Coop
Ian Campbell writes ("Re: [OSSTEST PATCH 23/27] make-flight: Provide
xen-unstable-smoke branch"):
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > This contains a very limited set of jobs:
> > build-amd64
> > build-armhf
> > test-amd64-amd64-libvirt
>
> Contrary to the prev
Ian Campbell writes ("Re: [OSSTEST PATCH 24/27] make-flight: mfi-common: Honour
$global_runvars"):
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > Provide a way for the main script to set some runvars on all jobs. We
> > expect this to be mostly set with +=.
>
> You've used this faci
Ian Campbell writes ("Re: [OSSTEST PATCH 23/27] make-flight: Provide
xen-unstable-smoke branch"):
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > This contains a very limited set of jobs:
> > build-amd64
> > build-armhf
> > test-amd64-amd64-libvirt
> > test-amd64-amd64-
On Wed, 2015-09-16 at 15:41 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 16/27] cs-job-create: Permit
> creation of `synth' runvars"):
> > On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > > This will be useful if we want to set hostalloc_* runvars. Normally
> > > w
On Wed, Sep 16, 2015 at 09:47:51AM +0100, Ross Lagerwall wrote:
> Since commit 191b3f3344ee ("p2m/ept: enable PML in p2m-ept for
> log-dirty"), the A and D bits of EPT paging entries are set
> unconditionally, regardless of whether PML is enabled or not. This
> causes a regression in Xen 4.6 on som
Ian Campbell writes ("Re: [OSSTEST PATCH 17/27] mg-show-flight-runvars:
Decorate synth runvar names with ~"):
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > Make mg-show-flight-runvars -a append ~ to the names of synth runvars.
> > (This is consistent with the new syntax in cs-job-cre
Robert Ho writes ("[OSSTest Nested v12 00/21] Introduction of netsted HVM test
job"):
> This patch set adds nested HVM test case for osstest.
Sorry for the delay in reviewing the last few patches in this series.
I've finished with it now. I hope my previous review comments
etc. have been helpful
Ian Campbell writes ("Re: [OSSTEST PATCH 07/27] memoise: New utility"):
> On Wed, 2015-09-16 at 14:58 +0100, Ian Jackson wrote:
> > Also of course this statement was, with my original patch, wrong,
> > because osstest.git didn't contain a copy of any version of the
> > vanilla GPL. I have added a
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Robert Ho writes ("[OSSTest Nested v12 21/21] await_tcp(): check_ip for each
loop iteration"):
> await_tcp usually invoked after a reboot, $ho IP may change,
> especially when $ho 'client name' of DHCP request changes.
> Therefore, await_tcp() check will fail if we don't update $ho->{IP}
> accordi
On Wed, 2015-09-16 at 16:10 +0200, Mike Belopuhov wrote:
> > The work just needs to be done by someone.
> >
>
> If we could use a stub that you'd be fine with -- it will be
> superb, more than we could ask for.
>
> Otherwise I have to pick the Xen committer and year based on
> the git history, i
I don't have further comments on this series.
It's definitely a good idea to have this in for 4.6.
If there are no other comments I suggest we commit this series as soon
as possible.
Wei.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists
On Wed, 2015-09-16 at 15:38 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 07/27] memoise: New utility"):
> > On Wed, 2015-09-16 at 14:58 +0100, Ian Jackson wrote:
> > > Also of course this statement was, with my original patch, wrong,
> > > because osstest.git didn't contain
Ian Campbell writes ("Re: [OSSTEST PATCH 16/27] cs-job-create: Permit creation
of `synth' runvars"):
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > This will be useful if we want to set hostalloc_* runvars. Normally
> > we would want to set those only on flights generated by make-fli
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Add this branch to select_xenbranch. This works like xen-unstable in
> most respects. We are going to sort out the push gate ref plumbing in
> xen.git in the next osstest patch.
>
> Also, use a branch-settings file to set its resource prior
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> The branches and push gates are now:
> xen.git#staging -[xen-unstable-smoke]-> #smoked -[xen-unstable]->
> #master
>
> Deployment note: When this passes the osstest self-push-gate, the main
> xen-unstable flight will start using smoked as an
On Wed, 2015-09-16 at 15:31 +0100, Ian Campbell wrote:
> On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> > This contains a very limited set of jobs:
> > build-amd64
> > build-armhf
> > test-amd64-amd64-libvirt
>
> Contrary to the previous ack -- this will need build-amd64-libvi
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> This contains a very limited set of jobs:
> build-amd64
> build-armhf
> test-amd64-amd64-libvirt
Contrary to the previous ack -- this will need build-amd64-libvirt, won't
it?
___
Xen-d
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Provide a way for the main script to set some runvars on all jobs. We
> expect this to be mostly set with +=.
>
> Signed-off-by: Ian Jackson
You've used this facility in #23, so maybe you want to reorder?
In any case:
Acked-by: Ian Campb
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> This contains a very limited set of jobs:
> build-amd64
> build-armhf
> test-amd64-amd64-libvirt
> test-amd64-amd64-xl-qemuu-debianhvm-i386
> test-armhf-armhf-xl
>
> The debianhvm job exists only in this flight, and is gen
Robert Ho writes ("[OSSTest Nested v12 20/21] Don't lvextend if actually no
more space to extend"):
> Though passes if judgement, the
> overall_limit_pe(\$vg_more_free_pe);
> may final judge no more free_pe to extend.
> So, check if $vg_more_free_pe is 0, if so, we don't lvextend,
> otherwis
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> job_create_test would pass $job to job_create_test_filter_callback but
> then later maybe append -xsm to it. Fix this.
>
> No functional change for existing in-tree code because all existing
> tests of the $job end in *.
>
> Signed-off-by:
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Make it possible to separately specify
> - reuse previous flight's builds of xen.git
> - reuse previous flight's builds of all other stuff
>
> Specifically:
>
> * Match the 4th argument to make-flight with case rather than if. If
>it
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> In the Debian hvm tests, ask branch_debianhvm_arch for the
> architecture to use. This currently prints only amd64.
>
> While we are here, provide some comments about the (somewhat
> confusing) argument conventions of do_hvm_debian_test_one.
On Wed, 16 Sep 2015, Wei Liu wrote:
> On Tue, Sep 15, 2015 at 06:53:53PM +0100, M A Young wrote:
> > On Tue, 15 Sep 2015, Stefano Stabellini wrote:
> >
> > > } else {
> > > +if (!disks[i].readwrite) {
> > > +LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "qem
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> We honour
> hostalloc_maxbonus_variation
> hostalloc_bonus_previousfail
> hostalloc_bonus_sharereuse
> and make them default to their previous values.
Took me a while to grok what was happening with $prevfail_equiv_bonus.
still:
> Sign
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Pass -a to mg-show-flight-runvars. That way when we use the new
> cs-job-create feature to set synth runvars during creation, we will
> see them in the dump.
>
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Make mg-show-flight-runvars -a append ~ to the names of synth runvars.
> (This is consistent with the new syntax in cs-job-create.)
>
> We do this by editing $row->[1] (and $colws[1]) so we can avoid
> disturbing the general column format cal
flight 61991 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61991/
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. 61780
test-armhf-armhf-xl-xs
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> This will be useful if we want to set hostalloc_* runvars. Normally
> we would want to set those only on flights generated by make-flight.
>
> Flights generated by cs-bisection-step or cs-adjust-flight ought not
> to copy them, because cs-bi
On Tue, Sep 15, 2015 at 06:53:53PM +0100, M A Young wrote:
> On Tue, 15 Sep 2015, Stefano Stabellini wrote:
>
> > } else {
> > +if (!disks[i].readwrite) {
> > +LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "qemu-xen doesn't
> > support read-only disk drivers")
This run is configured for baseline tests only.
flight 37936 xen-4.2-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37936/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-winxpsp3 6 xen-bo
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> This eliminates the race with cs-bisection-step (and other
> flight-construction tools which might reuse previous flights, provided
> that they also do not pass previous flight numbers from hand to hand
> with the db unlocked).
>
> Signed-off
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> No functional change.
>
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Thu, Sep 10, 2015 at 17:05 +, Lars Kurth wrote:
>
>
> On 10/09/2015 17:26, "Roger Pau Monné" wrote:
>
> >CCing Lars (the community manager).
> >
> >El 09/09/15 a les 14.11, Mike Belopuhov ha escrit:
> >> Hi,
> >>
> >> We're in the process of porting Xen PVHVM drivers to OpenBSD
> >> and
On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote:
> Previously the flight to delete was simply the one with the lowest
> flight number. Now we sort flights not by their own flight number,
> but by the highest flight number of any referencing flight.
>
> This means that flights whose builds ar
On Wed, Sep 16, 2015 at 09:25:25AM +0100, Ian Campbell wrote:
> On Wed, 2015-09-16 at 14:16 +0800, Chunyan Liu wrote:
>
> For the subject I prefer to avoid "fix " style messages. In this
> case something like "libxl: ensure xs transaction is initialised in
> libxl__device_pci_add_xenstore" would b
On Wed, 2015-09-16 at 15:00 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST v2 3/4] Add support for
> selecting resources based on their properties."):
> > On Wed, 2015-09-16 at 14:50 +0100, Ian Jackson wrote:
> > > As a matter of taste, I would have had propname_check throw ra
1 - 100 of 201 matches
Mail list logo
