From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk 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 Message-ID: <20110111172002.GJ10897@dumpdata.com> References: <4D0AD782.8030204@wavecon.de> <4D0B3DF2.5000100@wavecon.de> <20101217115132.GG2754@reaktio.net> <4D0B7E79.4010106@wavecon.de> <20101220201819.GN2754@reaktio.net> <1292937209.4500.1852.camel@zakaz.uk.xensource.com> <4D2496DE.1000007@wavecon.de> <20110111163828.GF10897@dumpdata.com> <4D2C8D6C.1080906@wavecon.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4D2C8D6C.1080906@wavecon.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Arno Toell , andrew.thomas@oracle.com Cc: "xen-devel@lists.xensource.com" , Ian Campbell , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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?