xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Vitaliy Tomin <highwaystar.ru@gmail.com>
Cc: Jan Beulich <JBeulich@suse.com>,
	Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: HVM crash system on AMD APU A8-6600K
Date: Thu, 10 Apr 2014 16:59:17 +0100	[thread overview]
Message-ID: <5346BFD5.5000900@citrix.com> (raw)
In-Reply-To: <CABPT1LuxW3cLrF74SN5FV41R6tGX6eq-5i2U7Tb712UDHStS7w@mail.gmail.com>

Please do try to remember to reply-to-all.

On 10/04/14 16:47, Vitaliy Tomin wrote:
>> At what point does it crash?  Immediately after you create an HVM
> guests, or some while afterwards?
>
>
> It mostly crashes after 30-60 seconds from run. Actually point somehow
> depends on host system load (maybe used memory). If I have opened
> browser or other heavy applications on host system it crashes faster,
> if I doesnt run anything on host OS but only hvm domain it runs longer
> up to 5 minutes.
>
>> Elsewhere on the thread, you have serial logs from debug builds of Xen.
> Do you have serial logs from non-debug builds?
>
> All logs I posted made with non debug build of xen and ends on crash.
> I can make logs with working debug build. Which options should I pass
> to commandline?

Can you get logs from a debug and non debug build of Xen, with at least
"loglvl=all guest_loglvl=all hap=0 iommu=0" on the command line.  For
the non debug version, can you boot and shut down the HVM guest.

Given the (hopefully correct) disabling of hap and the iommu, we are
left with AMD SVM left as the likely suspect for problems.

~Andrew

  parent reply	other threads:[~2014-04-10 15:59 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 13:47 HVM crash system on AMD APU A8-6600K Vitaliy Tomin
2014-02-03 13:51 ` Andrew Cooper
2014-02-03 13:58   ` Vitaliy Tomin
2014-02-03 14:08     ` Sander Eikelenboom
2014-02-03 14:09     ` Andrew Cooper
     [not found]       ` <CABPT1LscUZR_V1TOAzVmkvSms0M_Yucjp8WtUaeOADD_G-EbHA@mail.gmail.com>
2014-02-03 14:22         ` Vitaliy Tomin
2014-02-03 14:32         ` Andrew Cooper
2014-02-03 14:36           ` Vitaliy Tomin
2014-02-03 14:41             ` Andrew Cooper
2014-02-03 14:55             ` Konrad Rzeszutek Wilk
2014-02-03 15:18               ` Vitaliy Tomin
2014-02-03 15:47                 ` Boris Ostrovsky
2014-02-13 14:37                   ` Vitaliy Tomin
2014-04-07 15:36                     ` George Dunlap
2014-04-08  8:18                       ` Jan Beulich
2014-04-08  8:40                         ` Vitaliy Tomin
2014-04-08  9:14                           ` Jan Beulich
2014-04-08 12:53                             ` Vitaliy Tomin
2014-04-08 14:00                               ` Sander Eikelenboom
2014-04-08 15:23                                 ` Vitaliy Tomin
2014-04-08 16:02                                   ` Jan Beulich
2014-04-08 15:29                                 ` Vitaliy Tomin
2014-04-08 16:10                                   ` Sander Eikelenboom
2014-04-08 16:17                                     ` Konrad Rzeszutek Wilk
2014-04-09  1:43                                       ` Vitaliy Tomin
2014-04-10 13:01                                         ` Vitaliy Tomin
2014-04-10 13:30                                           ` Andrew Cooper
2014-04-10 13:56                                             ` Vitaliy Tomin
2014-04-10 13:59                                               ` Andrew Cooper
2014-04-10 14:33                                               ` Jan Beulich
2014-04-10 15:21                                                 ` Vitaliy Tomin
2014-04-10 15:23                                                   ` Andrew Cooper
2014-04-10 15:34                                                     ` Vitaliy Tomin
2014-04-10 15:39                                                       ` Andrew Cooper
     [not found]                                                         ` <CABPT1LuxW3cLrF74SN5FV41R6tGX6eq-5i2U7Tb712UDHStS7w@mail.gmail.com>
2014-04-10 15:59                                                           ` Andrew Cooper [this message]
2014-04-11 11:57                                                             ` Vitaliy Tomin
2014-04-11 13:30                                                               ` Jan Beulich
2014-05-03 15:43                                                                 ` Vitaliy Tomin
2014-05-05 11:06                                                                   ` Andrew Cooper
2014-05-05 11:24                                                                     ` Jan Beulich
2014-05-05 15:36                                                                       ` Vitaliy Tomin
2014-05-05 15:41                                                                         ` Jan Beulich
2014-04-08 13:07                         ` George Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2013-11-02  9:51 Vitaliy Tomin
2014-04-02 14:44 ` George Dunlap
2014-04-07 14:50   ` Vitaliy Tomin

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=5346BFD5.5000900@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=highwaystar.ru@gmail.com \
    --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).