From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org, Jim Fehlig <jfehlig@suse.com>
Cc: osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [osstest test] 64958: regressions - trouble: broken/fail/pass
Date: Wed, 25 Nov 2015 15:32:12 +0000 [thread overview]
Message-ID: <1448465532.17688.122.camel@citrix.com> (raw)
In-Reply-To: <1448462229.17688.114.camel@citrix.com>
On Wed, 2015-11-25 at 14:37 +0000, Ian Campbell wrote:
> 2015-11-21 23:06:44 Z executing ssh ... root@172.16.144.44 virsh domxml-from-native xen-xl /etc/xen/debian.jessie.guest.osstest.cfg > /etc/xen/debian.jessie.guest.osstest.cfg.xml
> error: An error occurred, but the cause is unknown
This turned out to be the check of vcpus vs MAX_VIRT_CPUS in
xenParseCPUFeatures.
MAX_VIRT_CPUS is defined (by libvirt) as XEN_LEGACY_MAX_VCPUS, which is
mostly wrong on x86 (which supports more than that for guests using vcpu
placement) but is very wrong on ARM where we insist on vcpu placement and
XEN_LEGACY_MAX_VCPUS is therefore 1.
This test was trying to create a 2 cpu guest.
Since this check is in xen_common.c I think it might take a little
unravelling to fix this, since it seems to have lead to various other
assumptions to do with CPU masks fitting into an unsigned long in the
libvirt code base.
/me rolls up sleeves.
Ian.
>
> This was always masked before now because when running with Wheezy
> osstest
> failed to find a suitable kernel+initramfs before this point.
>
> http://logs.test-lab.xenproject.org/osstest/logs/64958/test-armhf-armhf-l
> ibvirt-qcow2/arndale-metrocentre---var-log-libvirt-libvirtd.log.gz
> just has:
>
> 2015-11-21 23:06:44.686+0000: 1648: debug :
> virConnectDomainXMLFromNative:2626 : conn=0xb4000598, format=xen-xl,
> config=name = 'debian.jessie.guest.osstest'
> memory = 512
> vif = [ 'mac=5a:36:0e:be:00:09' ]
> #
> on_poweroff = 'preserve'
> on_reboot = 'restart'
> on_crash = 'preserve'
> #
> vcpus = 2
> #
> kernel = "/root/64958-test-armhf-armhf-libvirt-qcow2-
> di/kernel_jessie_armhf"
> ramdisk = "/root/64958-test-armhf-armhf-libvirt-qcow2-
> di/ramdisk_jessie_armhf"
>
> extra = "debian-installer/exit/poweroff=true domain=test-
> lab.xenproject.org console=hvc0 auto=true preseed hw-
> detect/load_firmware=false DEBCONF_DEBUG=5 DEBIAN_FRONTEND=text
> hostname=debian.jessie.guest.osstest url=osstest.test-
> lab.xenproject.org/~osstest/osstest/arndale-
> metrocentre_debian.jessie.guest.osstest_preseed netcfg/dhcp_timeout=150
> netcfg/choose_interface=auto -- console=hvc0"
> #
> disk = [
> 'format=qcow2,vdev=xvda,target=/var/lib/xen/images/debia
> n/disk.qcow2'
> ]
>
> #
>
> , flags=0
>
> and seemingly no information on the mysterious failure. The config looks
> perfectly find to me (and FWIW xl create likes it just fine)
>
> I'll dig in but I wondered if you had any pointers, to either what might
> be
> failing or why the error reporting seems to not filter through.
>
> Cheers,
> Ian.
>
> > test-armhf-armhf-xl-credit2 13 saverestore-support-
> > check fail never pass
> > test-armhf-armhf-xl-credit2 12 migrate-support-
> > check fail never pass
> > test-armhf-armhf-xl-vhd 11 migrate-support-
> > check fail never pass
> > test-armhf-armhf-xl-vhd 12 saverestore-support-
> > check fail never pass
> > test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-
> > check fail never pass
> > test-amd64-i386-libvirt 12 migrate-support-
> > check fail never pass
> >
> > version targeted for testing:
> > osstest 2b83c10eb530fbd6a501717deb5aac1beff0cf80
> > baseline version:
> > osstest b0c5663a03e7ad679841dea72785db4ca981efe8
> >
> > Last test of basis 64659 2015-11-18 01:58:35 Z 4 days
> > Testing same since 64958 2015-11-20 15:06:13 Z 1 days 1
> > attempts
> >
> > jobs:
> > build-amd64-xsm pass
> > build-armhf-xsm pass
> > build-i386-xsm pass
> > build-amd64 pass
> > build-armhf pass
> > build-i386 pass
> > build-amd64-libvirt pass
> > build-armhf-libvirt pass
> > build-i386-libvirt pass
> > build-amd64-pvops pass
> > build-armhf-pvops pass
> > build-i386-pvops pass
> > build-amd64-rumpuserxen pass
> > build-i386-rumpuserxen 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 fail
> > test-amd64-amd64-libvirt-xsm pass
> > test-armhf-armhf-libvirt-xsm fail
> > 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-xl-pvh-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-rumpuserxen-amd64 pass
> > test-amd64-amd64-xl-qemut-win7-amd64 pass
> > test-amd64-i386-xl-qemut-win7-amd64 fail
> > test-amd64-amd64-xl-qemuu-win7-amd64 pass
> > test-amd64-i386-xl-qemuu-win7-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 fail
> > test-amd64-i386-freebsd10-i386 pass
> > test-amd64-i386-rumpuserxen-i386 pass
> > test-amd64-amd64-xl-pvh-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 fail
> > test-amd64-i386-libvirt pass
> > test-amd64-amd64-xl-multivcpu pass
> > test-armhf-armhf-xl-multivcpu pass
> > test-amd64-amd64-qemuu-nested broken
> > 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 pass
> > test-amd64-amd64-i386-pvgrub pass
> > test-amd64-amd64-pygrub pass
> > test-armhf-armhf-libvirt-qcow2 fail
> > 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-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass
> > test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
> > test-amd64-amd64-libvirt-vhd pass
> > test-armhf-armhf-xl-vhd pass
> > test-amd64-amd64-xl-qemut-winxpsp3 pass
> > test-amd64-i386-xl-qemut-winxpsp3 pass
> > test-amd64-amd64-xl-qemuu-winxpsp3 pass
> > test-amd64-i386-xl-qemuu-winxpsp3 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=mas
> > ter
> >
> > Test harness code can be found at
> > http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
> >
> >
> > Not pushing.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-25 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-64958-mainreport@xen.org>
2015-11-25 14:37 ` [osstest test] 64958: regressions - trouble: broken/fail/pass Ian Campbell
2015-11-25 15:32 ` Ian Campbell [this message]
2015-12-03 1:33 ` Jim Fehlig
2015-12-03 9:31 ` Ian Campbell
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=1448465532.17688.122.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=jfehlig@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xen.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.