From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org,
osstest service owner <osstest-admin@xenproject.org>,
Jan Beulich <jbeulich@suse.com>, Paul Durrant <paul@xen.org>
Subject: Re: [Xen-devel] [xen-unstable test] 142383: regressions - FAIL
Date: Tue, 8 Oct 2019 13:15:30 +0200 [thread overview]
Message-ID: <20191008111530.GD66437@Air-de-Roger> (raw)
In-Reply-To: <b155b2f9-9664-7366-cdd0-10fac5c3ab3b@suse.com>
On Tue, Oct 08, 2019 at 12:42:25PM +0200, Jürgen Groß wrote:
> On 07.10.19 22:56, osstest service owner wrote:
> > flight 142383 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/142383/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 141822
> > test-amd64-i386-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 141822
>
> Hmm, test log says the guest didn't suspend.
>
> Could that be related to commit b183e180bce9303 ?
The libvirt libxl daemon spits:
2019-10-07 12:31:09.953+0000: libxl-save-helper: starting save: Success
2019-10-07 12:31:09.953+0000: xc: fd 40, dom 1, flags 1, hvm 0
2019-10-07 12:31:09.954+0000: xc: Saving domain 1, type x86 PV
2019-10-07 12:31:09.954+0000: xc: 64 bits, 4 levels
2019-10-07 12:31:09.959+0000: xc: max_mfn 0x280000
2019-10-07 12:31:09.959+0000: xc: p2m list from 0xffffc90000000000 to 0xffffc900000fffff, root at 0x27de0a
2019-10-07 12:31:09.959+0000: xc: max_pfn 0x1ffff, p2m_frames 256
2019-10-07 12:31:09.960+0000: xc: Failed to enable logdirty: 22,0,22 (22 = Invalid argument): Internal error
2019-10-07 12:31:09.960+0000: xc: Save failed (22 = Invalid argument): Internal error
2019-10-07 12:31:09.981+0000: libxl-save-helper: complete r=-1: Invalid argument
2019-10-07 12:31:09.983+0000: libxl: libxl.c:752:libxl__fd_flags_restore: fnctl F_SETFL of fd 40 to 0x2
2019-10-07 12:31:09.983+0000: libxl: libxl_event.c:1873:libxl__ao_complete: ao 0x7f760c002110: complete, rc=-8
2019-10-07 12:31:09.983+0000: libxl: libxl_event.c:1842:libxl__ao__destroy: ao 0x7f760c002110: destroy
Which seem to be related to the recent iommu changes, I would say it's
likely hitting the is_iommu_enabled check in paging_log_dirty_enable
and hence returning EINVAL.
Adding Paul and Jan who worked on the series.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-08 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 20:56 [Xen-devel] [xen-unstable test] 142383: regressions - FAIL osstest service owner
2019-10-08 10:42 ` Jürgen Groß
2019-10-08 11:15 ` Roger Pau Monné [this message]
2019-10-08 11:31 ` Jan Beulich
2019-10-08 16:12 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191008111530.GD66437@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=paul@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.