* [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
@ 2019-09-30 4:23 osstest service owner
2019-09-30 6:01 ` Jürgen Groß
0 siblings, 1 reply; 12+ messages in thread
From: osstest service owner @ 2019-09-30 4:23 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 141990 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141990/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-debianhvm-amd64 7 xen-boot fail REGR. vs. 141822
test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 141822
test-amd64-i386-libvirt-xsm 12 guest-start fail REGR. vs. 141822
test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 141822
test-amd64-i386-libvirt 12 guest-start fail REGR. vs. 141822
test-amd64-amd64-migrupgrade 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
test-amd64-i386-migrupgrade 22 guest-migrate/src_host/dst_host fail REGR. vs. 141822
test-arm64-arm64-examine 11 examine-serial/bootloader fail REGR. vs. 141822
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 141822
test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR. vs. 141822
test-amd64-amd64-libvirt-vhd 10 debian-di-install fail REGR. vs. 141822
test-armhf-armhf-libvirt 12 guest-start fail REGR. vs. 141822
test-armhf-armhf-libvirt-raw 10 debian-di-install fail REGR. vs. 141822
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 141822
test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 141822
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 141822
test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 141822
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail like 141822
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail like 141822
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 141822
test-amd64-i386-xl-pvshim 12 guest-start fail never pass
test-arm64-arm64-xl-seattle 13 migrate-support-check fail never pass
test-arm64-arm64-xl-seattle 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-xsm 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-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass
test-arm64-arm64-xl-thunderx 13 migrate-support-check fail never pass
test-arm64-arm64-xl-credit1 13 migrate-support-check fail never pass
test-arm64-arm64-xl-thunderx 14 saverestore-support-check fail never pass
test-arm64-arm64-xl-xsm 13 migrate-support-check fail never pass
test-arm64-arm64-xl-credit1 14 saverestore-support-check fail never pass
test-arm64-arm64-xl-xsm 14 saverestore-support-check fail never pass
test-arm64-arm64-xl 13 migrate-support-check fail never pass
test-arm64-arm64-xl 14 saverestore-support-check fail never pass
test-arm64-arm64-xl-credit2 13 migrate-support-check fail never pass
test-arm64-arm64-xl-credit2 14 saverestore-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-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 13 migrate-support-check fail never pass
test-armhf-armhf-xl 14 saverestore-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-credit2 13 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-credit1 13 migrate-support-check fail never pass
test-armhf-armhf-xl-credit1 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-vhd 12 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass
test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail never pass
test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass
test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
version targeted for testing:
xen d5b7d10cb49cf8fcf1104606fb27b80233bb98c1
baseline version:
xen f93abf0315efef861270c25d83c8047fd6a54ec4
Last test of basis 141822 2019-09-25 14:59:55 Z 4 days
Failing since 141882 2019-09-27 01:20:55 Z 3 days 4 attempts
Testing same since 141990 2019-09-29 15:45:11 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Chao Gao <chao.gao@intel.com>
Christian Lindig <christian.lindig@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Juergen Gross <jgross@suse.com>
Julien Grall <julien.grall@arm.com>
Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Paul Durrant <paul.durrant@citrix.com>
Razvan Cojocaru <rcojocaru@bitdefender.com>
Roger Pau Monné <roger.pau@citrix.com>
Sergey Dyasli <sergey.dyasli@citrix.com>
Simon Gaiser <simon@invisiblethingslab.com>
Stefano Stabellini <sstabellini@kernel.org>
Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Wei Liu <wl@xen.org>
jobs:
build-amd64-xsm pass
build-arm64-xsm pass
build-i386-xsm pass
build-amd64-xtf pass
build-amd64 pass
build-arm64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-arm64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-prev pass
build-i386-prev pass
build-amd64-pvops pass
build-arm64-pvops pass
build-armhf-pvops pass
build-i386-pvops 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-arm64-arm64-xl pass
test-armhf-armhf-xl pass
test-amd64-i386-xl pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm fail
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemut-debianhvm-i386-xsm pass
test-amd64-i386-xl-qemut-debianhvm-i386-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-i386-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-arm64-arm64-libvirt-xsm fail
test-amd64-i386-libvirt-xsm fail
test-amd64-amd64-xl-xsm pass
test-arm64-arm64-xl-xsm pass
test-amd64-i386-xl-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-amd64-xl-pvhv2-amd pass
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemut-debianhvm-amd64 fail
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-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-credit1 pass
test-arm64-arm64-xl-credit1 pass
test-armhf-armhf-xl-credit1 pass
test-amd64-amd64-xl-credit2 pass
test-arm64-arm64-xl-credit2 pass
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-xl-cubietruck pass
test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict pass
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict pass
test-amd64-amd64-examine pass
test-arm64-arm64-examine pass
test-armhf-armhf-examine pass
test-amd64-i386-examine pass
test-amd64-i386-freebsd10-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 pass
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt fail
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt fail
test-amd64-amd64-livepatch pass
test-amd64-i386-livepatch pass
test-amd64-amd64-migrupgrade fail
test-amd64-i386-migrupgrade fail
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 fail
test-amd64-i386-libvirt-pair fail
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
test-amd64-amd64-xl-pvshim pass
test-amd64-i386-xl-pvshim fail
test-amd64-amd64-pygrub pass
test-amd64-amd64-xl-qcow2 pass
test-armhf-armhf-libvirt-raw fail
test-amd64-i386-xl-raw pass
test-amd64-amd64-xl-rtds pass
test-armhf-armhf-xl-rtds pass
test-arm64-arm64-xl-seattle pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow pass
test-amd64-amd64-xl-shadow pass
test-amd64-i386-xl-shadow pass
test-arm64-arm64-xl-thunderx pass
test-amd64-amd64-libvirt-vhd fail
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.
(No revision log; it would be 1862 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 4:23 [Xen-devel] [xen-unstable test] 141990: regressions - FAIL osstest service owner
@ 2019-09-30 6:01 ` Jürgen Groß
2019-09-30 7:11 ` Jürgen Groß
0 siblings, 1 reply; 12+ messages in thread
From: Jürgen Groß @ 2019-09-30 6:01 UTC (permalink / raw)
To: osstest service owner, xen-devel, Paul Durrant
On 30.09.19 06:23, osstest service owner wrote:
> flight 141990 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/141990/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-debianhvm-amd64 7 xen-boot fail REGR. vs. 141822
> test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 141822
> test-amd64-i386-libvirt-xsm 12 guest-start fail REGR. vs. 141822
> test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 141822
> test-amd64-i386-libvirt 12 guest-start fail REGR. vs. 141822
> test-amd64-amd64-migrupgrade 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
> test-amd64-i386-migrupgrade 22 guest-migrate/src_host/dst_host fail REGR. vs. 141822
> test-arm64-arm64-examine 11 examine-serial/bootloader fail REGR. vs. 141822
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 141822
> test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR. vs. 141822
> test-amd64-amd64-libvirt-vhd 10 debian-di-install fail REGR. vs. 141822
> test-armhf-armhf-libvirt 12 guest-start fail REGR. vs. 141822
> test-armhf-armhf-libvirt-raw 10 debian-di-install fail REGR. vs. 141822
Several of the failures seem to be related to commit babde47a3feda6dd4
("introduce a 'passthrough' configuration option to xl.cfg").
I think the assert() in lixl_create.c (line 589) should just be dropped?
assert(info->passthrough != LIBXL_PASSTHROUGH_ENABLED);
LOG(DETAIL, "passthrough: %s",
libxl_passthrough_to_string(info->passthrough));
if (info->passthrough != LIBXL_PASSTHROUGH_DISABLED)
create.flags |= XEN_DOMCTL_CDF_iommu;
if (info->passthrough == LIBXL_PASSTHROUGH_SYNC_PT)
create.iommu_opts |= XEN_DOMCTL_IOMMU_no_sharept;
Or the if () statements after that are just plain wrong?
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 6:01 ` Jürgen Groß
@ 2019-09-30 7:11 ` Jürgen Groß
2019-09-30 7:51 ` Paul Durrant
0 siblings, 1 reply; 12+ messages in thread
From: Jürgen Groß @ 2019-09-30 7:11 UTC (permalink / raw)
To: osstest service owner, xen-devel, Paul Durrant
On 30.09.19 08:01, Jürgen Groß wrote:
> On 30.09.19 06:23, osstest service owner wrote:
>> flight 141990 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/141990/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-amd64-amd64-xl-qemut-debianhvm-amd64 7 xen-boot fail REGR.
>> vs. 141822
>> test-amd64-amd64-libvirt 12 guest-start fail REGR.
>> vs. 141822
>> test-amd64-i386-libvirt-xsm 12 guest-start fail REGR.
>> vs. 141822
>> test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host
>> fail REGR. vs. 141822
>> test-amd64-i386-libvirt 12 guest-start fail REGR.
>> vs. 141822
>> test-amd64-amd64-migrupgrade 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
>> test-amd64-i386-migrupgrade 22 guest-migrate/src_host/dst_host fail
>> REGR. vs. 141822
>> test-arm64-arm64-examine 11 examine-serial/bootloader fail REGR.
>> vs. 141822
>> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10
>> debian-hvm-install fail REGR. vs. 141822
>> test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR.
>> vs. 141822
>> test-amd64-amd64-libvirt-vhd 10 debian-di-install fail REGR.
>> vs. 141822
>> test-armhf-armhf-libvirt 12 guest-start fail REGR.
>> vs. 141822
>> test-armhf-armhf-libvirt-raw 10 debian-di-install fail REGR.
>> vs. 141822
>
> Several of the failures seem to be related to commit babde47a3feda6dd4
> ("introduce a 'passthrough' configuration option to xl.cfg").
>
> I think the assert() in lixl_create.c (line 589) should just be dropped?
>
> assert(info->passthrough != LIBXL_PASSTHROUGH_ENABLED);
> LOG(DETAIL, "passthrough: %s",
> libxl_passthrough_to_string(info->passthrough));
>
> if (info->passthrough != LIBXL_PASSTHROUGH_DISABLED)
> create.flags |= XEN_DOMCTL_CDF_iommu;
>
> if (info->passthrough == LIBXL_PASSTHROUGH_SYNC_PT)
> create.iommu_opts |= XEN_DOMCTL_IOMMU_no_sharept;
>
> Or the if () statements after that are just plain wrong?
I misread the code.
But nevertheless there is something wrong...
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 7:11 ` Jürgen Groß
@ 2019-09-30 7:51 ` Paul Durrant
2019-09-30 8:15 ` Paul Durrant
0 siblings, 1 reply; 12+ messages in thread
From: Paul Durrant @ 2019-09-30 7:51 UTC (permalink / raw)
To: 'Jürgen Groß', osstest service owner, xen-devel
> -----Original Message-----
> From: Jürgen Groß <jgross@suse.com>
> Sent: 30 September 2019 08:12
> To: osstest service owner <osstest-admin@xenproject.org>; xen-devel@lists.xenproject.org; Paul Durrant
> <Paul.Durrant@citrix.com>
> Subject: Re: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> On 30.09.19 08:01, Jürgen Groß wrote:
> > On 30.09.19 06:23, osstest service owner wrote:
> >> flight 141990 xen-unstable real [real]
> >> http://logs.test-lab.xenproject.org/osstest/logs/141990/
> >>
> >> Regressions :-(
> >>
> >> Tests which did not succeed and are blocking,
> >> including tests which could not be run:
> >> test-amd64-amd64-xl-qemut-debianhvm-amd64 7 xen-boot fail REGR.
> >> vs. 141822
> >> test-amd64-amd64-libvirt 12 guest-start fail REGR.
> >> vs. 141822
> >> test-amd64-i386-libvirt-xsm 12 guest-start fail REGR.
> >> vs. 141822
> >> test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host
> >> fail REGR. vs. 141822
> >> test-amd64-i386-libvirt 12 guest-start fail REGR.
> >> vs. 141822
> >> test-amd64-amd64-migrupgrade 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
> >> test-amd64-i386-migrupgrade 22 guest-migrate/src_host/dst_host fail
> >> REGR. vs. 141822
> >> test-arm64-arm64-examine 11 examine-serial/bootloader fail REGR.
> >> vs. 141822
> >> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10
> >> debian-hvm-install fail REGR. vs. 141822
> >> test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR.
> >> vs. 141822
> >> test-amd64-amd64-libvirt-vhd 10 debian-di-install fail REGR.
> >> vs. 141822
> >> test-armhf-armhf-libvirt 12 guest-start fail REGR.
> >> vs. 141822
> >> test-armhf-armhf-libvirt-raw 10 debian-di-install fail REGR.
> >> vs. 141822
> >
> > Several of the failures seem to be related to commit babde47a3feda6dd4
> > ("introduce a 'passthrough' configuration option to xl.cfg").
> >
> > I think the assert() in lixl_create.c (line 589) should just be dropped?
> >
> > assert(info->passthrough != LIBXL_PASSTHROUGH_ENABLED);
> > LOG(DETAIL, "passthrough: %s",
> > libxl_passthrough_to_string(info->passthrough));
> >
> > if (info->passthrough != LIBXL_PASSTHROUGH_DISABLED)
> > create.flags |= XEN_DOMCTL_CDF_iommu;
> >
> > if (info->passthrough == LIBXL_PASSTHROUGH_SYNC_PT)
> > create.iommu_opts |= XEN_DOMCTL_IOMMU_no_sharept;
> >
> > Or the if () statements after that are just plain wrong?
>
> I misread the code.
>
> But nevertheless there is something wrong...
>
Ok, I'll take a look now.
Paul
>
> Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 7:51 ` Paul Durrant
@ 2019-09-30 8:15 ` Paul Durrant
2019-09-30 9:07 ` Jan Beulich
0 siblings, 1 reply; 12+ messages in thread
From: Paul Durrant @ 2019-09-30 8:15 UTC (permalink / raw)
To: Paul Durrant, 'Jürgen Groß',
osstest service owner, xen-devel
> -----Original Message-----
> From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Paul Durrant
> Sent: 30 September 2019 08:51
> To: 'Jürgen Groß' <jgross@suse.com>; osstest service owner <osstest-admin@xenproject.org>; xen-
> devel@lists.xenproject.org
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> > -----Original Message-----
> > From: Jürgen Groß <jgross@suse.com>
> > Sent: 30 September 2019 08:12
> > To: osstest service owner <osstest-admin@xenproject.org>; xen-devel@lists.xenproject.org; Paul
> Durrant
> > <Paul.Durrant@citrix.com>
> > Subject: Re: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> >
> > On 30.09.19 08:01, Jürgen Groß wrote:
> > > On 30.09.19 06:23, osstest service owner wrote:
> > >> flight 141990 xen-unstable real [real]
> > >> http://logs.test-lab.xenproject.org/osstest/logs/141990/
> > >>
> > >> Regressions :-(
> > >>
> > >> Tests which did not succeed and are blocking,
> > >> including tests which could not be run:
> > >> test-amd64-amd64-xl-qemut-debianhvm-amd64 7 xen-boot fail REGR.
> > >> vs. 141822
> > >> test-amd64-amd64-libvirt 12 guest-start fail REGR.
> > >> vs. 141822
> > >> test-amd64-i386-libvirt-xsm 12 guest-start fail REGR.
> > >> vs. 141822
> > >> test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host
> > >> fail REGR. vs. 141822
> > >> test-amd64-i386-libvirt 12 guest-start fail REGR.
> > >> vs. 141822
> > >> test-amd64-amd64-migrupgrade 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
> > >> test-amd64-i386-migrupgrade 22 guest-migrate/src_host/dst_host fail
> > >> REGR. vs. 141822
> > >> test-arm64-arm64-examine 11 examine-serial/bootloader fail REGR.
> > >> vs. 141822
> > >> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10
> > >> debian-hvm-install fail REGR. vs. 141822
> > >> test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR.
> > >> vs. 141822
> > >> test-amd64-amd64-libvirt-vhd 10 debian-di-install fail REGR.
> > >> vs. 141822
> > >> test-armhf-armhf-libvirt 12 guest-start fail REGR.
> > >> vs. 141822
> > >> test-armhf-armhf-libvirt-raw 10 debian-di-install fail REGR.
> > >> vs. 141822
> > >
> > > Several of the failures seem to be related to commit babde47a3feda6dd4
> > > ("introduce a 'passthrough' configuration option to xl.cfg").
> > >
> > > I think the assert() in lixl_create.c (line 589) should just be dropped?
> > >
> > > assert(info->passthrough != LIBXL_PASSTHROUGH_ENABLED);
> > > LOG(DETAIL, "passthrough: %s",
> > > libxl_passthrough_to_string(info->passthrough));
> > >
> > > if (info->passthrough != LIBXL_PASSTHROUGH_DISABLED)
> > > create.flags |= XEN_DOMCTL_CDF_iommu;
> > >
> > > if (info->passthrough == LIBXL_PASSTHROUGH_SYNC_PT)
> > > create.iommu_opts |= XEN_DOMCTL_IOMMU_no_sharept;
> > >
> > > Or the if () statements after that are just plain wrong?
> >
> > I misread the code.
> >
> > But nevertheless there is something wrong...
> >
>
> Ok, I'll take a look now.
>
I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the problem and on at least one of the test failures I see lots of this kind of thing in the serial log:
Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
I'll try to find an AMD rig and see if I can repro a failure.
Paul
> Paul
>
> >
> > Juergen
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 8:15 ` Paul Durrant
@ 2019-09-30 9:07 ` Jan Beulich
2019-09-30 9:17 ` Paul Durrant
0 siblings, 1 reply; 12+ messages in thread
From: Jan Beulich @ 2019-09-30 9:07 UTC (permalink / raw)
To: Paul Durrant; +Cc: Juergen Gross, xen-devel, osstest service owner
On 30.09.2019 10:15, Paul Durrant wrote:
> I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the problem and on at least one of the test failures I see lots of this kind of thing in the serial log:
>
> Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
But these are bare metal Linux messages, aren't they?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 9:07 ` Jan Beulich
@ 2019-09-30 9:17 ` Paul Durrant
2019-09-30 9:30 ` Jürgen Groß
0 siblings, 1 reply; 12+ messages in thread
From: Paul Durrant @ 2019-09-30 9:17 UTC (permalink / raw)
To: 'Jan Beulich'; +Cc: Juergen Gross, xen-devel, osstest service owner
> -----Original Message-----
> From: Jan Beulich <jbeulich@suse.com>
> Sent: 30 September 2019 10:07
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: xen-devel@lists.xenproject.org; Juergen Gross <jgross@suse.com>; osstest service owner <osstest-
> admin@xenproject.org>
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> On 30.09.2019 10:15, Paul Durrant wrote:
> > I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the
> problem and on at least one of the test failures I see lots of this kind of thing in the serial log:
> >
> > Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT
> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT
> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT
> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT
> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT
> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
>
Ah yes, they might be. Still not found anything useful in other logs.
Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 9:17 ` Paul Durrant
@ 2019-09-30 9:30 ` Jürgen Groß
2019-09-30 9:52 ` Paul Durrant
2019-09-30 12:47 ` Paul Durrant
0 siblings, 2 replies; 12+ messages in thread
From: Jürgen Groß @ 2019-09-30 9:30 UTC (permalink / raw)
To: Paul Durrant, Jan Beulich; +Cc: xen-devel, osstest service owner
On 30.09.19 11:17, Paul Durrant wrote:
>> -----Original Message-----
>> From: Jan Beulich <jbeulich@suse.com>
>> Sent: 30 September 2019 10:07
>> To: Paul Durrant <Paul.Durrant@citrix.com>
>> Cc: xen-devel@lists.xenproject.org; Juergen Gross <jgross@suse.com>; osstest service owner <osstest-
>> admin@xenproject.org>
>> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>>
>> On 30.09.2019 10:15, Paul Durrant wrote:
>>> I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the
>> problem and on at least one of the test failures I see lots of this kind of thing in the serial log:
>>>
>>> Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT
>> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
>>> Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT
>> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
>>> Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT
>> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
>>> Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT
>> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
>>> Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT
>> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
>>
>
> Ah yes, they might be. Still not found anything useful in other logs.
One case was for stub-dm, another one for migration.
I could imagine info->passthrough isn't initialized properly for the
stubdom case, and maybe the information is missing in the migration
stream, too?
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 9:30 ` Jürgen Groß
@ 2019-09-30 9:52 ` Paul Durrant
2019-09-30 12:47 ` Paul Durrant
1 sibling, 0 replies; 12+ messages in thread
From: Paul Durrant @ 2019-09-30 9:52 UTC (permalink / raw)
To: 'Jürgen Groß', Jan Beulich
Cc: xen-devel, osstest service owner
> -----Original Message-----
> From: Jürgen Groß <jgross@suse.com>
> Sent: 30 September 2019 10:30
> To: Paul Durrant <Paul.Durrant@citrix.com>; Jan Beulich <jbeulich@suse.com>
> Cc: xen-devel@lists.xenproject.org; osstest service owner <osstest-admin@xenproject.org>
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> On 30.09.19 11:17, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Jan Beulich <jbeulich@suse.com>
> >> Sent: 30 September 2019 10:07
> >> To: Paul Durrant <Paul.Durrant@citrix.com>
> >> Cc: xen-devel@lists.xenproject.org; Juergen Gross <jgross@suse.com>; osstest service owner
> <osstest-
> >> admin@xenproject.org>
> >> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> >>
> >> On 30.09.2019 10:15, Paul Durrant wrote:
> >>> I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the
> >> problem and on at least one of the test failures I see lots of this kind of thing in the serial
> log:
> >>>
> >>> Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>
> >
> > Ah yes, they might be. Still not found anything useful in other logs.
>
> One case was for stub-dm, another one for migration.
>
> I could imagine info->passthrough isn't initialized properly for the
> stubdom case, and maybe the information is missing in the migration
> stream, too?
>
True, the last minute addition of the 'default' option could have messed things up. I'll check that scenario.
Paul
>
> Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 9:30 ` Jürgen Groß
2019-09-30 9:52 ` Paul Durrant
@ 2019-09-30 12:47 ` Paul Durrant
2019-09-30 16:38 ` Paul Durrant
1 sibling, 1 reply; 12+ messages in thread
From: Paul Durrant @ 2019-09-30 12:47 UTC (permalink / raw)
To: 'Jürgen Groß', Jan Beulich
Cc: xen-devel, osstest service owner
> -----Original Message-----
> From: Jürgen Groß <jgross@suse.com>
> Sent: 30 September 2019 10:30
> To: Paul Durrant <Paul.Durrant@citrix.com>; Jan Beulich <jbeulich@suse.com>
> Cc: xen-devel@lists.xenproject.org; osstest service owner <osstest-admin@xenproject.org>
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> On 30.09.19 11:17, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Jan Beulich <jbeulich@suse.com>
> >> Sent: 30 September 2019 10:07
> >> To: Paul Durrant <Paul.Durrant@citrix.com>
> >> Cc: xen-devel@lists.xenproject.org; Juergen Gross <jgross@suse.com>; osstest service owner
> <osstest-
> >> admin@xenproject.org>
> >> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> >>
> >> On 30.09.2019 10:15, Paul Durrant wrote:
> >>> I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the
> >> problem and on at least one of the test failures I see lots of this kind of thing in the serial
> log:
> >>>
> >>> Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>> Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT
> >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> >>
> >
> > Ah yes, they might be. Still not found anything useful in other logs.
>
> One case was for stub-dm, another one for migration.
>
> I could imagine info->passthrough isn't initialized properly for the
> stubdom case, and maybe the information is missing in the migration
> stream, too?
Ok, I've verified migration on my Intel test rig. It is fine with passthrough=disabled (or non-existent in the xl.cfg) and fails (as expected due to global logdirty refusing to activate when IOMMU mappings are present) when set to anything else. Thus the addition of the passthrough setting should actually fix failures caused by an earlier patch (when only a global disable could turn off IOMMU mappings).
I have not checked stubdoms yet and I am currently building an AMD system.
Paul
>
>
> Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 12:47 ` Paul Durrant
@ 2019-09-30 16:38 ` Paul Durrant
2019-10-01 8:43 ` Paul Durrant
0 siblings, 1 reply; 12+ messages in thread
From: Paul Durrant @ 2019-09-30 16:38 UTC (permalink / raw)
To: 'Jürgen Groß', 'Jan Beulich'
Cc: 'xen-devel@lists.xenproject.org',
'osstest service owner'
> -----Original Message-----
> From: Paul Durrant
> Sent: 30 September 2019 13:48
> To: 'Jürgen Groß' <jgross@suse.com>; Jan Beulich <jbeulich@suse.com>
> Cc: xen-devel@lists.xenproject.org; osstest service owner <osstest-admin@xenproject.org>
> Subject: RE: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> > -----Original Message-----
> > From: Jürgen Groß <jgross@suse.com>
> > Sent: 30 September 2019 10:30
> > To: Paul Durrant <Paul.Durrant@citrix.com>; Jan Beulich <jbeulich@suse.com>
> > Cc: xen-devel@lists.xenproject.org; osstest service owner <osstest-admin@xenproject.org>
> > Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> >
> > On 30.09.19 11:17, Paul Durrant wrote:
> > >> -----Original Message-----
> > >> From: Jan Beulich <jbeulich@suse.com>
> > >> Sent: 30 September 2019 10:07
> > >> To: Paul Durrant <Paul.Durrant@citrix.com>
> > >> Cc: xen-devel@lists.xenproject.org; Juergen Gross <jgross@suse.com>; osstest service owner
> > <osstest-
> > >> admin@xenproject.org>
> > >> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> > >>
> > >> On 30.09.2019 10:15, Paul Durrant wrote:
> > >>> I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the
> > >> problem and on at least one of the test failures I see lots of this kind of thing in the serial
> > log:
> > >>>
> > >>> Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT
> > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > >>> Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT
> > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > >>> Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT
> > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > >>> Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT
> > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > >>> Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT
> > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > >>
> > >
> > > Ah yes, they might be. Still not found anything useful in other logs.
> >
> > One case was for stub-dm, another one for migration.
> >
> > I could imagine info->passthrough isn't initialized properly for the
> > stubdom case, and maybe the information is missing in the migration
> > stream, too?
>
> Ok, I've verified migration on my Intel test rig. It is fine with passthrough=disabled (or non-
> existent in the xl.cfg) and fails (as expected due to global logdirty refusing to activate when IOMMU
> mappings are present) when set to anything else. Thus the addition of the passthrough setting should
> actually fix failures caused by an earlier patch (when only a global disable could turn off IOMMU
> mappings).
> I have not checked stubdoms yet and I am currently building an AMD system.
>
stubdom seems to work (although it's broken, possibly for a long time, if you try to use a qcow2 system disk image) and AMD seems ok too. So, still no idea what breakage osstest has found.
> Paul
>
> >
> >
> > Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
2019-09-30 16:38 ` Paul Durrant
@ 2019-10-01 8:43 ` Paul Durrant
0 siblings, 0 replies; 12+ messages in thread
From: Paul Durrant @ 2019-10-01 8:43 UTC (permalink / raw)
To: Paul Durrant, 'Jürgen Groß', 'Jan Beulich'
Cc: 'xen-devel@lists.xenproject.org',
'osstest service owner'
> -----Original Message-----
> From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Paul Durrant
> Sent: 30 September 2019 17:38
> To: 'Jürgen Groß' <jgross@suse.com>; 'Jan Beulich' <jbeulich@suse.com>
> Cc: 'xen-devel@lists.xenproject.org' <xen-devel@lists.xenproject.org>; 'osstest service owner'
> <osstest-admin@xenproject.org>
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> > -----Original Message-----
> > From: Paul Durrant
> > Sent: 30 September 2019 13:48
> > To: 'Jürgen Groß' <jgross@suse.com>; Jan Beulich <jbeulich@suse.com>
> > Cc: xen-devel@lists.xenproject.org; osstest service owner <osstest-admin@xenproject.org>
> > Subject: RE: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> >
> > > -----Original Message-----
> > > From: Jürgen Groß <jgross@suse.com>
> > > Sent: 30 September 2019 10:30
> > > To: Paul Durrant <Paul.Durrant@citrix.com>; Jan Beulich <jbeulich@suse.com>
> > > Cc: xen-devel@lists.xenproject.org; osstest service owner <osstest-admin@xenproject.org>
> > > Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> > >
> > > On 30.09.19 11:17, Paul Durrant wrote:
> > > >> -----Original Message-----
> > > >> From: Jan Beulich <jbeulich@suse.com>
> > > >> Sent: 30 September 2019 10:07
> > > >> To: Paul Durrant <Paul.Durrant@citrix.com>
> > > >> Cc: xen-devel@lists.xenproject.org; Juergen Gross <jgross@suse.com>; osstest service owner
> > > <osstest-
> > > >> admin@xenproject.org>
> > > >> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> > > >>
> > > >> On 30.09.2019 10:15, Paul Durrant wrote:
> > > >>> I can't find anything conclusive in the logs, but it looks like it's mainly AMD h/w that's the
> > > >> problem and on at least one of the test failures I see lots of this kind of thing in the serial
> > > log:
> > > >>>
> > > >>> Sep 29 17:33:55.316422 [ 169.828563] AMD-Vi: Event logged [[ 169.831798] IO_PAGE_FAULT
> > > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > > >>> Sep 29 17:33:55.376595 [ 169.840481] AMD-Vi: Event logged [[ 169.843716] IO_PAGE_FAULT
> > > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > > >>> Sep 29 17:33:55.388469 [ 169.852398] AMD-Vi: Event logged [[ 169.855627] IO_PAGE_FAULT
> > > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > > >>> Sep 29 17:33:55.400486 [ 169.864311] AMD-Vi: Event logged [[ 169.867540] IO_PAGE_FAULT
> > > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > > >>> Sep 29 17:33:55.412559 [ 169.876224] AMD-Vi: Event logged [[ 169.879458] IO_PAGE_FAULT
> > > >> device=00:13.1 domain=0x0006 address=0x0000000000000080 flags=0x0020]
> > > >>
> > > >
> > > > Ah yes, they might be. Still not found anything useful in other logs.
> > >
> > > One case was for stub-dm, another one for migration.
> > >
> > > I could imagine info->passthrough isn't initialized properly for the
> > > stubdom case, and maybe the information is missing in the migration
> > > stream, too?
> >
> > Ok, I've verified migration on my Intel test rig. It is fine with passthrough=disabled (or non-
> > existent in the xl.cfg) and fails (as expected due to global logdirty refusing to activate when
> IOMMU
> > mappings are present) when set to anything else. Thus the addition of the passthrough setting should
> > actually fix failures caused by an earlier patch (when only a global disable could turn off IOMMU
> > mappings).
> > I have not checked stubdoms yet and I am currently building an AMD system.
> >
>
> stubdom seems to work (although it's broken, possibly for a long time, if you try to use a qcow2
> system disk image) and AMD seems ok too. So, still no idea what breakage osstest has found.
>
Ok, I think I've figured out the problem. If the h/w is not 'directio' capable then libxl__domain_create_info_setdefault() will leave passthrough alone, meaning it is still set to 0 == LIBXL_PASSTHROUGH_ENABLED... and then the assertion is hit. I'll send a patch shortly.
Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2019-10-01 8:43 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-30 4:23 [Xen-devel] [xen-unstable test] 141990: regressions - FAIL osstest service owner
2019-09-30 6:01 ` Jürgen Groß
2019-09-30 7:11 ` Jürgen Groß
2019-09-30 7:51 ` Paul Durrant
2019-09-30 8:15 ` Paul Durrant
2019-09-30 9:07 ` Jan Beulich
2019-09-30 9:17 ` Paul Durrant
2019-09-30 9:30 ` Jürgen Groß
2019-09-30 9:52 ` Paul Durrant
2019-09-30 12:47 ` Paul Durrant
2019-09-30 16:38 ` Paul Durrant
2019-10-01 8:43 ` Paul Durrant
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.