From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: How to dump vcpu regs when a domain is killed during xl create Date: Tue, 19 Aug 2014 10:01:21 +0100 Message-ID: <53F31261.5050107@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJfIE-0001RT-6m for xen-devel@lists.xenproject.org; Tue, 19 Aug 2014 09:01:26 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: manish jaggi , xen-users@lists.xen.org, Vijay Kilari , manish.jaggi@caviumnetworks.com, xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On 19/08/14 06:11, manish jaggi wrote: > Adding the question on xen-devel > > On 18 August 2014 14:08, manish jaggi 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