From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 30769: regressions - trouble: blocked/broken/fail/pass
Date: Fri, 17 Oct 2014 16:06:30 -0400 [thread overview]
Message-ID: <20141017200630.GC17012@laptop.dumpdata.com> (raw)
In-Reply-To: <osstest-30769-mainreport@xen.org>
On Fri, Oct 17, 2014 at 03:42:44AM +0100, xen.org wrote:
> flight 30769 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30769/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-xl-qemut-winxpsp3 10 guest-localmigrate fail REGR. vs. 30744
That shows that the save is happening:
http://www.chiark.greenend.org.uk/~xensrcts/logs/30769/test-amd64-i386-xl-qemut-winxpsp3/serial-rice-weevil.log
ct 16 21:46:15.654615 (XEN) HVM4 save: VIRIDIAN_VCPU
Oct 16 21:46:15.654642 (XEN) HVM4 save: VMCE_VCPU
Oct 16 21:46:15.654672 (XEN) HVM4 save: TSC_ADJUST
...
and then the restore:
Oct 16 21:46:37.474614 (XEN) HVM5 restore: TSC_ADJUST 0
Oct 16 21:46:37.474647 (XEN) HVM5 restore: TSC_ADJUST 1
Oct 16 21:46:37.474674 [ 1406.549487] device vif5.0 entered promiscuous mode
Oct 16 21:46:37.962607 [ 1406.552350] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
Oct 16 21:46:37.962652 [ 1406.663239] device vif5.0-emu entered promiscuous mode
Oct 16 21:46:38.074609 [ 1406.666168] xenbr0: port 3(vif5.0-emu) entered forwarding state
Oct 16 21:46:38.082590 [ 1406.666191] xenbr0: port 3(vif5.0-emu) entered forwarding state
.. with all of the NICs seeming to go in the right state.
Is there a particular file that has the output from 'xl migrate'?
Thought it probably will be nop as the save/restore worked fine.
> build-i386-rumpuserxen 3 host-install(3) broken REGR. vs. 30744
> test-amd64-i386-pair 7 xen-boot/src_host fail REGR. vs. 30744
Looking at the log, the reboot was initiated at 2014-10-17 01:48:17
and the serial log shows:
Oct 17 01:48:24.872878 [ 3440.256448] Restarting system.
So the reboot did get started..
And then:
Oct 17 01:52:00.570602 scape-moth login:
The machine (so 4 minutes later) is back on.
Maybe this:
2014-10-17 01:51:13 Z reboot-confirm-booted: waiting 40s...
should be expanded to 360 seconds?
>
> Tests which did not succeed, but are not blocking:
> test-amd64-amd64-libvirt 9 guest-start fail never pass
> test-armhf-armhf-libvirt 9 guest-start fail never pass
> test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a
> test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
> test-armhf-armhf-xl 10 migrate-support-check fail never pass
> test-amd64-i386-libvirt 9 guest-start fail never pass
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop fail never pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop fail never pass
> test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-winxpsp3 14 guest-stop fail never pass
> test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop fail never pass
> test-amd64-amd64-xl-winxpsp3 14 guest-stop fail never pass
> test-amd64-i386-xl-winxpsp3 14 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop fail never pass
> test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass
> test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop fail never pass
> test-amd64-amd64-xl-win7-amd64 14 guest-stop fail never pass
> test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop fail never pass
> test-amd64-i386-xl-win7-amd64 14 guest-stop fail never pass
> test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop fail never pass
>
> version targeted for testing:
> xen 9cea500dc0294947b12b8e2479a238acd0e990f2
> baseline version:
> xen 4d57153b52a36183d58e8de6ba613929f906386a
>
> ------------------------------------------------------------
> People who touched revisions under test:
> Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
> Chao Peng <chao.p.peng@linux.intel.com>
> Dongxiao Xu <dongxiao.xu@intel.com>
> Jan Beulich <jbeulich@suse.com>
> Wei Liu <wei.liu2@citrix.com>
> ------------------------------------------------------------
>
> jobs:
> build-amd64 pass
> build-armhf pass
> build-i386 pass
> build-amd64-libvirt pass
> build-armhf-libvirt pass
> build-i386-libvirt pass
> build-amd64-oldkern pass
> build-i386-oldkern pass
> build-amd64-pvops pass
> build-armhf-pvops pass
> build-i386-pvops pass
> build-amd64-rumpuserxen pass
> build-i386-rumpuserxen broken
> test-amd64-amd64-xl pass
> test-armhf-armhf-xl pass
> test-amd64-i386-xl pass
> test-amd64-i386-rhel6hvm-amd pass
> 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 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-win7-amd64 fail
> test-amd64-i386-xl-win7-amd64 fail
> test-amd64-i386-xl-credit2 pass
> test-amd64-i386-freebsd10-i386 pass
> test-amd64-i386-rumpuserxen-i386 blocked
> test-amd64-amd64-xl-pcipt-intel fail
> test-amd64-i386-rhel6hvm-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-i386-xl-multivcpu pass
> test-amd64-amd64-pair pass
> test-amd64-i386-pair fail
> test-amd64-amd64-xl-sedf-pin pass
> test-amd64-amd64-xl-sedf pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-winxpsp3-vcpus1 fail
> test-amd64-amd64-xl-qemut-winxpsp3 fail
> test-amd64-i386-xl-qemut-winxpsp3 fail
> test-amd64-amd64-xl-qemuu-winxpsp3 fail
> test-amd64-i386-xl-qemuu-winxpsp3 fail
> test-amd64-amd64-xl-winxpsp3 fail
> test-amd64-i386-xl-winxpsp3 fail
>
>
> ------------------------------------------------------------
> sg-report-flight on osstest.cam.xci-test.com
> logs: /home/xc_osstest/logs
> images: /home/xc_osstest/images
>
> Logs, config files, etc. are available at
> http://www.chiark.greenend.org.uk/~xensrcts/logs
>
> Test harness code can be found at
> http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
>
> broken-step build-i386-rumpuserxen host-install(3)
>
> Not pushing.
>
> ------------------------------------------------------------
> commit 9cea500dc0294947b12b8e2479a238acd0e990f2
> Author: Jan Beulich <jbeulich@suse.com>
> Date: Thu Oct 16 10:08:39 2014 +0200
>
> move XENMEM_get_vnumainfo out of tools-only section of public/memory.h
>
> After all this interface specifically exists for guest kernels to learn
> about their (virtual) topology. I'm sure I made a comment to this
> effect during review, but apparently I then didn't notice that this
> never got carried out.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> commit 4c5e3a8e84f2158487d8f403b3053c52d8ee2dd7
> Author: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
> Date: Thu Oct 16 10:07:56 2014 +0200
>
> docs, amd_ucode: condense amd_ucode notes
>
> Some cleanups to the documentation-
> - Remove unnecessary steps listed to apply ucode using initrd.
> - Condense 'Misc notes' section as well
>
> Suggested-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Signed-off-by: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
>
> commit 747187995dd8cb28dcac1db8851d60e54f85f8e4
> Author: Chao Peng <chao.p.peng@linux.intel.com>
> Date: Thu Oct 9 12:02:04 2014 +0800
>
> tools: CMDs and APIs for Cache Monitoring Technology
>
> Introduced some new xl commands to enable/disable Cache Monitoring
> Technology(CMT) feature.
>
> The following two commands is to attach/detach the CMT feature
> to/from a certain domain.
>
> $ xl psr-cmt-attach domid
> $ xl psr-cmt-detach domid
>
> This command is to display the CMT information, such as L3 cache
> occupancy.
>
> $ xl psr-cmt-show cache_occupancy <domid>
>
> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
> (qemu changes not included)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-17 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 2:42 [xen-unstable test] 30769: regressions - trouble: blocked/broken/fail/pass xen.org
2014-10-17 20:06 ` Konrad Rzeszutek Wilk [this message]
2014-10-20 16:56 ` Ian Jackson
2014-10-21 8:16 ` Ian Campbell
2014-10-21 13:46 ` Ian Jackson
2014-10-21 13:59 ` 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=20141017200630.GC17012@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.