From: David F Barrera <dfbp@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: xen-devel@lists.xensource.com, stoeni <xen@stoeni.de>
Subject: Re: cannot start more than one domU
Date: Wed, 09 Nov 2005 10:43:15 -0600 [thread overview]
Message-ID: <43722723.4040604@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017305DA9BDC@scsmsx402.amr.corp.intel.com>
Nakajima, Jun wrote:
>David F Barrera wrote:
>
>
>>stoeni wrote:
>>
>>
>>
>>>hi,
>>>
>>>attached you find the xm dmesg output of my xen-unstable machine,
>>>first
>>>domU starts correct, second/third crashes (see log).
>>>
>>>dom0 and domU were both compiled with smp support (smt enabled) on a
>>>dual xeon 2.8.
>>>
>>>did i missed something at kernel configuration?
>>>
>>>
>>>
>>>
>>No. I reported this problem some time back and am still seeing it
>>daily: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=267
>>
>>
>>
>
>Sounds like a critical bug. Is anybody taking a look at this? BTW, is
>this specific to PAE?
>
>
I've only seen it on a PAE enabled box.
>
>Jun
>---
>Intel Open Source Technology Center
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-11-09 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 16:39 cannot start more than one domU Nakajima, Jun
2005-11-09 16:43 ` David F Barrera [this message]
2005-11-09 19:42 ` David F Barrera
-- strict thread matches above, loose matches on Subject: below --
2005-11-09 16:59 Nakajima, Jun
2005-11-09 17:15 ` David F Barrera
2005-11-09 20:50 ` stoeni
2005-11-09 16:48 Ian Pratt
2005-11-09 16:55 ` David F Barrera
2005-11-09 15:23 stoeni
2005-11-09 16:04 ` David F Barrera
2005-11-10 20:11 ` stoeni
2005-11-11 18:12 ` Keir Fraser
2005-11-11 21:24 ` stoeni
2005-11-15 23:13 ` stoeni
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=43722723.4040604@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen@stoeni.de \
/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.