[Xen-devel] [linux-next test] 112358: regressions - trouble: blocked/broken/fail/pass

flight 112358 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/112358/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-pvops 2 hosts-allocate broken REGR. vs. 112338 build-arm64-xsm

[Xen-devel] [xen-unstable test] 112357: trouble: blocked/broken/fail/pass

flight 112357 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/112357/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 2 hosts-allocate broken REGR. vs.

Re: [Xen-devel] [PATCH v2 1/2] libxl: Implement the handler to handle unrecoverable AER errors.

On 2017-07-28 17:39:52 +0100, Ian Jackson wrote: > Venu Busireddy writes ("[PATCH v2 1/2] libxl: Implement the handler to handle > unrecoverable AER errors."): > > Implement the callback function to handle unrecoverable AER errors, and > > also the public APIs that can be used to

[Xen-devel] [linux-linus test] 112355: regressions - trouble: blocked/broken/fail/pass

flight 112355 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/112355/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64 2 hosts-allocate broken REGR. vs. 110515 build-arm64-pvops

Re: [Xen-devel] [PATCH v2] xen-disk: use g_new0 to fix build

On Fri, 28 Jul 2017, Olaf Hering wrote: > g_malloc0_n is available since glib-2.24. To allow build with older glib > versions use the generic g_new0, which is already used in many other > places in the code. > > Fixes commit 3284fad728 ("xen-disk: add support for multi-page shared rings") > >

Re: [Xen-devel] [Qemu-devel] [PATCH v2] xen-disk: use g_new0 to fix build

On Fri, 28 Jul 2017, Philippe Mathieu-Daudé wrote: > Hi Olaf, > > On 07/28/2017 10:11 AM, Olaf Hering wrote: > > g_malloc0_n is available since glib-2.24. To allow build with older glib > > versions use the generic g_new0, which is already used in many other > > places in the code. > > Can you

Re: [Xen-devel] Why xen-pirq chip use startup_irq() for .irq_enable?

On 07/27/2017 09:25 PM, shuo.a@intel.com wrote: > On Thu 27.Jul'17 at 12:06:10 -0400, Boris Ostrovsky wrote: >> (Adjusting addressees: David is no longer maintaining Xen code, >> Juergen is) > Thanks Boris. >> >> On 07/27/2017 09:04 AM, shuo.a@intel.com wrote: >>> Hi, >>> Here is a device

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

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

Re: [Xen-devel] [Qemu-devel] [PATCH v2] xen-disk: use g_new0 to fix build

On 28 July 2017 at 21:49, Philippe Mathieu-Daudé wrote: > Hi Olaf, > > On 07/28/2017 10:11 AM, Olaf Hering wrote: >> >> g_malloc0_n is available since glib-2.24. To allow build with older glib >> versions use the generic g_new0, which is already used in many other >> places in

Re: [Xen-devel] [Qemu-devel] [PATCH v2] xen-disk: use g_new0 to fix build

Hi Olaf, On 07/28/2017 10:11 AM, Olaf Hering wrote: g_malloc0_n is available since glib-2.24. To allow build with older glib versions use the generic g_new0, which is already used in many other places in the code. Can you provide information about which distrib/release/version/[packages?]

Re: [Xen-devel] [PATCH 2/4] arm: processor: add ccknownpass field into hsr_cond union

On 07/28/2017 09:31 PM, Julien Grall wrote: Hi, On 07/28/2017 08:43 PM, Volodymyr Babchuk wrote: On ARMv8, one of conditional exceptions (SMC that originates from aarch32 state) have extra field in HCR.ISS encoding: CCKNOWNPASS, bit [19] Indicates whether the instruction might have failed

Re: [Xen-devel] [PATCH 4/4] arm: traps: handle SMC32 in check_conditional_instr()

Hi, On 07/28/2017 08:43 PM, Volodymyr Babchuk wrote: On ARMv8 architecture SMC instruction in aarch32 state can be conditional. version + paragraph please. Also, ARMv8 supports both AArch32 and AArch64. As I said in my answer on "arm: smccc: handle SMCs/HVCs according to SMCCC" ([1]), This

Re: [Xen-devel] [PATCH 3/4] arm: traps: handle unknown exceptions in check_conditional_instr()

Hi, On 07/28/2017 08:43 PM, Volodymyr Babchuk wrote: According to ARM architecture reference manual, exception with version + paragraph unknown reason (HSR.EC == 0) have no valid bits in HSR (apart from HSR.EC), so we can't check if that was caused by conditional instruction. We need

Re: [Xen-devel] [PATCH 2/4] arm: processor: add ccknownpass field into hsr_cond union

Hi, On 07/28/2017 08:43 PM, Volodymyr Babchuk wrote: On ARMv8, one of conditional exceptions (SMC that originates from aarch32 state) have extra field in HCR.ISS encoding: CCKNOWNPASS, bit [19] Indicates whether the instruction might have failed its condition code check. 0 - The

Re: [Xen-devel] [PATCH 1/4] arm: processor: rename iss to res0 in hsr_cond union

Hi, On 07/28/2017 08:43 PM, Volodymyr Babchuk wrote: Name "iss" in this case was used not exactly correctly, because this is only part of HSR.ISS field. ARM refence manual denotes this s/refence/reference/ part of ISS as RES0 when it describes encoding for conditional exceptions. When you

[Xen-devel] [xen-unstable-smoke test] 112365: tolerable trouble: broken/pass - PUSHED

flight 112365 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/112365/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 13

[Xen-devel] [PATCH 4/4] arm: traps: handle SMC32 in check_conditional_instr()

On ARMv8 architecture SMC instruction in aarch32 state can be conditional. Thus, we should not skip it while checking HSR.EC value. For this type of exception special coding of HSR.ISS is used. There is additional flag to check before perfoming standart handling of CCVALID and COND fields.

[Xen-devel] [PATCH 3/4] arm: traps: handle unknown exceptions in check_conditional_instr()

According to ARM architecture reference manual, exception with unknown reason (HSR.EC == 0) have no valid bits in HSR (apart from HSR.EC), so we can't check if that was caused by conditional instruction. We need assume that it is uncoditional. Signed-off-by: Volodymyr Babchuk

[Xen-devel] [PATCH 2/4] arm: processor: add ccknownpass field into hsr_cond union

On ARMv8, one of conditional exceptions (SMC that originates from aarch32 state) have extra field in HCR.ISS encoding: CCKNOWNPASS, bit [19] Indicates whether the instruction might have failed its condition code check. 0 - The instruction was unconditional, or was conditional and passed

[Xen-devel] [PATCH 1/4] arm: processor: rename iss to res0 in hsr_cond union

Name "iss" in this case was used not exactly correctly, because this is only part of HSR.ISS field. ARM refence manual denotes this part of ISS as RES0 when it describes encoding for conditional exceptions. Signed-off-by: Volodymyr Babchuk ---

[Xen-devel] [PATCH 0/4] arm: allign check_conditional_instr() with ARM64 requirements

Hello all, Julien asked me to take a look at check_conditional_instr() in traps.c, because it incorrectly handled SMC32 on ARMv8 architecture. This patch series brings it into accordance with TRM (at least, I hope so). ___ Xen-devel mailing list

Re: [Xen-devel] [Qemu-devel] [PATCH v2] xen-disk: use g_new0 to fix build

On 07/28/2017 08:11 AM, Olaf Hering wrote: > g_malloc0_n is available since glib-2.24. To allow build with older glib s/is/is only/ > versions use the generic g_new0, which is already used in many other > places in the code. > > Fixes commit 3284fad728 ("xen-disk: add support for multi-page

[Xen-devel] [ovmf test] 112356: all pass - PUSHED

flight 112356 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/112356/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 1557f05b37f89d1f3cd41a5543a22533fc68ede6 baseline version: ovmf

[Xen-devel] [qemu-mainline test] 112352: regressions - trouble: blocked/broken/fail/pass

flight 112352 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/112352/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-pvops 2 hosts-allocate broken REGR. vs. 111765 build-arm64-xsm

Re: [Xen-devel] [PATCH v2 1/2] libxl: Implement the handler to handle unrecoverable AER errors.

On 2017-07-28 16:58:13 +0100, Wei Liu wrote: > On Wed, Jul 26, 2017 at 07:16:38PM -0500, Venu Busireddy wrote: > > Implement the callback function to handle unrecoverable AER errors, and > > also the public APIs that can be used to register/unregister the handler. > > When an AER error occurs, the

[Xen-devel] [PATCH v2 2/2] libxl: do not start dom0 qemu for stubdomain when not needed

Do not setup vfb+vkb when no access method was configured. Then check if qemu is really needed. The only not configurable thing forcing qemu running in dom0 after this change are consoles used to save/restore. But even in that case, there is much smaller part of qemu exposed. Signed-off-by:

[Xen-devel] [PATCH v2 1/2] libxl: use xen-blkback for 'vbd' disk types by default

This will allow later to make HVM domain without qemu in dom0 (in addition to the one in stubdomain). Signed-off-by: Marek Marczykowski-Górecki --- This is extracted from v1 of "libxl: do not start dom0 qemu for stubdomain when not needed". Signed-off-by: Marek

Re: [Xen-devel] [PATCH v2 1/2] libxl: Implement the handler to handle unrecoverable AER errors.

Venu Busireddy writes ("[PATCH v2 1/2] libxl: Implement the handler to handle unrecoverable AER errors."): > Implement the callback function to handle unrecoverable AER errors, and > also the public APIs that can be used to register/unregister the handler. > When an AER error occurs, the handler

Re: [Xen-devel] [Qemu-devel] [PATCH] xen-disk: use g_malloc0 to fix build

Olaf Hering writes: > On Fri, Jul 28, Eric Blake wrote: > >> This version is prone to multiplication overflow (well, maybe not, but >> you have to audit for that). Wouldn't it be better to use: > > What could go wrong? > qemu will die either way, I think. An overflow in the

Re: [Xen-devel] [OSSTEST PATCH] arm64: tolerate host allocation failures

On Fri, 28 Jul 2017, Ian Jackson wrote: > We have no working ARM64 hardware right now. Stop blocking things. > > (Arguably this ought to be done in general for all arches, but > actually bugs in the flight construction code can cause this too, and > we wouldn't want such a regression to pass the

Re: [Xen-devel] [PATCH RFC] x86/sysctl: Implement XEN_SYSCTL_get_cpuid_policy

On Thu, Jul 27, 2017 at 06:48:15PM +0100, Andrew Cooper wrote: > Provide a SYSCTL for the toolstack to obtain complete system cpuid policy > information. The CPUID information is serialised as an array of 6x 32bit > integers, and a mechanism is provided to query the maximum number of entries >

Re: [Xen-devel] [PATCH v2 09/13] xen/arm: Add use_iommu flag to xen_arch_domainconfig

Hi, Wei On Fri, Jul 28, 2017 at 7:16 PM, Wei Liu wrote: > On Tue, Jul 25, 2017 at 08:26:51PM +0300, Oleksandr Tyshchenko wrote: >> From: Oleksandr Tyshchenko >> >> This flag is intended to let Xen know that the guest has devices >> which will

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

On Fri, Jul 28, 2017 at 05:17:12PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [PATCH] libxl: do not start dom0 qemu for stubdomain > when not needed"): > > On Fri, Jul 28, 2017 at 06:05:13PM +0200, Marek Marczykowski-Górecki wrote: > > > On Fri, Jul 28, 2017 at 04:17:51PM +0100, Wei Liu

Re: [Xen-devel] [PATCH v4 06/13] libxl: change p9 to use generec add function

On Fri, Jul 28, 2017 at 03:11:34PM +0100, Wei Liu wrote: > On Tue, Jul 18, 2017 at 05:25:23PM +0300, Oleksandr Grytsov wrote: > [...] > > /* Waits for the passed device to reach state XenbusStateInitWait. > > * This is not really useful by itself, but is important when executing > > * hotplug

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

Wei Liu writes ("Re: [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed"): > On Fri, Jul 28, 2017 at 06:05:13PM +0200, Marek Marczykowski-Górecki wrote: > > On Fri, Jul 28, 2017 at 04:17:51PM +0100, Wei Liu wrote: > > > On Thu, Jul 27, 2017 at 12:44:25AM +0200, Marek

Re: [Xen-devel] [PATCH v2 09/13] xen/arm: Add use_iommu flag to xen_arch_domainconfig

On Tue, Jul 25, 2017 at 08:26:51PM +0300, Oleksandr Tyshchenko wrote: > From: Oleksandr Tyshchenko > > This flag is intended to let Xen know that the guest has devices > which will most likely be used for passthrough and as the result > the IOMMU is expected to be

Re: [Xen-devel] [PATCH v2 2/2] xl: Register the AER event handler to handle AER errors.

On Fri, Jul 28, 2017 at 09:06:03AM -0700, Venu Busireddy wrote: > On 2017-07-28 16:58:16 +0100, Wei Liu wrote: > > On Wed, Jul 26, 2017 at 07:16:39PM -0500, Venu Busireddy wrote: > > > When a guest is created, register the AER event handler to handle the > > > AER errors. When an AER error occurs,

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

On Fri, Jul 28, 2017 at 06:05:13PM +0200, Marek Marczykowski-Górecki wrote: > On Fri, Jul 28, 2017 at 04:17:51PM +0100, Wei Liu wrote: > > On Thu, Jul 27, 2017 at 12:44:25AM +0200, Marek Marczykowski-Górecki wrote: > > > diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c > > > index

Re: [Xen-devel] [PATCH v2 2/2] xl: Register the AER event handler to handle AER errors.

On 2017-07-28 16:58:16 +0100, Wei Liu wrote: > On Wed, Jul 26, 2017 at 07:16:39PM -0500, Venu Busireddy wrote: > > When a guest is created, register the AER event handler to handle the > > AER errors. When an AER error occurs, the handler will forcibly remove > > the erring PCIe device from the

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

On Fri, Jul 28, 2017 at 04:17:51PM +0100, Wei Liu wrote: > On Thu, Jul 27, 2017 at 12:44:25AM +0200, Marek Marczykowski-Górecki wrote: > > diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c > > index 44ebd70..c9aefe15 100644 > > --- a/tools/libxl/libxl_dm.c > > +++

Re: [Xen-devel] Xen 4.9 + kernel 4.13rc2 -- ballooning regression? reappearance of "Over-allocation for domain 1" errors

On 7/27/17 11:23 PM, Juergen Gross wrote: Can you please post the domain's config file used to create the domain and the kernel config? Sure. https://pastebin.com/M6cr2pX7 ___ Xen-devel mailing list Xen-devel@lists.xen.org

Re: [Xen-devel] [PATCH v2 2/2] xl: Register the AER event handler to handle AER errors.

On Wed, Jul 26, 2017 at 07:16:39PM -0500, Venu Busireddy wrote: > When a guest is created, register the AER event handler to handle the > AER errors. When an AER error occurs, the handler will forcibly remove > the erring PCIe device from the guest. > > Signed-off-by: Venu Busireddy

Re: [Xen-devel] [PATCH v2 1/2] libxl: Implement the handler to handle unrecoverable AER errors.

On Wed, Jul 26, 2017 at 07:16:38PM -0500, Venu Busireddy wrote: > Implement the callback function to handle unrecoverable AER errors, and > also the public APIs that can be used to register/unregister the handler. > When an AER error occurs, the handler will forcibly remove the erring > PCIe

Re: [Xen-devel] [PATCH OSSTEST 10/11] make-hosts-flight: set runvars for FreeBSD test

Roger Pau Monne writes ("[PATCH OSSTEST 10/11] make-hosts-flight: set runvars for FreeBSD test"): > This is needed in order to run the memdisk test. Acked-by: Ian Jackson Ian. ___ Xen-devel mailing list

Re: [Xen-devel] [PATCH OSSTEST 11/11] sg-run-job: hook the memdisk test into examine

Roger Pau Monne writes ("[PATCH OSSTEST 11/11] sg-run-job: hook the memdisk test into examine"): > Hook the memdisk parameter detection and the saving of the host > properties into the examine jobs. Looking at this: > + run-ts . =ts-memdisk-try-append + host > } >

Re: [Xen-devel] [PATCH OSSTEST 09/11] ts-examine-hostprops-save: introduce a script to save properties

Roger Pau Monne writes ("[PATCH OSSTEST 09/11] ts-examine-hostprops-save: introduce a script to save properties"): > The introduce script turns the properties stored in the runvars using > the format hostprop_$hotname_$prop=$val into host properties stored in > the database. ... > +exit 0 if

Re: [Xen-devel] [PATCH OSSTEST 08/11] ts-memdisk-try-append: introduce a script to test memdisk options

Roger Pau Monne writes ("[PATCH OSSTEST 08/11] ts-memdisk-try-append: introduce a script to test memdisk options"): > The intended usage is to run this script against every host in order > to record the possible needed memdisk flags. Acked-by: Ian Jackson Except that

Re: [Xen-devel] [PATCH OSSTEST 07/11] ts-freebsd-host-install: add option to test memdisk options

Roger Pau Monne writes ("[PATCH OSSTEST 07/11] ts-freebsd-host-install: add option to test memdisk options"): ... > +if ($bootonly) { > +hostprop_putative_record($ho, "MemdiskAppend", $memdisk_append) > +if $memdisk_append; > +exit 0; I think this should be a separate option

Re: [Xen-devel] [PATCH OSSTEST 07/11] ts-freebsd-host-install: add option to test memdisk options

Roger Pau Monne writes ("[PATCH OSSTEST 07/11] ts-freebsd-host-install: add option to test memdisk options"): > This is needed in order to figure out which memdisk options should be > used to boot the images on each specific box. ... > +if ($r{'arch'} !~ m/amd64/g) { > +logm("Arch $r{'arch'}

Re: [Xen-devel] [PATCH OSSTEST 06/11] TestSupport: introduce hostprop_putative_record

Roger Pau Monne writes ("[PATCH OSSTEST 06/11] TestSupport: introduce hostprop_putative_record"): > This is used to store tentative host properties in the runvars of a > job, with the expectation that at some point (ie: at the end of the > job) they will be turned into real properties stored in

Re: [Xen-devel] [PATCH OSSTEST 05/11] mfi-common: move set_freebsd_runvars to mfi-common

Roger Pau Monne writes ("[PATCH OSSTEST 05/11] mfi-common: move set_freebsd_runvars to mfi-common"): > So that it can also be used by make-hosts-flight. No functional change > intended. Acked-by: Ian Jackson ___ Xen-devel

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

On Fri, Jul 28, 2017 at 05:34:42PM +0200, Marek Marczykowski-Górecki wrote: [...] > This patch itself does not break it (yet). Such guest will have all > consoles needed for migration by default. This also means that need_qemu > will always be true in practice. I imagine the next step would be

Re: [Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

Roger Pau Monne writes ("[PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop"): > This is from the code in mg-hosts. Switch cmd_setprops to use the > newly introduced function. I think this needs to be abstracted through jobdb. Certainly these SQL statements operating on the

Re: [Xen-devel] [PATCH v2] xen: Implement hypercall for tracing of program counters

On Wed, Jul 26, 2017 at 12:43:45PM +0200, Felix Schmoll wrote: > > diff --git a/xen/Kconfig b/xen/Kconfig > index 65d491d776..5ed2c9c390 100644 > --- a/xen/Kconfig > +++ b/xen/Kconfig > @@ -38,4 +38,8 @@ config LTO > > If unsure, say N. > > +config TRACE_PC > +bool "Enable tracing

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

On Fri, Jul 28, 2017 at 04:17:51PM +0100, Wei Liu wrote: > On Thu, Jul 27, 2017 at 12:44:25AM +0200, Marek Marczykowski-Górecki wrote: > > Use xen-blkback for 'vbd' disk types by default and do not setup vfb+vkb > > when no access method was configured. Then check if qemu is really > > needed. > >

[Xen-devel] [OSSTEST PATCH] cs-hosts-list: Document the --arches, --kernels and --suites options

These have a rather counterintuitive behaviour which is nevertheless useful. Document it, and the reasoning. CC: Roger Pau Monne Signed-off-by: Ian Jackson --- cs-hosts-list | 37 + 1 file changed, 37

Re: [Xen-devel] [PATCH OSSTEST 02/11] ts-freebsd-host-install: fix image permissions

Roger Pau Monne writes ("[PATCH OSSTEST 02/11] ts-freebsd-host-install: fix image permissions"): > Make sure images copied to the tftp path have the right permissions, > so use dd instead of cp, which will obviously not preserve the > original permissions. Acked-by: Ian Jackson

Re: [Xen-devel] [PATCH OSSTEST 03/11] sg-run-job: fix typo in the examine jobs

Roger Pau Monne writes ("[PATCH OSSTEST 03/11] sg-run-job: fix typo in the examine jobs"): > proc prep-job/host-examine-xen is declared twice, one of them should > be prep-job/host-examine-linux instead. > > Signed-off-by: Roger Pau Monné Thank you. Acked-by: Ian Jackson

[Xen-devel] [PATCH OSSTEST 10/11] make-hosts-flight: set runvars for FreeBSD test

This is needed in order to run the memdisk test. Signed-off-by: Roger Pau Monné --- make-hosts-flight | 3 +++ 1 file changed, 3 insertions(+) diff --git a/make-hosts-flight b/make-hosts-flight index 0152dfe1..d5670857 100755 --- a/make-hosts-flight +++

[Xen-devel] [PATCH OSSTEST 08/11] ts-memdisk-try-append: introduce a script to test memdisk options

The intended usage is to run this script against every host in order to record the possible needed memdisk flags. Signed-off-by: Roger Pau Monné --- ts-memdisk-try-append | 27 +++ 1 file changed, 27 insertions(+) create mode 100755

[Xen-devel] [PATCH OSSTEST 01/11] netboot_memdisk: allow each host to have different append values

Some hosts require "append raw" [0] when booting with memdisk, while others don't. This is based on the hardware/BIOS, and needs to be set on a per-host basis. In order to do this, add a new "MemdiskAppend" host property and make use of it in the setup_netboot_memdisk helper. [0]

[Xen-devel] [PATCH OSSTEST 04/11] TestSupport: introduce set_host_prop

This is from the code in mg-hosts. Switch cmd_setprops to use the newly introduced function. No functional change. Signed-off-by: Roger Pau Monné --- Osstest/TestSupport.pm | 31 ++- mg-hosts | 31 +--

[Xen-devel] [PATCH OSSTEST 00/11] osstest: add support to examine the needed memdisk flags for each host

Hello, This builds on top of my previous osstest FreeBSD support series, and expands the examine flight in order to test which memdisk options should be used for each host. Hopefully all of this will be automatic upon running a examine flight. The required options are detected by

[Xen-devel] [PATCH OSSTEST 02/11] ts-freebsd-host-install: fix image permissions

Make sure images copied to the tftp path have the right permissions, so use dd instead of cp, which will obviously not preserve the original permissions. Signed-off-by: Roger Pau Monné --- ts-freebsd-host-install | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[Xen-devel] [PATCH OSSTEST 03/11] sg-run-job: fix typo in the examine jobs

proc prep-job/host-examine-xen is declared twice, one of them should be prep-job/host-examine-linux instead. Signed-off-by: Roger Pau Monné --- sg-run-job | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sg-run-job b/sg-run-job index b7ce963a..ed1ed3c8

[Xen-devel] [PATCH OSSTEST 09/11] ts-examine-hostprops-save: introduce a script to save properties

The introduce script turns the properties stored in the runvars using the format hostprop_$hotname_$prop=$val into host properties stored in the database. Signed-off-by: Roger Pau Monné --- ts-examine-hostprops-save | 39 +++ 1 file

[Xen-devel] [PATCH OSSTEST 06/11] TestSupport: introduce hostprop_putative_record

This is used to store tentative host properties in the runvars of a job, with the expectation that at some point (ie: at the end of the job) they will be turned into real properties stored in the database. Signed-off-by: Roger Pau Monné --- Osstest/TestSupport.pm | 7

[Xen-devel] [PATCH OSSTEST 11/11] sg-run-job: hook the memdisk test into examine

Hook the memdisk parameter detection and the saving of the host properties into the examine jobs. Signed-off-by: Roger Pau Monné --- sg-run-job | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sg-run-job b/sg-run-job index ed1ed3c8..4df89410 100755 --- a/sg-run-job

[Xen-devel] [PATCH OSSTEST 05/11] mfi-common: move set_freebsd_runvars to mfi-common

So that it can also be used by make-hosts-flight. No functional change intended. Signed-off-by: Roger Pau Monné --- make-freebsd-flight | 31 --- mfi-common | 31 +++ 2 files changed, 31 insertions(+), 31

[Xen-devel] [PATCH OSSTEST 07/11] ts-freebsd-host-install: add option to test memdisk options

This is needed in order to figure out which memdisk options should be used to boot the images on each specific box. Note that upon success the script stores the tentative host property in the runvars. Signed-off-by: Roger Pau Monné --- ts-freebsd-host-install | 27

Re: [Xen-devel] [PATCH] Makefile: Fix uninstall target

On Thu, Jul 27, 2017 at 08:08:27PM +0300, Petre Pircalabu wrote: > Running "make uninstall" does not remove all installed files, a > situation which might cause link related issues if xen is re-installed > in a different location. > In order to make uninstall correctly remove the files it is best

Re: [Xen-devel] [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed

On Thu, Jul 27, 2017 at 12:44:25AM +0200, Marek Marczykowski-Górecki wrote: > Use xen-blkback for 'vbd' disk types by default and do not setup vfb+vkb > when no access method was configured. Then check if qemu is really > needed. > > The only not configurable thing forcing qemu running in dom0

Re: [Xen-devel] [PATCH] xen: avoid deadlock in xenbus

On 28/07/17 17:14, Boris Ostrovsky wrote: > On 07/28/2017 10:53 AM, Juergen Gross wrote: >> When starting the xenwatch thread a theoretical deadlock situation is >> possible: >> >> xs_init() contains: >> >> task = kthread_run(xenwatch_thread, NULL, "xenwatch"); >> if (IS_ERR(task)) >>

Re: [Xen-devel] [PATCH] xen: avoid deadlock in xenbus

On 07/28/2017 10:53 AM, Juergen Gross wrote: > When starting the xenwatch thread a theoretical deadlock situation is > possible: > > xs_init() contains: > > task = kthread_run(xenwatch_thread, NULL, "xenwatch"); > if (IS_ERR(task)) > return PTR_ERR(task); > xenwatch_pid =

Re: [Xen-devel] [PATCH] libvchan: Fix cleanup when xc_gntshr_open failed

On Wed, Jul 26, 2017 at 11:27:14PM +0200, Marek Marczykowski-Górecki wrote: > If xc_gntshr_open failed the only thing to cleanup is free allocated > memory. So instead of calling libxenvchan_close (which assume > valid calculated buffers being mmaped already) free memory and return. > >

Re: [Xen-devel] [PATCH v3 0/3] docs: convert manpages to pod

On Wed, Jul 26, 2017 at 04:39:47PM +0200, Olaf Hering wrote: > To remove the buildtime dependency to pandoc/ghc some manpages are > converted from markdown to pod format. This will provide more manpages > which are referenced in xl(1) and xl.cfg(5). > > This series does not cover

[Xen-devel] [PATCH] xen: avoid deadlock in xenbus

When starting the xenwatch thread a theoretical deadlock situation is possible: xs_init() contains: task = kthread_run(xenwatch_thread, NULL, "xenwatch"); if (IS_ERR(task)) return PTR_ERR(task); xenwatch_pid = task->pid; And xenwatch_thread() does: mutex_lock(_mutex);

Re: [Xen-devel] [PATCH 04/25 v6] xen/arm: vpl011: Add support for vuart in libxl

On 07/28/2017 03:42 PM, Wei Liu wrote: On Fri, Jul 28, 2017 at 03:14:31PM +0100, Julien Grall wrote: Hi Wei, On 07/28/2017 02:49 PM, Wei Liu wrote: On Tue, Jul 25, 2017 at 11:08:24PM +0530, Bhupinder Thakur wrote: Hi, On 18 July 2017 at 17:00, Wei Liu wrote: CC x86

[Xen-devel] [GIT PULL] xen: fixes for 4.13-rc3

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.13b-rc3-tag xen: fixes for 4.13-rc3 It contains three minor cleanups for xen related drivers. Thanks. Juergen drivers/xen/events/events_base.c | 13 +++--

Re: [Xen-devel] [PATCH 04/25 v6] xen/arm: vpl011: Add support for vuart in libxl

On Fri, Jul 28, 2017 at 03:14:31PM +0100, Julien Grall wrote: > Hi Wei, > > On 07/28/2017 02:49 PM, Wei Liu wrote: > > On Tue, Jul 25, 2017 at 11:08:24PM +0530, Bhupinder Thakur wrote: > > > Hi, > > > > > > On 18 July 2017 at 17:00, Wei Liu wrote: > > > > CC x86 maintainers

Re: [Xen-devel] [OSSTEST PATCH v14 21/24] make-flight: Prepare devstack jobs on "openstack*" branches only

Anthony PERARD writes ("[OSSTEST PATCH v14 21/24] make-flight: Prepare devstack jobs on "openstack*" branches only"): > This patch create new jobs *-devstack that will only be added to the > branches openstack*, which will be introduced in the next patch. So no > overall functional change.

Re: [Xen-devel] [OSSTEST PATCH v14 22/24] New branch openstack-ocata

Anthony PERARD writes ("[OSSTEST PATCH v14 22/24] New branch openstack-ocata"): > Testing of the Ocata stable branch of OpenStack against Xen unstable. Thanks for the additonal explanation. Acked-by: Ian Jackson ___

Re: [Xen-devel] [OSSTEST PATCH v14 19/24] TestSupport: Implement target_subunit_cmd a subunit stream parser into substeps

Anthony PERARD writes ("[OSSTEST PATCH v14 19/24] TestSupport: Implement target_subunit_cmd a subunit stream parser into substeps"): > target_subunit_cmd can be used like target_cmd, but the command would > needs to output a subunit v1 stream, which will be parsed and turned > into osstest

Re: [Xen-devel] [OSSTEST PATCH v14 18/24] TestSupport: Introduce target_cmd_stashed

Anthony PERARD writes ("[OSSTEST PATCH v14 18/24] TestSupport: Introduce target_cmd_stashed"): > This works like target_cmd, but takes a ref to a filename as argument > and stash the output of the command then return a path to the stashed > output. > > Signed-off-by: Anthony PERARD

[Xen-devel] [OSSTEST PATCH v14 24/24] openstack tests: Don't run them on arm*

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- make-flight | 1 + 1 file changed, 1 insertion(+) diff --git a/make-flight b/make-flight index cc95529..f615155 100755 --- a/make-flight +++ b/make-flight @@ -224,6 +224,7 @@

[Xen-devel] [OSSTEST PATCH v14 17/24] ts-openstack-deploy: Increase devstack timeout

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-deploy | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ts-openstack-deploy b/ts-openstack-deploy index e7c94a5..875c4a7 100755 --- a/ts-openstack-deploy

[Xen-devel] [OSSTEST PATCH v14 10/24] ts-openstack-deploy: Increase open fd limit for RabbitMQ

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-deploy | 7 +++ 1 file changed, 7 insertions(+) diff --git a/ts-openstack-deploy b/ts-openstack-deploy index 2107760..f677513 100755 --- a/ts-openstack-deploy +++

[Xen-devel] [OSSTEST PATCH v14 18/24] TestSupport: Introduce target_cmd_stashed

This works like target_cmd, but takes a ref to a filename as argument and stash the output of the command then return a path to the stashed output. Signed-off-by: Anthony PERARD --- Notes: Changes in V14: - Use filename for error message instead of file

[Xen-devel] [OSSTEST PATCH v14 14/24] ts-openstack-tempest: Update list of skipped tests

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-tempest | 19 --- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/ts-openstack-tempest b/ts-openstack-tempest index b95043a..ae3662f 100755

[Xen-devel] [SELINUX POLICY PATCH] Update for Xen 4.7

Since Xen 4.7, /dev/xen/privcmd is used instead of /proc/xen/privcmd. Add the device into the policy so `xenstored` can work. Signed-off-by: Anthony PERARD --- policy/modules/kernel/devices.fc | 1 + 1 file changed, 1 insertion(+) diff --git

[Xen-devel] [OSSTEST PATCH v14 22/24] New branch openstack-ocata

Testing of the Ocata stable branch of OpenStack against Xen unstable. OpenStack have many different repo which should be clone/fetch at roughly the same time. This does not matter much for a stable branch of OpenStack, but during development they can be a proposed patch for a repo that depends on

[Xen-devel] [OSSTEST PATCH v14 16/24] ts-logs-capture: Capture OpenStack logs

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-logs-capture | 6 ++ 1 file changed, 6 insertions(+) diff --git a/ts-logs-capture b/ts-logs-capture index 061a118..0e3d267 100755 --- a/ts-logs-capture +++ b/ts-logs-capture @@

[Xen-devel] [OSSTEST PATCH v14 11/24] ts-openstack-deploy: Apply a Tempest patch

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-deploy | 9 + 1 file changed, 9 insertions(+) diff --git a/ts-openstack-deploy b/ts-openstack-deploy index f677513..befe3d3 100755 --- a/ts-openstack-deploy +++

[Xen-devel] [OSSTEST PATCH v14 19/24] TestSupport: Implement target_subunit_cmd a subunit stream parser into substeps

target_subunit_cmd can be used like target_cmd, but the command would needs to output a subunit v1 stream, which will be parsed and turned into osstest substeps. The command can be `| subunit-2to1` in order to turn a subunit v2 stream into v1. Currently, time is not taken into account, and all

[Xen-devel] [OSSTEST PATCH v14 12/24] ts-openstack-deploy: Ignore libvirt-python version and use latest

Devstack is going to try to install a specific version of libvirt-python (currently 2.5.0) but this fail with libvirt installed by osstest. Remove the requirement and use the latest available instead. Signed-off-by: Anthony PERARD Acked-by: Ian Jackson

[Xen-devel] [OSSTEST PATCH v14 21/24] make-flight: Prepare devstack jobs on "openstack*" branches only

This patch create new jobs *-devstack that will only be added to the branches openstack*, which will be introduced in the next patch. So no overall functional change. Here is a list of jobs that a openstack* branch will have: build-amd64 build-amd64-libvirt build-amd64-pvops

[Xen-devel] [OSSTEST PATCH v14 13/24] ts-openstack-tempest: Fix tempest invocation

./run_tempest.sh is deprecated. Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-tempest | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ts-openstack-tempest b/ts-openstack-tempest index

[Xen-devel] [OSSTEST PATCH v14 15/24] ts-openstack-deploy: Move logs to /var/log/openstack

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-deploy | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ts-openstack-deploy b/ts-openstack-deploy index 00f262f..e7c94a5 100755 --- a/ts-openstack-deploy

[Xen-devel] [OSSTEST PATCH v14 23/24] make-flight: Increase dom0_mem for openstack flight

With 4G for dom0_mem, a host running devstack is using about 1.5G of swap. Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- make-flight | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/make-flight b/make-flight

[Xen-devel] [OSSTEST PATCH v14 20/24] ts-openstack-tempest: Use target_subunit_cmd

Signed-off-by: Anthony PERARD Acked-by: Ian Jackson --- ts-openstack-tempest | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ts-openstack-tempest b/ts-openstack-tempest index ae3662f..596142a 100755 ---

  1   2   >