From owner-freebsd-virtualization@FreeBSD.ORG Mon Jan 20 02:43:33 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9139AC4 for ; Mon, 20 Jan 2014 02:43:33 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 780161398 for ; Mon, 20 Jan 2014 02:43:33 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id cm18so5092872qab.23 for ; Sun, 19 Jan 2014 18:43:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=kJT+WpMTo29yxeZomoC0jGo6M7k2+xPitYdMUNSM4NA=; b=zMgC0bGfuNU72HFETXuKQYFYOYtDbAKuqYBdgSSYA5bT+LCUUAvvPQeGcwRMCHXkx2 busY1TXkZdxQvJZiYDJhPRfQr9t6/RSTLR75b/R/DbcftfmiKW9jBnlETS4iNhCtJa/T 2bOLXFmMkXmrngQKNMZJyJ+ToFmQq+mi2RRrUEMtUYuaTn5rbqzo0t8ryZfZahzh7GVy uRDME5ciXwbD0U7huaMwFNTweWL3s2oLQ/dMETxNlerqZStT+IQDjqSKaIcAYWCl52nX 4Z4gpnyZoLyOyi8C22jT2xKUxsEntRTl7a4JbYVANQVJp3YxvkEjOocQyuVu+/u2fC08 a84Q== MIME-Version: 1.0 X-Received: by 10.224.167.19 with SMTP id o19mr22524272qay.77.1390185812111; Sun, 19 Jan 2014 18:43:32 -0800 (PST) Received: by 10.140.34.17 with HTTP; Sun, 19 Jan 2014 18:43:32 -0800 (PST) In-Reply-To: <9C504625-F183-455E-A0FD-F9A5EC5FA944@gmail.com> References: <9C504625-F183-455E-A0FD-F9A5EC5FA944@gmail.com> Date: Sun, 19 Jan 2014 18:43:32 -0800 Message-ID: Subject: Re: kldload vmm partial lockup From: Neel Natu To: Joe Maloney Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 02:43:33 -0000 Hi Joe, On Sun, Jan 19, 2014 at 2:21 PM, Joe Maloney wrote: > I=92ve been trying to get bhyve to work on a system with the following sp= ecs: > > FreeBSD 10.0 64 bit > ASUS P6T Deluxe > Intel i7 920 > > According to what I=92ve researched my cpu should have the VT-D extension= s. However many users of this motherboard have complained about ASUS not p= roperly supporting VT-D with Xen and something about a problem with tables = getting corrupt due to a problem with the bios. On the third link below wh= ich is the Xen wiki it even states that this motherboard needs a bios updat= e which is not available to the public. > > https://communities.intel.com/thread/28389 > > http://vip.asus.com/forum/view.aspx?id=3D20090402224408018&SLanguage=3Den= -us&board_id=3D1 > > http://wiki.xen.org/wiki/VTd_HowTo > > I am curious though if this would be what would be causing my problem wit= h bhyve? I suppose I am willing to just by a new motherboard if so. > > I can run kldload vmm and I see a bunch of text fly by and then something= about uhci interrupt problem. As soon as that happens the messages repeat= s my network drops and no keyboard input. However the message repeats and = it doesn=92t appear that the system has fully locked up otherwise. However= on another system that works I notice that kldload VMM does not show this = information it just loads the module. > > Is there a way I can gather more logs somehow so that I can determine wha= t text is appearing before the uhci errors? Perhaps some kind of dump proc= edure? Or is there a way I can confirm that freebsd can properly see and u= tilize the VT-D extensions. VirtualBox runs fine with the VT extensions en= abled. I also made sure VirtualBox wasn=92t installed or loaded before I t= ried bhyve. I=92ve tried to research for a week or two before posting here= . > I have a patch to not initialize the iommu unless there are passthru devices explicitly configured for bhyve to use. It is available here: http://people.freebsd.org/~neel/patches/bhyve_iommu_init.patch Could you give it a spin and see if it helps with the ASUS system? best Neel > Joe Maloney > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org"