flight 111539 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111539/
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
Tes
flight 111534 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111534/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail like 111377
test-amd64-amd64-xl-qemuu-win7-amd64
branch xen-unstable
xenbranch xen-unstable
job test-arm64-arm64-libvirt-xsm
testid guest-start
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
Tree: linux git://xenbits.xe
flight 111529 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111529/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 7 xen-bootfail REGR. vs. 110515
test-amd64-amd64-li
This is based on git://git.savannah.gnu.org/grub.git phcoder/verifiers branch.
Just an RFC.
TODO:
- disable the GRUB2 modules load/unload,
- disable the dangerous modules, e.g. iorw, memrw.
Signed-off-by: Daniel Kiper
---
grub-core/Makefile.core.def|6 +++
grub-core/commands/ef
Signed-off-by: Daniel Kiper
---
xen/arch/x86/boot/head.S| 20 ++--
xen/arch/x86/efi/efi-boot.h | 12 +++-
xen/arch/x86/efi/stub.c |5 -
3 files changed, 33 insertions(+), 4 deletions(-)
diff --git a/xen/arch/x86/boot/head.S b/xen/arch/x86/boot/head.S
i
Signed-off-by: Daniel Kiper
---
xen/arch/x86/Makefile |1 +
1 file changed, 1 insertion(+)
diff --git a/xen/arch/x86/Makefile b/xen/arch/x86/Makefile
index 93ead6e..e09f5f4 100644
--- a/xen/arch/x86/Makefile
+++ b/xen/arch/x86/Makefile
@@ -95,6 +95,7 @@ syms-warn-dup-$(CONFIG_SUPPRESS_DUPLIC
In comparison to ELF the PE format is not supported by the Multiboot2
protocol. So, if we wish to load xen.efi using this protocol we have
to add MULTIBOOT2_HEADER_TAG_ADDRESS and MULTIBOOT2_HEADER_TAG_ENTRY_ADDRESS
tags into Multiboot2 header.
Additionally, put MULTIBOOT2_HEADER_TAG_ENTRY_ADDRESS
Hey,
As in subject... This way we get:
- one binary which can be loaded by the EFI loader,
Multiboot and Multiboot2 protocols,
- if we wish, in the future we can drop xen/xen.gz
and build xen.efi only,
- crash dumps generated by the xen.efi loaded from
the EFI loader can be analy
In comparison to ELF the PE format is not supported by the Multiboot
protocol. So, if we wish to load xen.efi using this protocol we have
to put header_addr, load_addr, load_end_addr, bss_end_addr and
entry_addr data into Multiboot header.
Signed-off-by: Daniel Kiper
---
xen/arch/x86/boot/head.S
..which verifies PE signatures with SHIM_LOCK protocol. We want
to re-use this code in subsequent patch in efi_multiboot2().
Signed-off-by: Daniel Kiper
---
xen/common/efi/boot.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/xen/common/efi/boot.c b/xe
This is the first step to get:
- one binary which can be loaded by the EFI loader,
Multiboot and Multiboot2 protocols,
- if we wish, in the future we can drop xen/xen.gz
and build xen.efi only,
- crash dumps generated by the xen.efi loaded from
the EFI loader can be analyzed by cr
We need the POSIX time to properly fill the TimeDateStamp field in the PE
header.
Signed-off-by: Daniel Kiper
---
xen/Makefile | 14 --
xen/include/xen/compile.h.in |1 +
2 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/xen/Makefile b/xen/Makefile
flight 71673 distros-debian-stretch real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71673/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-armhf-stretch-netboot-pygrub 1 build-check(1)blocked n/a
build-arm64-pvops
On Fri, 2017-07-07 at 10:03 -0700, Volodymyr Babchuk wrote:
> On 7 July 2017 at 09:41, Dario Faggioli
> wrote:
> >
> > Also, are you sure (e.g., because of how the Linux driver is done)
> > that
> > this always happen on one vCPU?
>
> No, I can't guarantee that. Linux driver is single threaded,
This run is configured for baseline tests only.
flight 71674 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71674/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf e9651c12721d882f384ef10b7467af4ba56387c3
baseline v
This run is configured for baseline tests only.
flight 71672 xen-4.7-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71672/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-xsm 16 guest-start/
On Fri, Jul 7, 2017 at 9:39 AM, Tom Lendacky wrote:
> Currently there is a check if the address being mapped is in the ISA
> range (is_ISA_range()), and if it is, then phys_to_virt() is used to
> perform the mapping. When SME is active, the default is to add pagetable
> mappings with the encryptio
On Fri, Jul 7, 2017 at 9:38 AM, Tom Lendacky wrote:
> Update the CPU features to include identifying and reporting on the
> Secure Memory Encryption (SME) feature. SME is identified by CPUID
> 0x801f, but requires BIOS support to enable it (set bit 23 of
> MSR_K8_SYSCFG). Only show the SME f
flight 111527 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111527/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-examine 7 reboot fail REGR. vs. 111416
test-amd64-amd64-pai
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-libvirt-pair
testid guest-start/debian
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
Tree: linux git://gi
* Tom Lendacky wrote:
> This patch series provides support for AMD's new Secure Memory Encryption
> (SME)
> feature.
I'm wondering, what's the typical performance hit to DRAM access latency when
SME
is enabled?
On that same note, if the performance hit is noticeable I'd expect SME to not
b
log a message when we enter this situation:
1) we already allocated the max number of available grants from hypervisor
and
2) we still need more (but the request fails because of 1)).
Sometimes the lack of grants causes IO hangs in xen_blkfront devices.
Adding this log would help debuging.
Signed
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 set
This is a non-functional change in preparation for introducing a
resource_shared_mark_ready in TestSupport.
Signed-off-by: Roger Pau Monné
---
Changes since v4:
- New in this version.
---
Osstest/Executive.pm | 5 +++--
Osstest/JobDB/Executive.pm | 2 +-
2 files changed, 4 insertions(+),
Add support and introduce a FreeBSD build job to sg-run-job.
Signed-off-by: Roger Pau Monné
---
Changes since v4:
- Use a switch in allocate-build-host.
Changes since v3:
- New in this version (split from existing patch).
---
sg-run-job | 14 ++
1 file changed, 14 insertions(+)
d
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é
---
Changes since v4:
- Al
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, w
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 v4:
- Fix the usage of the catching-otherwise blocks.
Changes since v3:
- New in this version (split from patch).
---
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 insta
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 v4:
- Unify more code between FreeBSD and Debian: introduce an
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 job:
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
---
Changes since v3:
- New in this version.
---
Osstest/TestSupport.pm | 13 +
1 file changed, 13 insertions(+)
diff --git a/Osstest/TestSu
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 s
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 i
That allows marking a host as ready to be shared. Replace the current
caller that open-codes it.
Signed-off-by: Roger Pau Monné
---
Changes since v4:
- New in this version.
---
Osstest/TestSupport.pm | 9 -
ts-xen-build-prep | 4 ++--
2 files changed, 10 insertions(+), 3 deletions(
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.
Deployment note: A copy of the memdisk binary (from syslinux) must be
placed in the roo
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 | 8
3 files changed, 18 inser
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 +++-
ts-host-install| 2 +-
2 files changed, 8 insertions(+),
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 +---
Osstest/TestSup
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é
Acked-by: Ian Jackson
---
Changes s
This run is configured for baseline tests only.
flight 71670 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71670/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 401d1343cb0279908a748fd0ff27609ccc300b43
baseline v
On Fri, Jul 07, 2017 at 02:50:01PM -0700, Stefano Stabellini wrote:
> On Fri, 7 Jul 2017, Roger Pau Monné wrote:
> > On Thu, Jul 06, 2017 at 03:55:28PM -0500, Vikram Sethi wrote:
> > > > > > AER: Will PCIe non-fatal and fatal errors (secondary bus reset for
> > > > > > fatal)
> > > > > > be
> > >
On Fri, 2017-07-07 at 17:19 +0100, Julien Grall wrote:
> On 05/07/17 14:50, Ivan Pavic wrote:
> > On 07/05/2017 02:55 PM, Julien Grall wrote:
> > >
> > > If you got a message in the former, but not the latter. Then you
> > > hit
> > > the bug described in my previous e-mail.
> >
> > Yes, I've
This run is configured for baseline tests only.
flight 71668 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71668/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-libvirt-xsm 1 build-check(1) bloc
45 matches
Mail list logo
