Re: [Xen-devel] [xen-unstable test] 115555: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 10.11.17 at 10:50, <jgross@xxxxxxxx> 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@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel