From: "Steven Hand" <steven.hand@cl.cam.ac.uk>
To: "Zulauf, John" <john.zulauf@intel.com>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
xen-devel@lists.xensource.com
Subject: Re: Dom0 Hang for large VCPU counts > PCPU
Date: Wed, 24 Jan 2007 19:49:34 -0000 [thread overview]
Message-ID: <07ec01c73ff0$c5e1a9b0$0302a8c0@Violet> (raw)
In-Reply-To: BD262A443AD428499D90AF8368C4528D2A77FB@fmsmsx411.amr.corp.intel.com
With FC6 (or any 2.6.18 kernel) there's an issue using the tsc clocksource
(we're working
on a fix); may not be related but could be worth booting with
"clocksource=acpi_pm".
cheers,
S.
----- Original Message -----
From: "Zulauf, John" <john.zulauf@intel.com>
To: "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk>;
<xen-devel@lists.xensource.com>
Sent: Wednesday, January 24, 2007 7:28 PM
Subject: RE: [Xen-devel] Dom0 Hang for large VCPU counts > PCPU
________________________________________
On January 24, 2007 11:11 AM Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
wrote
> On 24/1/07 6:56 pm, "Zulauf, John" <john.zulauf@intel.com> wrote:
>
> > Using xen-3.0.4-testing with an HVM booting the FC6 DVD on a Core2 Duo
> > (i.e. 2 PCPU) on a 965 chipset
> >
> > VCPU=17 - works
> > VCPU=20 - works (takes a very long time)
> > VCPU=24 - lockup (whole machine, yes I mean Dom0)
> > VCPU=31 - same
> > VCPU=32 - same
>
> Have you worked out where it gets stuck? Do many-VCPU domU guests fare
> better?
It IS dying for a domU guests. Do you perhaps mean PV guests? No we
haven't tried them. I don't have any at the moment to test.
Clarifying the initial report:
Host is 2 core (Core 2 Duo/965 chipset) box with VPCU=PCPU for Dom0.
Issue occurs when attempting to start an HVM DomU with VCPU >= 24 (though we
haven't checked 21-23 yet).
The DomU never(apparently) starts, and Dom0 hard hangs. (i.e. not even the
numlock key works)
Given that Dom0 hangs hard when this occurs, we don't have any ideas as to
the exact cause of death.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-01-24 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 18:56 Dom0 Hang for large VCPU counts > PCPU Zulauf, John
2007-01-24 19:10 ` Keir Fraser
2007-01-24 19:28 ` Zulauf, John
2007-01-24 19:44 ` Keir Fraser
2007-01-24 19:49 ` Steven Hand [this message]
2007-01-24 22:04 ` Zulauf, John
2007-01-24 19:34 ` Woller, Thomas
2007-01-26 0:42 ` Zulauf, John
2007-01-28 18:52 ` Woller, Thomas
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='07ec01c73ff0$c5e1a9b0$0302a8c0@Violet' \
--to=steven.hand@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=john.zulauf@intel.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 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.