From owner-freebsd-virtualization@FreeBSD.ORG Wed Jan 22 02:53:25 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA178CBA for ; Wed, 22 Jan 2014 02:53:25 +0000 (UTC) Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 79F681374 for ; Wed, 22 Jan 2014 02:53:25 +0000 (UTC) Received: by mail-oa0-f46.google.com with SMTP id n16so7139524oag.5 for ; Tue, 21 Jan 2014 18:53:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=tnTIr7vWFi1kDcmGY6wMUzSy3wCcj1aqEemE3k49lXE=; b=FN8hll6i9Ed9vigxm3Ne9TBOSRYQG6e/dyaMPLnMncSWR0kXav2JZz9PTika76oSWh 5Ppv9/lp/dTI7yMZUQTmmcoX/h8wPU9gEsD2vAz5OVCjtGH8DSPbX7ck+plo1g/wPsTV utpEL7mqEU9B6yFDy3MsmvV1mBL6EUCf1dcWM6TH9okpkk/BDfbYdlYcgi64hQEys1Bn /HUPNze2bL8dsvZRJMw5cPzMJccNUhVD3zDpBwTgGTQyvF6DwECTjAt4wINMd0OWCr/S u5KDMDI/ZOy253/ROTgZc3+Qomg9UyrE4V29OrOyRsFti0B+meUTu4RgWaERwduA4cfz 9Iuw== X-Received: by 10.182.29.66 with SMTP id i2mr24314733obh.23.1390359204402; Tue, 21 Jan 2014 18:53:24 -0800 (PST) Received: from [10.0.1.3] (ip72-209-165-165.ks.ks.cox.net. [72.209.165.165]) by mx.google.com with ESMTPSA id fn10sm11241178obb.12.2014.01.21.18.53.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 18:53:23 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: kldload vmm partial lockup From: Joe Maloney In-Reply-To: Date: Tue, 21 Jan 2014 20:53:17 -0600 Message-Id: <52A1E4D3-9625-40B7-AF4A-2EAFBF3A7025@gmail.com> References: <9C504625-F183-455E-A0FD-F9A5EC5FA944@gmail.com> To: Neel Natu X-Mailer: Apple Mail (2.1827) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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: Wed, 22 Jan 2014 02:53:25 -0000 Neel, sorry it took me a day or two to get to test this. The patch compiles = cleanly however it fails now trying to build the vmm module. Joe Maloney /usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:232:7: error: implicit = declaration of function 'ppt_avail_devices' is invalid in C99 [-Werror,-Wimplicit-function-declaration] if (ppt_avail_devices() > 0) ^ /usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:565:6: error: implicit = declaration of function 'ppt_assigned_devices' is invalid in C99 [-Werror,-Wimplicit-function-declaration] if (ppt_assigned_devices(vm) =3D=3D 0) { ^ /usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:565:6: note: did you mean = 'ppt_assign_device'? if (ppt_assigned_devices(vm) =3D=3D 0) { ^~~~~~~~~~~~~~~~~~~~ ppt_assign_device /usr/src/sys/modules/vmm/../../amd64/vmm/io/ppt.h:46:5: note: = 'ppt_assign_device' declared here int ppt_assign_device(struct vm *vm, int bus, int slot, int func); ^ 2 errors generated. *** Error code 1 Stop. make[4]: stopped in /usr/src/sys/modules/vmm *** Error code 1 Stop. make[3]: stopped in /usr/src/sys/modules *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/sys/GENERIC *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src root@jmhome-pc:/usr/src #=20 On Jan 19, 2014, at 8:43 PM, Neel Natu wrote: > Hi Joe, >=20 > 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 specs: >>=20 >> FreeBSD 10.0 64 bit >> ASUS P6T Deluxe >> Intel i7 920 >>=20 >> According to what I=92ve researched my cpu should have the VT-D = extensions. However many users of this motherboard have complained = about ASUS not properly 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 which is the Xen wiki it even states that this = motherboard needs a bios update which is not available to the public. >>=20 >> https://communities.intel.com/thread/28389 >>=20 >> = http://vip.asus.com/forum/view.aspx?id=3D20090402224408018&SLanguage=3Den-= us&board_id=3D1 >>=20 >> http://wiki.xen.org/wiki/VTd_HowTo >>=20 >> I am curious though if this would be what would be causing my problem = with bhyve? I suppose I am willing to just by a new motherboard if so. >>=20 >> 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 repeats 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. >>=20 >> Is there a way I can gather more logs somehow so that I can determine = what text is appearing before the uhci errors? Perhaps some kind of = dump procedure? Or is there a way I can confirm that freebsd can = properly see and utilize the VT-D extensions. VirtualBox runs fine with = the VT extensions enabled. I also made sure VirtualBox wasn=92t = installed or loaded before I tried bhyve. I=92ve tried to research for = a week or two before posting here. >>=20 >=20 > I have a patch to not initialize the iommu unless there are passthru > devices explicitly configured for bhyve to use. >=20 > It is available here: > http://people.freebsd.org/~neel/patches/bhyve_iommu_init.patch >=20 > Could you give it a spin and see if it helps with the ASUS system? >=20 > best > Neel >=20 >> Joe Maloney >>=20 >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to = "freebsd-virtualization-unsubscribe@freebsd.org"