From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Arno Toell <at@wavecon.de>, andrew.thomas@oracle.com
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] Re: Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic
Date: Tue, 11 Jan 2011 12:20:02 -0500 [thread overview]
Message-ID: <20110111172002.GJ10897@dumpdata.com> (raw)
In-Reply-To: <4D2C8D6C.1080906@wavecon.de>
On Tue, Jan 11, 2011 at 06:03:40PM +0100, Arno Toell wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11.01.2011 17:38, Konrad Rzeszutek Wilk wrote:
> > It could have been that was what you hit. I don't remember the changeset
> > number, but you could try booting your old hypervisor without the Vt-D
> > and see if that was it (iommu=off) ?
>
> Chances are, as I already mentioned the machine boots fine if I disable
> VMX in bios. Booting with "iommu=off" has the same effect.
>
> I skipped through the changelogs recently and found, one (or more) of
> the following changesets _should_ fix the issue. I'm lacking any
> knowledge about the hypervisor's internal subsystems and code paths
> though. So my seeked fix might or might not be within that subset at all.
>
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/aced00366822
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/c9f461d6ea1d
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/f7d54e1d7044
This is not the bug you are hitting, but that fix is important.
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/81a636dd784d
Ditto
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/9c7b9e65bc37
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/ae381a864b4f
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/4e689840622f
>
> As said, I look for the exact fix, to get Debian people a hint about
> what to backport for their 4.0.1 soon-to-be-stable package.
Hmm, let me ping Andrew, he might know. Andrew, do you remember what fix
you needed to get Dom0 to boot when you had more than 64GB of memory
with the VT-d enabled?
next prev parent reply other threads:[~2011-01-11 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D0AD782.8030204@wavecon.de>
[not found] ` <4D0B3DF2.5000100@wavecon.de>
[not found] ` <20101217115132.GG2754@reaktio.net>
[not found] ` <4D0B7E79.4010106@wavecon.de>
2010-12-20 20:18 ` [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic Pasi Kärkkäinen
2010-12-20 20:20 ` Arno Toell
2010-12-21 13:13 ` Re: [Xen-users] " Ian Campbell
2010-12-23 11:13 ` [Xen-devel] " Arno Toell
2010-12-27 15:28 ` Re: [Xen-users] " Konrad Rzeszutek Wilk
2011-01-05 10:58 ` [Xen-devel] " Pasi Kärkkäinen
2011-01-05 16:05 ` Arno Toell
2011-01-05 16:16 ` Re: [Xen-users] " Ian Campbell
2011-01-11 16:38 ` Konrad Rzeszutek Wilk
2011-01-11 17:03 ` [Xen-devel] " Arno Toell
2011-01-11 17:20 ` Konrad Rzeszutek Wilk [this message]
2011-01-11 18:39 ` andrew thomas
2011-01-12 11:55 ` Arno Toell
2011-01-13 12:11 ` Arno Toell
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=20110111172002.GJ10897@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.thomas@oracle.com \
--cc=at@wavecon.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).