flight 111491 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111491/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 18 guest-start/win.repeat fail in 111425
REGR. vs. 110441
Hi Stefano,
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2017年7月7日 4:26
> To: Wei Chen
> Cc: xen-devel@lists.xen.org; sstabell...@kernel.org; Julien Grall
> ; Steve Capper ; Kaly Xin
> From: Gao, Chao
> Sent: Thursday, July 6, 2017 3:58 PM
>
> The problem is for a VF of RC integrated PF (e.g. PF's BDF is 00:02.0),
> we would wrongly use 00:00.0 to search VT-d unit.
>
> If a PF is an extended function, the BDF of a traditional function within the
> same device should be used
flight 111475 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111475/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR. vs. 111403
Hi Thomas,
At 07/07/2017 11:04 AM, Ye Xiaolong wrote:
On 07/07, Dou Liyang wrote:
Hi xiaolong,
Really thanks for your testing.
At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
On 07/06, Thomas Gleixner wrote:
On Thu, 6 Jul 2017, kernel test robot wrote:
commit:
If LMCE is supported by host and ' mca_caps = [ "lmce" ] ' is present
in xl config, the LMCE capability will be exposed in guest MSR_IA32_MCG_CAP.
By default, LMCE is not exposed to guest so as to keep the backwards migration
compatibility.
Signed-off-by: Haozhong Zhang
v7 is based on staging branch and only contains the remaining patches.
Changes in v7:
* (Patch 1) Introduce a general way to restore vMCE parameters.
* (Patch 2) Adapt to the change in patch 1.
* Other patch 3 - 7 remain the same as v5 patch 7 - 11.
Haozhong Zhang (7):
[N ] 1/7
If option '-l' or '--lmce' is specified and the host supports LMCE,
xen-mceinj will inject LMCE to CPU specified by '-c' (or CPU0 if '-c'
is not present).
Signed-off-by: Haozhong Zhang
Acked-by: Wei Liu
---
Cc: Ian Jackson
vMCE parameters in struct xen_domctl_ext_vcpucontext were extended in
the past, and is likely to be extended in the future. When migrating a
PV domain from old Xen, XEN_DOMCTL_set_ext_vcpucontext should handle
the differences.
Instead of adding ad-hoc handling code at each extension, we introduce
If MCG_LMCE_P is present in guest MSR_IA32_MCG_CAP, then allow guest
to read/write MSR_IA32_MCG_EXT_CTL.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/cpu/mcheck/vmce.c | 34
Signed-off-by: Haozhong Zhang
Reviewed-by: Jan Beulich
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/cpu/mcheck/mce.c | 24 +++-
Inject LMCE to guest if the host MCE is LMCE and the affected vcpu is
known. Otherwise, broadcast MCE to all vcpus on Intel host.
Signed-off-by: Haozhong Zhang
Reviewed-by: Jan Beulich
---
Cc: Jan Beulich
Cc: Andrew Cooper
Though XEN_MC_inject_v2 allows injecting MC# to specified CPUs, the
current xc_mca_op() does not use this feature and not provide an
interface to callers. This commit add a new xc_mca_op_inject_v2() that
receives a cpumap providing the set of target CPUs.
Signed-off-by: Haozhong Zhang
On 07/07, Dou Liyang wrote:
>Hi xiaolong,
>
>Really thanks for your testing.
>
>At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
>>On 07/06, Thomas Gleixner wrote:
>>>On Thu, 6 Jul 2017, kernel test robot wrote:
>>>
commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize
Hi xiaolong,
Really thanks for your testing.
At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
On 07/06, Thomas Gleixner wrote:
On Thu, 6 Jul 2017, kernel test robot wrote:
commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize interrupt
mode behind timer init")
This run is configured for baseline tests only.
flight 71661 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71661/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 60e85a39fe49071683f3ac5e208f1582511d26bf
baseline
flight 111466 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111466/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 6 xen-install fail REGR. vs. 111036
On 07/06, Thomas Gleixner wrote:
>On Thu, 6 Jul 2017, kernel test robot wrote:
>
>> commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize
>> interrupt mode behind timer init")
>
>> ++++
>> || 43436935b7 | 03fa63cc96 |
>>
flight 111492 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111492/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-1 46 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 111038
Tests which
flight 111501 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111501/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 48efc1044ba1348ad21db131ffc08bece70db6f9
baseline version:
xtf
This run is configured for baseline tests only.
flight 71659 xen-4.9-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71659/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm 1
On Thu, 07/06 16:50, no-re...@patchew.org wrote:
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Subject: [Qemu-devel] [PATCH 0/3] Qemu: Add Xen vIOMMU interrupt remapping
> function support
> Message-id:
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/3] Qemu: Add Xen vIOMMU interrupt remapping
function support
Message-id: 1498715394-16402-1-git-send-email-tianyu@intel.com
Type: series
=== TEST SCRIPT BEGIN ===
Initialize xenfb properly, as all other backends, from its own
"initialise" function.
Remove the dependency of vkbd on vfb: use qemu_console_lookup_by_index
to find the principal console (to get the size of the screen) instead of
relying on a vfb backend to be available (which adds a dependency
This run is configured for baseline tests only.
flight 71660 qemu-upstream-4.9-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71660/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm 1
On Thu, 29 Jun 2017, Paul Durrant wrote:
> > -Original Message-
> > From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> > Sent: 28 June 2017 19:37
> > To: xen-de...@lists.xenproject.org; qemu-de...@nongnu.org
> > Cc: sstabell...@kernel.org; peter.mayd...@linaro.org; Anthony Perard
>
Will fix, thanks!
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
>
> So why do you want the hardware domain to interact with the ictlr? Could not
> you hide it completely?
>
snip
> What would happen if you enable the interrupt here for the guest? Should not
> you do it when the guest is requesting to enable (see vgic_enable_irqs).
>
>
> Also, how about EOI an
Sent: Thursday, July 06, 2017 13:48
Sent: Thursday, July 06, 2017 12:26
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: Tuesday, July 04, 2017 09:47
>
> On 07/04/2017 05:42 PM, Nick Garnett wrote:
>> I tried installing the tools with an ARM64 chroot also and had a
>> similar issue.
flight 111458 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111458/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 111385
test-armhf-armhf-libvirt-xsm 14
>> The purpose of tegra_interrupt_compat is to maintain a tegra-specific
>> whitelist of interrupt controllers we know how to route. Presumably,
>> there may be custom boards out there that may have additional
>> interrupt routing capabilities that this patch set would not support
>> as-is. I'm
flight 111442 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111442/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
111368
Tests
On Fri, 30 Jun 2017, Wei Chen wrote:
> The legacy smmu binding will be deprecated in favour of the generic
> "iommus" binding. So we need a new helper to parse generic iommu
> bindings. When the system detects the SMMU is using generic iommu
> binding, this helper will be called when this platform
On Thu, 6 Jul 2017, kernel test robot wrote:
> commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize
> interrupt mode behind timer init")
> ++++
> || 43436935b7 | 03fa63cc96 |
>
Hi Roger,
Thanks for your comments. My responses inline.
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
> roger@citrix.com
> Sent: Tuesday, July 4, 2017 3:31 AM
> To: Julien Grall
> Cc: edgar.igles...@xilinx.com;
Sent: Thursday, July 06, 2017 12:26
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: Tuesday, July 04, 2017 09:47
>
> On 07/04/2017 05:42 PM, Nick Garnett wrote:
>> I tried installing the tools with an ARM64 chroot also and had a
>> similar issue. In that case, the package
On Fri, 30 Jun 2017, Wei Chen wrote:
> Each PCI(e) device under a root complex is uniquely identified by its
> Requester ID (AKA RID). A Requester ID is a triplet of a Bus number,
> Device number, and Function number. IOMMUs may distinguish PCI devices
> through sideband data derived from the
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
>
> > > I would prefer for it to remain as it is.
> >
> > This is only practical if it's going to be tested, and tested regularly
> > - not *only* on the final release candidate, right before we sign off
> > on the release. It needs
Posting from gmail, so hopefully it doesn't send it as HTML..
On Thu, Jul 6, 2017 at 3:45 PM, Adam Williamson
wrote:
> On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
>> On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
>> > Hi, folks! A
On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
> > Hi, folks! A while ago, Xen virtualization functionality was added to
> > the criteria and the validation test case set, on the understanding
> > that Oracle would
Sent: Wednesday, July 05, 2017 01:15
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: Tuesday, July 04, 2017 09:47
>
> On 07/04/2017 05:42 PM, Nick Garnett wrote:
>> I tried installing the tools with an ARM64 chroot also and had a
>> similar issue. In that case, the package
On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
> Hi, folks! A while ago, Xen virtualization functionality was added to
> the criteria and the validation test case set, on the understanding
> that Oracle would provide testing for it (and help fix bugs as they
> arose).
>
> For
Hi,
On 07/06/2017 06:42 PM, Stefano Stabellini wrote:
On Thu, 6 Jul 2017, Jan Beulich wrote:
On 05.07.17 at 22:39, wrote:
On 05/07/2017 19:35, Stefano Stabellini wrote:
On Tue, 4 Jul 2017, Jan Beulich wrote:
For one, we could remove the CONFIG_HAS_MEM_ACCESS around
flight 111490 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111490/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 424a269d48386f53c81600620ef3ea1c3b78dbce
baseline version:
xtf
On Thu, 6 Jul 2017, Jan Beulich wrote:
> >>> On 05.07.17 at 22:39, wrote:
> > On 05/07/2017 19:35, Stefano Stabellini wrote:
> >> On Tue, 4 Jul 2017, Jan Beulich wrote:
> >>> For one, we could remove the CONFIG_HAS_MEM_ACCESS around
> >>> them if a broader use is planned.
Roger Pau Monne writes ("Re: [PATCH v4 09/16] osstest: introduce a FreeBSD
build script"):
> On Thu, Jul 06, 2017 at 06:31:02PM +0100, Ian Jackson wrote:
> > Although I have to say, evaling the output of make seems brave.
> > Does BSD make only ever print blather to stderr, then ?
>
> That's a
Roger Pau Monne writes ("Re: [PATCH v4 10/16] osstest: add support for
runtime_IDENT_hostflags"):
> On Thu, Jul 06, 2017 at 04:28:09PM +0100, Ian Jackson wrote:
> > I like the implied interface better than the one which implicitly
> > overwrites all previous runtime hostflags.
>
> Right.
>
> >
On Thu, Jul 06, 2017 at 06:31:02PM +0100, Ian Jackson wrote:
> Roger Pau Monne writes ("Re: [PATCH v4 09/16] osstest: introduce a FreeBSD
> build script"):
> > On Thu, Jul 06, 2017 at 04:25:24PM +0100, Ian Jackson wrote:
> > > Roger Pau Monne writes ("[PATCH v4 09/16] osstest: introduce a FreeBSD
On Thu, Jul 06, 2017 at 04:28:09PM +0100, Ian Jackson wrote:
> Roger Pau Monne writes ("[PATCH v4 10/16] osstest: add support for
> runtime_IDENT_hostflags"):
> > +sub set_runtime_hostflag ($$) {
> > +my ($ident,$value) = @_;
> > +
> > +store_runvar("runtime_${ident}_hostflags", $value);
Roger Pau Monne writes ("Re: [PATCH v4 09/16] osstest: introduce a FreeBSD
build script"):
> On Thu, Jul 06, 2017 at 04:25:24PM +0100, Ian Jackson wrote:
> > Roger Pau Monne writes ("[PATCH v4 09/16] osstest: introduce a FreeBSD
> > build script"):
> > You have a spurious ", " at the end there.
flight 111416 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111416/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 21 guest-start/debian fail REGR. vs. 110515
On Thu, Jul 06, 2017 at 04:25:24PM +0100, Ian Jackson wrote:
> Roger Pau Monne writes ("[PATCH v4 09/16] osstest: introduce a FreeBSD build
> script"):
> You have a spurious ", " at the end there.
>
> In general, I notice that you sometimes add comments like this:
>
> # Reverse the neutron
This run is configured for baseline tests only.
flight 71655 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71655/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 11 guest-start
flight 111425 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111425/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-raw 19 guest-start/debian.repeat fail REGR. vs. 110441
Hi all
I'm checking which commit to tag for Xen 4.8.2. AFAICT there is only
1e8e464febb32 that can be considered a bug fix.
Normally what we do is we branch mini-os.git (stable-4.8) and backport
the commit. However there is only one doc change between the commit
we want and 4.8.1 tag. I propose
>>> On 06.07.17 at 17:34, wrote:
> On 07/06/2017 05:24 PM, Jan Beulich wrote:
> On 06.07.17 at 16:53, wrote:
>>> On 07/06/2017 02:10 PM, Jan Beulich wrote:
>>> On 06.07.17 at 13:50, wrote:
> --- /dev/null
Roger Pau Monne writes ("[PATCH v4 16/16] osstest: hook FreeBSD flight into
cr-daily-branch"):
> Add the missing pieces so that cr-daily-branch knows how to create a
> FreeBSD flight. This has been tested by calling `./cr-daily-branch
> freebsd`.
>
> Note that there are two missing pieces. The
flight 111467 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111467/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-3 21 xtf/test-hvm32-invlpg~shadow fail REGR. vs. 111038
Roger Pau Monne writes ("[PATCH v4 05/16] osstest: introduce a helper to setup
a host to boot using memdisk"):
> The helper allows booting a host from pxelinux using an image
> compatible with memdisk.
>
> Note that this requires having a copy of the memdisk binary (provided
> as part of
Roger Pau Monne writes ("[PATCH v4 15/16] osstest: introduce a script to create
a FreeBSD flight"):
> The logic to create a FreeBSD build job is added to
> make-freebsd-flight. This includes creating a FreeBSD build job, and
> also testing the output of that build job (by creating another build
>
Roger Pau Monne writes ("[PATCH v4 11/16] osstest: introduce a script to set
the runtime hostflags runvar for FreeBSD jobs"):
> Due to the nature of the FreeBSD install media, which is
> self-generated from the ts-freebsd-build script, the hostflags runvar
> set to FreeBSD jobs are related to the
On Tue, Jun 27, 2017 at 01:03:20PM +0300, Oleksandr Grytsov wrote:
> From: Oleksandr Grytsov
>
> Add libxl__device_add functio.
> Almost all devices have similar libxl__device__add function.
> This generic function implements same functionality but
> using the
Roger Pau Monne writes ("[PATCH v4 14/16] osstest: add support for FreeBSD
buildjobs to sg-run-job"):
> Add support and introduce a FreeBSD build job to sg-run-job.
...
> proc allocate-build-host {ostype} {
> global jobinfo
> +if {[string equal $ostype FREEBSD]} {
> +run-ts
Roger Pau Monne writes ("[PATCH v4 13/16] osstest: change the meaning of
need_build_host"):
> Make need_build_host store a string instead of a boolean. This is
> later going to be expanded to handle the FreeBSD build jobs.
...
> -if {$need_build_host} { catching-otherwise broken
Hi Jan,
On 07/06/2017 05:22 PM, Jan Beulich wrote:
On 06.07.17 at 16:38, wrote:
>> On 07/06/2017 02:18 PM, Jan Beulich wrote:
>> On 06.07.17 at 13:50, wrote:
@@ -128,7 +131,7 @@ static inline int generic_fls64(__u64 x)
Hi Jan,
On 07/06/2017 05:24 PM, Jan Beulich wrote:
On 06.07.17 at 16:53, wrote:
>> On 07/06/2017 02:10 PM, Jan Beulich wrote:
>> On 06.07.17 at 13:50, wrote:
--- /dev/null
+++ b/xen/include/xen/page-defs.h
@@ -0,0 +1,24
Roger Pau Monne writes ("[PATCH v4 12/16] osstest: allow catching-otherwise to
pass arguments to the called script"):
> Allow catching-otherwise to take a variable number of tail arguments,
> that will be propagated to the called proc.
Err, this is not necessary, I think. The caller can do it.
Roger Pau Monne writes ("[PATCH v4 11/16] osstest: introduce a script to set
the runtime hostflags runvar for FreeBSD jobs"):
> Due to the nature of the FreeBSD install media, which is
> self-generated from the ts-freebsd-build script, the hostflags runvar
> set to FreeBSD jobs are related to the
On Tue, Jun 27, 2017 at 01:03:19PM +0300, Oleksandr Grytsov wrote:
> From: Oleksandr Grytsov
>
> Add libxl__device_list, libxl__device_list_free.
> Device list is created from libxl xen store entries.
> In order to fill libxl device structure from xen store,
> the
On 07/06/2017 04:21 PM, Jan Beulich wrote:
On 06.07.17 at 16:02, wrote:
>> On 07/06/2017 01:34 PM, Jan Beulich wrote:
>> On 06.07.17 at 12:57, wrote:
On 07/06/2017 10:20 AM, Jan Beulich wrote:
> fuzz_insn_fetch() is the only
Roger Pau Monne writes ("[PATCH v4 10/16] osstest: add support for
runtime_IDENT_hostflags"):
> This is required for FreeBSD, that will need to set some of the
> hostflags at runtime. The current IDENT_hostflags will be keep as-is,
> and they should only be set at job creation time.
>
> Also
Roger Pau Monne writes ("[PATCH v4 09/16] osstest: introduce a FreeBSD build
script"):
> In order to generate the FreeBSD installer image and the install
> media.
> +sub install_deps () {
> +target_install_packages($ho, 'git');
Please say
+target_install_packages($ho, qw(git));
> +
>>> On 06.07.17 at 16:53, wrote:
> On 07/06/2017 02:10 PM, Jan Beulich wrote:
> On 06.07.17 at 13:50, wrote:
>>> --- /dev/null
>>> +++ b/xen/include/xen/page-defs.h
>>> @@ -0,0 +1,24 @@
>>> +#ifndef __XEN_PAGE_DEFS_H__
>>> +#define
>>> On 06.07.17 at 16:38, wrote:
> On 07/06/2017 02:18 PM, Jan Beulich wrote:
> On 06.07.17 at 13:50, wrote:
>>> @@ -128,7 +131,7 @@ static inline int generic_fls64(__u64 x)
>>> static __inline__ int get_bitmask_order(unsigned int count)
>>>
>>> On 06.07.17 at 16:02, wrote:
> On 07/06/2017 01:34 PM, Jan Beulich wrote:
> On 06.07.17 at 12:57, wrote:
>>> On 07/06/2017 10:20 AM, Jan Beulich wrote:
fuzz_insn_fetch() is the only data access helper where it is possible
to
flight 111470 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111470/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 60e85a39fe49071683f3ac5e208f1582511d26bf
baseline version:
ovmf
Roger Pau Monne writes ("[PATCH v4 06/16] osstest: add a FreeBSD host install
recipe"):
> The installation is performed using the bsdinstall tool, which is part
> of the FreeBSD base system. The installer image is setup with the
> osstest ssh keys and sshd enabled by default, which allows the
Roger Pau Monne writes ("[PATCH v4 08/16] osstest: add support for the FreeBSD
package manager"):
> FreeBSD support is added to target_install_packages and
> target_install_packages_norec, although there's no equivalent to the
> --no-install-recommends in the FreeBSD package manager.
LGTM, just
Roger Pau Monne writes ("[PATCH v4 07/16] osstest: introduce build helpers for
FreeBSD"):
> Some steps of the FreeBSD build process need to be done as root, so
> introduce some helpers to perform those steps:
> buildcmd_stamped_logged_root and target_cmd_build_root. They behave
> exactly the same
Roger Pau Monne writes ("[PATCH v4 06/16] osstest: add a FreeBSD host install
recipe"):
> The installation is performed using the bsdinstall tool, which is part
> of the FreeBSD base system. The installer image is setup with the
> osstest ssh keys and sshd enabled by default, which allows the
Hi Jan,
On 07/06/2017 02:10 PM, Jan Beulich wrote:
On 06.07.17 at 13:50, wrote:
>> --- /dev/null
>> +++ b/xen/include/xen/page-defs.h
>> @@ -0,0 +1,24 @@
>> +#ifndef __XEN_PAGE_DEFS_H__
>> +#define __XEN_PAGE_DEFS_H__
>> +
>> +/* Helpers for different page
Roger Pau Monne writes ("[PATCH v4 04/16] osstest: introduce a helper to
calculate the sha256 of a given file"):
> The helper is going to be used to calculate the sha256 of the FreeBSD
> installer images.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
The installation is performed using the bsdinstall tool, which is part
of the FreeBSD base system. The installer image is setup with the
osstest ssh keys and sshd enabled by default, which allows the test
harness to just ssh into the box, create the install config file and
launch the scripted
Due to the nature of the FreeBSD install media, which is
self-generated from the ts-freebsd-build script, the hostflags runvar
set to FreeBSD jobs are related to the current version under test.
The following hostflags might need to be fetched from the runvars of a
previous build-$arch-freebsd
Make need_build_host store a string instead of a boolean. This is
later going to be expanded to handle the FreeBSD build jobs.
Signed-off-by: Roger Pau Monné
---
Changes since v3:
- New in this version (split from patch).
---
sg-run-job | 33
The helper allows booting a host from pxelinux using an image
compatible with memdisk.
Note that this requires having a copy of the memdisk binary (provided
as part of pxelinux) in the root of the tftp server.
Signed-off-by: Roger Pau Monné
---
Changes since v3:
- New in
Add the missing pieces so that cr-daily-branch knows how to create a
FreeBSD flight. This has been tested by calling `./cr-daily-branch
freebsd`.
Note that there are two missing pieces. The first one is correctly
setting the FREEBSD_BUILDJOB environment variable when calling
make-freebsd-flight,
Some steps of the FreeBSD build process need to be done as root, so
introduce some helpers to perform those steps:
buildcmd_stamped_logged_root and target_cmd_build_root. They behave
exactly the same as the non-root counterparts.
Signed-off-by: Roger Pau Monné
---
Changes
FreeBSD support is added to target_install_packages and
target_install_packages_norec, although there's no equivalent to the
--no-install-recommends in the FreeBSD package manager.
Signed-off-by: Roger Pau Monné
---
Changes since v3:
- New in this version.
---
The helper is going to be used to calculate the sha256 of the FreeBSD
installer images.
Signed-off-by: Roger Pau Monné
---
Changes since v3:
- New in this version.
---
Osstest/TestSupport.pm | 13 +
1 file changed, 13 insertions(+)
diff --git
The logic to create a FreeBSD build job is added to
make-freebsd-flight. This includes creating a FreeBSD build job, and
also testing the output of that build job (by creating another build
job that depends on the output of the first).
Note that the FreeBSD build job needs some input in order to
Add support and introduce a FreeBSD build job to sg-run-job.
Signed-off-by: Roger Pau Monné
---
Changes since v3:
- New in this version (split from existing patch).
---
sg-run-job | 13 +
1 file changed, 13 insertions(+)
diff --git a/sg-run-job b/sg-run-job
In order to generate the FreeBSD installer image and the install
media.
The install sets are the vanilla ones generated by the 'ftp' release
target. The installer image is handcrafted based on the filesystem
created by the 'bootonly' target, which is then populated with the ssh
host keys, and
This is used in order to get the per-host tftp prefix, used to store
the host initrd file.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
---
Changes since v1:
- New in this version.
---
Osstest/TestSupport.pm | 8 +++-
And introduce built_stash_debugfile in order the keep the previous
behavior of built_stash_file.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
---
Osstest/TestSupport.pm | 14 --
ts-kernel-build| 4 ++--
ts-xen-build
Allow catching-otherwise to take a variable number of tail arguments,
that will be propagated to the called proc.
Signed-off-by: Roger Pau Monné
---
Changes since v3:
- New in this version.
---
sg-run-job | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff
This is required for FreeBSD, that will need to set some of the
hostflags at runtime. The current IDENT_hostflags will be keep as-is,
and they should only be set at job creation time.
Also introduce a helper to set the runtime hostflags.
Signed-off-by: Roger Pau Monné
---
Hello,
This series introduces initial FreeBSD host support to osstest. The
current series allow installing a bare-metal host with FreeBSD and
building FreeBSD on it in order to generate new install media that can
be fed into the installer script.
This is still very limited, since no Xen testing
This is equivalent to the already existing authorized_keys function,
and generates the contents of the known_hosts file that should be
installed on targets.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
---
Osstest/Debian.pm | 36
Hi Jan,
On 07/06/2017 02:18 PM, Jan Beulich wrote:
On 06.07.17 at 13:50, wrote:
>> --- a/xen/include/asm-arm/config.h
>> +++ b/xen/include/asm-arm/config.h
>> @@ -19,6 +19,8 @@
>> #define BITS_PER_LONG (BYTES_PER_LONG << 3)
>> #define POINTER_ALIGN BYTES_PER_LONG
1 - 100 of 162 matches
Mail list logo