* [xen-unstable test] 115555: regressions - FAIL
@ 2017-11-04 23:14 osstest service owner
2017-11-10 9:33 ` Roger Pau Monné
0 siblings, 1 reply; 4+ messages in thread
From: osstest service owner @ 2017-11-04 23:14 UTC (permalink / raw)
To: xen-devel, osstest-admin
[-- Attachment #1: Type: text/plain, Size: 18570 bytes --]
flight 115555 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115555/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-i386-pvgrub 11 guest-start fail REGR. vs. 115526
test-amd64-amd64-amd64-pvgrub 11 guest-start fail REGR. vs. 115526
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs. 115526
test-amd64-i386-xl-qemut-ws16-amd64 13 guest-saverestore fail REGR. vs. 115526
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 115526
test-amd64-i386-libvirt-qcow2 17 guest-start/debian.repeat fail like 115526
test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 115526
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 115526
test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 115526
test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 115526
test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 115526
test-armhf-armhf-libvirt 14 saverestore-support-check fail like 115526
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail like 115526
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail like 115526
test-amd64-amd64-xl-pvhv2-intel 12 guest-start fail never pass
test-amd64-amd64-xl-pvhv2-amd 12 guest-start fail never pass
test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-i386-libvirt 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-amd64-i386-libvirt-qcow2 12 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 13 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass
test-armhf-armhf-xl-xsm 13 migrate-support-check fail never pass
test-armhf-armhf-xl-xsm 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass
test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass
test-armhf-armhf-xl 13 migrate-support-check fail never pass
test-armhf-armhf-xl 14 saverestore-support-check fail never pass
test-armhf-armhf-libvirt-xsm 13 migrate-support-check fail never pass
test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 12 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass
test-armhf-armhf-libvirt 13 migrate-support-check fail never pass
test-armhf-armhf-xl-rtds 13 migrate-support-check fail never pass
test-armhf-armhf-xl-rtds 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass
test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass
test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass
version targeted for testing:
xen e07ebab86595df29838f0960693df84f34528833
baseline version:
xen ff93dc55431517ed29c70dbff6721c6b0803acf9
Last test of basis 115526 2017-11-03 13:51:00 Z 1 days
Testing same since 115555 2017-11-04 09:34:51 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Julien Grall <julien.grall@arm.com>
Wei Liu <wei.liu2@citrix.com>
jobs:
build-amd64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64-xtf pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-prev pass
build-i386-prev pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
build-amd64-rumprun pass
build-i386-rumprun pass
test-xtf-amd64-amd64-1 pass
test-xtf-amd64-amd64-2 pass
test-xtf-amd64-amd64-3 pass
test-xtf-amd64-amd64-4 pass
test-xtf-amd64-amd64-5 pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl pass
test-amd64-i386-xl pass
test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-armhf-armhf-libvirt-xsm pass
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-xl-xsm pass
test-armhf-armhf-xl-xsm pass
test-amd64-i386-xl-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-amd64-xl-pvhv2-amd fail
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemut-debianhvm-amd64 pass
test-amd64-i386-xl-qemut-debianhvm-amd64 pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-freebsd10-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
test-amd64-amd64-rumprun-amd64 pass
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-qemut-ws16-amd64 fail
test-amd64-i386-xl-qemut-ws16-amd64 fail
test-amd64-amd64-xl-qemuu-ws16-amd64 fail
test-amd64-i386-xl-qemuu-ws16-amd64 fail
test-armhf-armhf-xl-arndale pass
test-amd64-amd64-xl-credit2 pass
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-xl-cubietruck pass
test-amd64-amd64-examine pass
test-armhf-armhf-examine pass
test-amd64-i386-examine pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumprun-i386 pass
test-amd64-amd64-xl-qemut-win10-i386 fail
test-amd64-i386-xl-qemut-win10-i386 fail
test-amd64-amd64-xl-qemuu-win10-i386 fail
test-amd64-i386-xl-qemuu-win10-i386 fail
test-amd64-amd64-qemuu-nested-intel pass
test-amd64-amd64-xl-pvhv2-intel fail
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt pass
test-armhf-armhf-libvirt pass
test-amd64-i386-libvirt pass
test-amd64-amd64-livepatch pass
test-amd64-i386-livepatch pass
test-amd64-amd64-migrupgrade pass
test-amd64-i386-migrupgrade pass
test-amd64-amd64-xl-multivcpu pass
test-armhf-armhf-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-amd64-amd64-amd64-pvgrub fail
test-amd64-amd64-i386-pvgrub fail
test-amd64-amd64-pygrub pass
test-amd64-i386-libvirt-qcow2 fail
test-amd64-amd64-xl-qcow2 pass
test-armhf-armhf-libvirt-raw pass
test-amd64-i386-xl-raw pass
test-amd64-amd64-xl-rtds pass
test-armhf-armhf-xl-rtds pass
test-amd64-amd64-libvirt-vhd pass
test-armhf-armhf-xl-vhd pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit e07ebab86595df29838f0960693df84f34528833
Author: Wei Liu <wei.liu2@citrix.com>
Date: Fri Nov 3 14:14:46 2017 +0000
Revert "tools/dombuilder: Prevent failures of xc_dom_gnttab_init()"
This reverts commit 9ff6dbfa7576cc1c5d6f9a3c59c69a8503e36f11, which
breaks hvm save/restore.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
commit 29028ed8db226ad3b7bc576c1e8891983acaa3ff
Merge: 9ff6dbf ff93dc5
Author: Wei Liu <wei.liu2@citrix.com>
Date: Thu Nov 2 17:07:58 2017 +0000
Merge remote-tracking branch 'origin/staging' into staging
commit 9ff6dbfa7576cc1c5d6f9a3c59c69a8503e36f11
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Thu Oct 12 20:19:09 2017 +0100
tools/dombuilder: Prevent failures of xc_dom_gnttab_init()
Recent changes in grant table configuration have caused calls to
xc_dom_gnttab_init() to fail if not proceeded with a call to
xc_domain_set_gnttab_limits(). This is backwards from the point of view of
3rd party dombuilder users.
Add max_{grant,maptrack}_frames parameters to struct xc_dom_image, and require
them to be set by callers using xc_dom_gnttab_init(). Libxl, which uses
xc_dom_gnttab_init() itself is updated appropriately.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Tested-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Release-acked-by: Julien Grall <julien.grall@linaro.org>
commit 87b0ae7e8277d2fa13486ce2e11a941e55f8df40
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Thu Oct 12 20:19:08 2017 +0100
tools/dombuilder: Fix asymmetry when setting up console and xenstore rings
libxl always uses xc_dom_gnttab_init(), which internally calls
xc_dom_gnttab{_hvm,}_seed() to set up the grants point at the console and
xenstore rings. For HVM guests, libxl then asks Xen for the information set
up previously, and calls xc_dom_gnttab_hvm_seed() a second time, which is
wasteful. ARM construction expects libxl to have set up
dom->{console,xenstore}_evtchn earlier, so only actually functions because of
this second call.
Rationalise everything and make it consistent for all guests.
1) Users of the domain builder are expected to provide
dom->{console,xenstore}_{evtchn,domid} unconditionally. This is checked
by setting invalid values in xc_dom_allocate(), and checking in
xc_dom_boot_image().
2) For x86 HVM and ARM guests, the event channels are given to Xen at the
same time as the ring gfns. ARM already did this, but x86 is updated to
match. x86 PV already provides this information in the start_info page.
3) Libxl is updated to drop all relevant functionality from
hvm_build_set_params(), and behave consistently with PV guests when it
comes to the handling of dom->{console,xenstore}_{evtchn,domid,gfn}.
This removes several redundant hypercalls (including a foreign mapping) from
the x86 HVM and ARM construction paths.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Tested-by: Julien Grall <julien.grall@arm.com>
Release-acked-by: Julien Grall <julien.grall@linaro.org>
commit f48b5449dabc770acdde6d25cfbd265cfb71034d
Author: Wei Liu <wei.liu2@citrix.com>
Date: Thu Oct 12 20:19:07 2017 +0100
tools/dombuilder: Switch to using gfn terminology for console and xenstore rings
The sole use of xc_dom_translated() and xc_dom_p2m() outside of the domain
builder is for libxl_dom() to translate the console and xenstore pfns back
into useful values. PV guest pfns are only interesting to the domain builder,
and gfns are the address space used by all other hypercalls.
Renaming the fields in xc_dom_image is deliberate, as it will cause
out-of-tree users of the dombuilder to notice the different semantics.
Correct the terminology throughout xc_dom_gnttab{_hvm,}_seed(), which are all
using gfns despite the existing variable names.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Tested-by: Julien Grall <julien.grall@arm.com>
Release-acked-by: Julien Grall <julien.grall@linaro.org>
[ wei: fix stubdom build ]
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
commit 86cf189a957129ea1ad6468fe9a0887b9e2819f3
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Thu Oct 12 20:19:06 2017 +0100
tools/dombuilder: Remove clear_page() from xc_dom_boot.c
pfn 0 is a legitimate (albeit unlikely) frame to use, so skipping it is wrong.
This behaviour appears to exists simply to cover the fact that zero is the
default value of an uninitialised field in dom.
ARM already clears the frames at the point that the pfns are allocated,
meaning that the added clear_page() is wasteful. Alter x86 to match ARM and
clear the page when it is allocated.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Tested-by: Julien Grall <julien.grall@arm.com>
Release-acked-by: Julien Grall <julien.grall@linaro.org>
commit 716273c94077e354194c7236623fe3dfa34572d3
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Thu Oct 12 20:19:05 2017 +0100
tools/dombuilder: Drop more PVH v1 leftovers
alloc_magic_pages() is renamed to alloc_magic_pages_pv() to mirror its
alloc_magic_pages_hvm() counterpart. Delete a redundant comment, introduce
some newlines clarity, and remove a logically dead allocation of shared info.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Tested-by: Julien Grall <julien.grall@arm.com>
Release-acked-by: Julien Grall <julien.grall@linaro.org>
(qemu changes not included)
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 115555: regressions - FAIL
2017-11-04 23:14 [xen-unstable test] 115555: regressions - FAIL osstest service owner
@ 2017-11-10 9:33 ` Roger Pau Monné
2017-11-10 9:50 ` Juergen Gross
0 siblings, 1 reply; 4+ messages in thread
From: Roger Pau Monné @ 2017-11-10 9:33 UTC (permalink / raw)
To: osstest service owner; +Cc: xen-devel
On Sat, Nov 04, 2017 at 11:14:35PM +0000, osstest service owner wrote:
> flight 115555 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/115555/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-i386-pvgrub 11 guest-start fail REGR. vs. 115526
> test-amd64-amd64-amd64-pvgrub 11 guest-start fail REGR. vs. 115526
Both of the above trigger an assertion, it seems to be in pvgrub code
(because I doubt minios has anything kexec related):
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-3.16.0-4-686-pae root=UUID=482efee7-e0f0-453e-bb8e-000bfc
d5a822 ro
initrd /boot/initrd.img-3.16.0-4-686-pae
============= Init TPM Front ================
Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT
Tpmfront:Info Shutting down tpmfront
close blk: backend=/local/domain/0/backend/vbd/2/51712 node=device/vbd/51712
ASSERTION FAILED: 0 at kexec.c:418.
Do_exit called!
base is 0xb6fca8 caller is 0x6c85d
base is 0xb6fcb8 caller is 0x617ff
base is 0xb6fce8 caller is 0x18fc5
base is 0xb6fdd8 caller is 0x39f8
base is 0xb6fe08 caller is 0x8bbf
base is 0xb6fe18 caller is 0xa6ae
base is 0xb6fe48 caller is 0x10526
base is 0xb6fed8 caller is 0x10c03
base is 0xb6ff58 caller is 0x41f9
base is 0xb6ff7c caller is 0x61f31
base is 0xb6ffec caller is 0x319e
> test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs. 115526
In this case it seems like the guest didn't suspend, but AFAICT the
guest is up and running. No errors on the serial console. It's on the
x16 migration.
> test-amd64-i386-xl-qemut-ws16-amd64 13 guest-saverestore fail REGR. vs. 115526
This one is worse, there's the following error from libxc:
xc: detail: Frames: 105472/1045504 10%
xc: detail: Frames: 115712/1045504 11%
xc: detail: Frames: 125952/1045504 12%
xc: detail: Frames: 136192/1045504 13%
xc: error: Failed to get types for pfn batch (14 = Bad address): Internal error
xc: error: Save failed (14 = Bad address): Internal error
The guest seems to be alive afterwards.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 115555: regressions - FAIL
2017-11-10 9:33 ` Roger Pau Monné
@ 2017-11-10 9:50 ` Juergen Gross
2017-11-10 10:02 ` Jan Beulich
0 siblings, 1 reply; 4+ messages in thread
From: Juergen Gross @ 2017-11-10 9:50 UTC (permalink / raw)
To: Roger Pau Monné, osstest service owner; +Cc: xen-devel
On 10/11/17 10:33, Roger Pau Monné wrote:
> On Sat, Nov 04, 2017 at 11:14:35PM +0000, osstest service owner wrote:
>> flight 115555 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/115555/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-amd64-amd64-i386-pvgrub 11 guest-start fail REGR. vs. 115526
>> test-amd64-amd64-amd64-pvgrub 11 guest-start fail REGR. vs. 115526
>
> Both of the above trigger an assertion, it seems to be in pvgrub code
> (because I doubt minios has anything kexec related):
>
> root (hd0,0)
>
> Filesystem type is ext2fs, partition type 0x83
>
> kernel /boot/vmlinuz-3.16.0-4-686-pae root=UUID=482efee7-e0f0-453e-bb8e-000bfc
>
> d5a822 ro
>
> initrd /boot/initrd.img-3.16.0-4-686-pae
>
> ============= Init TPM Front ================
> Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT
> Tpmfront:Info Shutting down tpmfront
> close blk: backend=/local/domain/0/backend/vbd/2/51712 node=device/vbd/51712
> ASSERTION FAILED: 0 at kexec.c:418.
That's a failure of HYPERVISOR_mmu_update() just before the target
kernel is being executed (see stubdom/grub/kexec.c).
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 115555: regressions - FAIL
2017-11-10 9:50 ` Juergen Gross
@ 2017-11-10 10:02 ` Jan Beulich
0 siblings, 0 replies; 4+ messages in thread
From: Jan Beulich @ 2017-11-10 10:02 UTC (permalink / raw)
To: Roger Pau Monné, Juergen Gross; +Cc: xen-devel, osstest service owner
>>> On 10.11.17 at 10:50, <jgross@suse.com> wrote:
> On 10/11/17 10:33, Roger Pau Monné wrote:
>> On Sat, Nov 04, 2017 at 11:14:35PM +0000, osstest service owner wrote:
>>> flight 115555 xen-unstable real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/115555/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>> test-amd64-amd64-i386-pvgrub 11 guest-start fail REGR. vs.
> 115526
>>> test-amd64-amd64-amd64-pvgrub 11 guest-start fail REGR. vs.
> 115526
>>
>> Both of the above trigger an assertion, it seems to be in pvgrub code
>> (because I doubt minios has anything kexec related):
>>
>> root (hd0,0)
>>
>> Filesystem type is ext2fs, partition type 0x83
>>
>> kernel /boot/vmlinuz-3.16.0-4-686-pae
> root=UUID=482efee7-e0f0-453e-bb8e-000bfc
>>
>> d5a822 ro
>>
>> initrd /boot/initrd.img-3.16.0-4-686-pae
>>
>> ============= Init TPM Front ================
>> Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront
> initialization! error = ENOENT
>> Tpmfront:Info Shutting down tpmfront
>> close blk: backend=/local/domain/0/backend/vbd/2/51712 node=device/vbd/51712
>> ASSERTION FAILED: 0 at kexec.c:418.
>
> That's a failure of HYPERVISOR_mmu_update() just before the target
> kernel is being executed (see stubdom/grub/kexec.c).
Which in turn, looking at the hypervisor logs, are attempts to fiddle
with MFN 0, which the domains don't own.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-11-10 10:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-04 23:14 [xen-unstable test] 115555: regressions - FAIL osstest service owner
2017-11-10 9:33 ` Roger Pau Monné
2017-11-10 9:50 ` Juergen Gross
2017-11-10 10:02 ` Jan Beulich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).