From owner-freebsd-virtualization@FreeBSD.ORG Thu Jan 23 03:40:22 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 A5624841 for ; Thu, 23 Jan 2014 03:40:22 +0000 (UTC) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 73C181656 for ; Thu, 23 Jan 2014 03:40:22 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rp16so1279112pbb.6 for ; Wed, 22 Jan 2014 19:40:22 -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 :content-transfer-encoding:message-id:references:to; bh=iPkdryXSJzl37Y6WItFeOCUbbW5cai6waYufCs08qAs=; b=p6d7qOaF9JLxRjwGP4knpLFmOCpFugVq744yluc8C1uaPr+nxdLSV8CgZiv7eO0sIC UJOSzC6t2dpIyVeymkgEPKYNyrjX+QvKybXBGj5Kj7boHa2JD26Wlwz+KTic8K51ksCm x9wSzTyyAmlqz3C5vjauXIds5DckQVPq8vLVB1pE17UFnxh88znbmWH2B9MWuVDc6kth Yg+Y76Ip6zUdH5ljR2ZN6BRfd9MbuqPKocdSeJJZQO1Ja8kqYgwvXm3eWoFfosSD+Id+ 6VeZilAQk5zuZ6L14L4cEO3Qqi8ATuc7uQUrW+1o5rngllSDX9tjsWSMKuoyjdJVWibo POkw== X-Received: by 10.66.253.33 with SMTP id zx1mr5645800pac.28.1390448422028; Wed, 22 Jan 2014 19:40:22 -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 sq7sm30312955pbc.19.2014.01.22.19.40.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 19:40:21 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: kldload vmm partial lockup From: Joe Maloney In-Reply-To: Date: Wed, 22 Jan 2014 21:40:16 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <22E3745A-7020-47D7-B4BF-A0FA0232FA6A@gmail.com> References: <9C504625-F183-455E-A0FD-F9A5EC5FA944@gmail.com> <52A1E4D3-9625-40B7-AF4A-2EAFBF3A7025@gmail.com> To: Neel Natu X-Mailer: Apple Mail (2.1827) 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: Thu, 23 Jan 2014 03:40:22 -0000 Hey Neel, I compiled 11-CURRENT and it works now I can kldload vmm with no = problems. Thanks. Joe Maloney On Jan 21, 2014, at 9:01 PM, Neel Natu wrote: > Hi Joe, >=20 > On Tue, Jan 21, 2014 at 6:53 PM, Joe Maloney wrote: >> 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. >>=20 >=20 > No worries. >=20 > I committed the patch as r260972: > http://svnweb.freebsd.org/base?view=3Drevision&revision=3D260972 >=20 > Could you get the latest HEAD and see how it works for you? >=20 > best > Neel >=20 > p.s. not sure why the patch is not compiling - perhaps ppt.h did not > get patched properly? >=20 >> Joe Maloney >>=20 >> /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 >>=20 >> Stop. >> make[4]: stopped in /usr/src/sys/modules/vmm >> *** Error code 1 >>=20 >> Stop. >> make[3]: stopped in /usr/src/sys/modules >> *** Error code 1 >>=20 >> Stop. >> make[2]: stopped in /usr/obj/usr/src/sys/GENERIC >> *** Error code 1 >>=20 >> Stop. >> make[1]: stopped in /usr/src >> *** Error code 1 >>=20 >> Stop. >> make: stopped in /usr/src >> root@jmhome-pc:/usr/src # >>=20 >> On Jan 19, 2014, at 8:43 PM, Neel Natu wrote: >>=20 >> Hi Joe, >>=20 >> On Sun, Jan 19, 2014 at 2:21 PM, Joe Maloney = wrote: >>=20 >> 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" >>=20 >>=20