From: Vasiliy G Tolstov <v.tolstov@selfip.ru>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>
Subject: Re: [Xen-devel] [PATCH 0/2] Xen PV on HVM multiple PV consoles
Date: Mon, 06 Dec 2010 16:03:34 +0300 [thread overview]
Message-ID: <1291640614.32324.85.camel@work.selfip.ru> (raw)
In-Reply-To: <alpine.DEB.2.00.1012061035070.9029@kaball-desktop>
On Mon, 2010-12-06 at 10:36 +0000, Stefano Stabellini wrote:
>
> Could you please add CONFIG_DEBUG_INFO=y to your kernel config, so that
> we can see the name of the functions in the stack trace?
>
After add debug kernel not crushed. I'm test more expensive it now. Can
You provide ps auxwww | grep qemu-dm after creating domain with two
serial consoles? (sles does not have libxl, i want to write now wrapper
to qemu-dm, after that try to compile rpm from spec to support libxl).
--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru
next prev parent reply other threads:[~2010-12-06 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 18:25 [PATCH 0/2] Xen PV on HVM multiple PV consoles Stefano Stabellini
2010-12-01 18:26 ` [PATCH 1/2] hvc_xen: support PV on HVM consoles stefano.stabellini
2010-12-01 18:26 ` [PATCH 2/2] hvc_xen: implement multiconsole support stefano.stabellini
2010-12-01 20:43 ` [PATCH 0/2] Xen PV on HVM multiple PV consoles Vasiliy G Tolstov
2010-12-02 17:21 ` Stefano Stabellini
2010-12-03 19:35 ` [Xen-devel] " Vasiliy G Tolstov
2010-12-06 10:36 ` Stefano Stabellini
2010-12-06 13:03 ` Vasiliy G Tolstov [this message]
2010-12-07 10:30 ` Stefano Stabellini
2010-12-09 11:00 ` Vasiliy G Tolstov
2010-12-09 12:12 ` Pasi Kärkkäinen
2010-12-09 12:15 ` [Xen-devel] " Vasiliy G Tolstov
2010-12-09 18:07 ` Jeremy Fitzhardinge
2010-12-09 18:16 ` Pasi Kärkkäinen
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=1291640614.32324.85.camel@work.selfip.ru \
--to=v.tolstov@selfip.ru \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).