From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: stubdom crash, xen 4.2.1, libxl
Date: Mon, 15 Apr 2013 23:24:53 +0200 [thread overview]
Message-ID: <516C7025.4050001@invisiblethingslab.com> (raw)
In-Reply-To: <51656A3C.8050601@invisiblethingslab.com>
[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]
On 10.04.2013 15:33, Marek Marczykowski wrote:
> On 10.04.2013 15:29, Ian Campbell wrote:
>> On Tue, 2013-04-09 at 15:27 +0100, Marek Marczykowski wrote:
>>> Hi all,
>>>
>>> I've tried to use stubdom under xen 4.2. The same config that worked with xen
>>> 4.1, crashed with xen 4.2.
>>
>> You mean the stubdom itself crashed?
>
> Yes.
>
>> Are you able to capture its console?
>
> It crashed before any output on console. Only visible with "c" state on xl
> list. When I've attached to it via gdbsx it point out first line of main(), so
> stubdom code doesn't even begin to execute. I can provide core dump if it can
> help.
Can anyone send me working config for HVM with stubdom for xl (4.2)?
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 553 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-15 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:27 stubdom crash, xen 4.2.1, libxl Marek Marczykowski
2013-04-10 13:29 ` Ian Campbell
2013-04-10 13:33 ` Marek Marczykowski
2013-04-15 21:24 ` Marek Marczykowski [this message]
2013-04-17 15:54 ` Anthony PERARD
2013-04-18 1:21 ` Marek Marczykowski
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=516C7025.4050001@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=Ian.Campbell@citrix.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 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.