xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: manish jaggi <manishjaggi.oss@gmail.com>,
	xen-users@lists.xen.org, Vijay Kilari <vijay.kilari@gmail.com>,
	manish.jaggi@caviumnetworks.com, xen-devel@lists.xenproject.org
Subject: Re: How to dump vcpu regs when a domain is killed during xl create
Date: Tue, 19 Aug 2014 10:01:21 +0100	[thread overview]
Message-ID: <53F31261.5050107@citrix.com> (raw)
In-Reply-To: <CAAiw7J=mkFV-JoudBq_kU1oWMn+HhHuAOP7mJfxSS101qB6FhQ@mail.gmail.com>

On 19/08/14 06:11, manish jaggi wrote:
> Adding the question on xen-devel
>
> On 18 August 2014 14:08, manish jaggi <manishjaggi.oss@gmail.com> wrote:
>> I tried to start a domain using xl create, which showed some xen logs
>> and then hanged for a minute or so and then displayed a messgae
>> killed. Below is the log
>>
>> linux:~ # xl create domU.cfg
>> Parsing config from domU.cfg
>> (XEN)  ....
>> Killed
>>
>> Is there a way to know why it was killed and dump core regs (vcpu
>> regs) at the point it was killed.

There is no guarantee the domain has successfully started.

Put "loglvl=all guest_loglvl=all" on the Xen command line, reboot, and
attach the results of

xl -vvvv create domU.cfg

and xl dmesg after the domain has failed in this way.

~Andrew

  reply	other threads:[~2014-08-19  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAiw7J=RNK7kF_POT56-8x73+xno-0Ys02VZBnoQc6uozYQn3g@mail.gmail.com>
2014-08-19  5:11 ` How to dump vcpu regs when a domain is killed during xl create manish jaggi
2014-08-19  9:01   ` Andrew Cooper [this message]
2014-08-19 10:02     ` manish jaggi
2014-08-19 10:05       ` Andrew Cooper
2014-08-19 10:51         ` manish jaggi
2014-08-19 10:54           ` Andrew Cooper
2014-08-19 11:39             ` manish jaggi

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=53F31261.5050107@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=manishjaggi.oss@gmail.com \
    --cc=vijay.kilari@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xen-users@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).