From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Xen 4.0.0-rc7 problem/hang with vt-d DMAR parsing Date: Tue, 23 Mar 2010 22:05:15 +0200 Message-ID: <20100323200515.GZ1878@reaktio.net> References: <20100323193748.GW1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Weidong Han List-Id: xen-devel@lists.xenproject.org On Tue, Mar 23, 2010 at 07:54:33PM +0000, Keir Fraser wrote: > On 23/03/2010 19:37, "Pasi K=E4rkk=E4inen" wrote: >=20 > >> It's not impossible that the BIOS VT-d support is just broken (I ass= ume > >> you've never tested VT-d on this particular type of system before). > >=20 > > Yeah, I've never used VT-d on this system earlier, so it could just b= e broken > > BIOS. > > I guess Xen still shouldn't hang on it? >=20 > We'd prefer to gracefully disable VT-d. >=20 4.0.0-rc7 (without any extra cmdline options) does disable vt-d and boot = ok,=20 after 'hanging' for 30 seconds while parsing the DMAR tables. If I add "iommu=3Dverbose" option for Xen, then it'll print huge amount o= f stuff=20 like I pasted earlier.. and it takes forever to print all that. Hmm.. wondering if the patch Jan just sent will help with that.=20 Sounds like it might help :) -- Pasi