From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 30 23:17:44 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48B47892; Sun, 30 Nov 2014 23:17:44 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D40C7F2; Sun, 30 Nov 2014 23:17:43 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MQvDO-1XTDJb29Hy-00UIkm; Mon, 01 Dec 2014 00:17:41 +0100 Message-ID: <547BA58B.9050204@gmx.com> Date: Mon, 01 Dec 2014 00:17:31 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Neel Natu Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com> <547A1454.2030901@gmx.com> <547B39A8.5040106@gmx.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:SefSw2+Q/tvDHP4YcFb94GYwePeUKHjd+DR09yrAdsuTzaQVgSS z4hgVVMlLdf/W/duGyEFYkvZQjrNH4av8pZnlpMEKzewL3z0LNXFTDEftkbdChDcIVt4qbw KoAef63etLsHHXpiCg0Gaz4mdjXqZSavvZtvNtMuXaEx1L65SNHWhmB3rQ0avbIlE+qcjEw HTCeM2XEeO8tmMf+bUpTQ== X-UI-Out-Filterresults: notjunk:1; Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sun, 30 Nov 2014 23:17:44 -0000 On 11/30/14 20:42, Neel Natu wrote: >>> this CPU does not support VT-d, which is needed for PCI passthru. >> >> >> Indeed. Good catch, Neel should this be the case? > > Definitely! > > vmm.ko should probably not even attach the ppt driver to "pptdevs" if > an IOMMU is absent. OK, the mystery is solved then. Thank you all for your answers PS: I just started using bhyve and it's amazing to say the least! Amazing work people!