xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Schinker <ba1020@homie.homelinux.net>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: Test Xen 4.8 RC5 instable 04.11.16
Date: Fri, 4 Nov 2016 11:18:40 +0000	[thread overview]
Message-ID: <20161104111840.GF30231@citrix.com> (raw)
In-Reply-To: <787018292.26.1478258009864.JavaMail.zimbra@homie.homelinux.net>

On Fri, Nov 04, 2016 at 11:13:29AM +0000, Juergen Schinker wrote:
> * Hardware:
>  Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz
>  Sandisk SSD 1T
>  32G Ram
> * Software:
> 
> Debian Stretch/testing is dom0
>  
> * Guest operating systems:
> 
> Guests Ubuntu 14.04 LTS Debian Stretch/Sid 
> 
> Ubuntu 16.10 yakity yak with latest 4.8 kernel works 
>  
> * Functionality tested:
> xl 
> creating booting 
> pygrub
> credit2
> 
> * Comments:
> 
>  I compiled the latest vanilla kernel for gpu-passthrough with single gpu -
> 
> rc5 runs ca. 1h then freeze - which log should i check for ?
>  

If the guest freezes, you can have a look at guest serial output, Dom0
dmesg and xen dmesg (xl dmesg).

If the host freezes, you will need to setup a serial console and uses
another machine to capture the log as it goes.

> 
> host                   : xen
> release                : 4.8.5-xen
> version                : #1 SMP PREEMPT Mon Oct 31 20:31:38 GMT 2016
> machine                : x86_64
> nr_cpus                : 4
> max_cpu_id             : 3
> nr_nodes               : 1
> cores_per_socket       : 2
> threads_per_core       : 2
> cpu_mhz                : 2312
> hw_caps                : b7ebfbff:77bae3ff:28100800:00000001:00000001:00000281:00000000:00000100
> virt_caps              : hvm hvm_directio
> total_memory           : 32711
> free_memory            : 4133
> sharing_freed_memory   : 0
> sharing_used_memory    : 0
> outstanding_claims     : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 8
> xen_extra              : .0-rc
> xen_version            : 4.8.0-rc
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
> xen_scheduler          : credit2
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : Mon Oct 31 13:21:56 2016 +0000 git:496673a
> xen_commandline        : placeholder sched=credit2 iommu=1
> cc_compiler            : gcc (Debian 6.2.0-9) 6.2.0 20161019
> cc_compile_by          : root
> cc_compile_domain      : 
> cc_compile_date        : Thu Nov  3 20:55:16 GMT 2016
> build_id               : de5b411bee8c8590609ddfe7f425344deee707ba
> xend_config_format     : 4

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-04 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 11:13 Test Xen 4.8 RC5 instable 04.11.16 Juergen Schinker
2016-11-04 11:18 ` Wei Liu [this message]
2016-11-04 17:29   ` Dario Faggioli
2016-11-04 18:11     ` Juergen Schinker
2016-11-04 18:31       ` Dario Faggioli
2016-11-04 18:52         ` Juergen Schinker

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=20161104111840.GF30231@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=ba1020@homie.homelinux.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).