From owner-freebsd-current@FreeBSD.ORG Thu Apr 9 21:00:12 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 01C3C426 for ; Thu, 9 Apr 2015 21:00:11 +0000 (UTC) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5E6EAAF for ; Thu, 9 Apr 2015 21:00:11 +0000 (UTC) Received: by iebrs15 with SMTP id rs15so2407352ieb.3 for ; Thu, 09 Apr 2015 14:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=7drRnI7EEokD1QSWWhlHbNVqe9HNlLuFtijbjpEQW5c=; b=cFWyqCyha9+W+zG2WaGcedeuQrcORBb4RrfHI/GHUdGVtpK0wT8sEgBQEQEhSL293d xhL1+tggO7CVPtHmvVXZ3FincTAB91UTLNE8W+o3myC7Kf3X5Lc9nlsIQS9b/j1w+M48 6Uo0regx0wJPXUXuyNKMwVfdVOB23cDHm0yXRdLDpR7l8Kt964lI+LfllBOP3eI42A+b qPTFJAxLlFABvCce7DbUgTtv+hsNkHlGS29HPhGmXljR7TzCLTWcjXVtkajmbltnyH5F qUWVhcrGjuN7wDhw6OAwbsGffeNGZp7NRIV0oFVt+zh1a5dJ2C11Y4XUI26vy5+kjKln T86Q== MIME-Version: 1.0 X-Received: by 10.42.23.17 with SMTP id q17mr25855337icb.4.1428613211197; Thu, 09 Apr 2015 14:00:11 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.86 with HTTP; Thu, 9 Apr 2015 14:00:11 -0700 (PDT) In-Reply-To: <20150409105026.GH8220@zxy.spb.ru> References: <552635A5.5070707@entel.upc.edu> <20150409082128.GF2390@kib.kiev.ua> <5526381A.3010909@entel.upc.edu> <20150409083512.GG2390@kib.kiev.ua> <20150409085233.GD1394@zxy.spb.ru> <20150409100335.GJ2390@kib.kiev.ua> <20150409105026.GH8220@zxy.spb.ru> Date: Thu, 9 Apr 2015 14:00:11 -0700 X-Google-Sender-Auth: Y_3buXg0KHZvmwqK1aWe6W072qM Message-ID: Subject: Re: No IOMMU/DMAR with DELL 3020 From: Kevin Oberman To: Slawa Olhovchenkov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Konstantin Belousov , Gustau P?rez , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 21:00:12 -0000 On Thu, Apr 9, 2015 at 3:50 AM, Slawa Olhovchenkov wrote: > On Thu, Apr 09, 2015 at 01:03:35PM +0300, Konstantin Belousov wrote: > > > On Thu, Apr 09, 2015 at 11:52:33AM +0300, Slawa Olhovchenkov wrote: > > > On Thu, Apr 09, 2015 at 11:35:12AM +0300, Konstantin Belousov wrote: > > > > > > > On Thu, Apr 09, 2015 at 10:28:10AM +0200, Gustau P?rez wrote: > > > > > Yup, sorry for the error. I checked the micro in the ark and it > has vt-d: > > > > > > > > > > http://goo.gl/CZZRHz > > > > It only indicates that the CPU/northbridge has the hardware, but > BIOS must > > > > do a work to configure it and to inform the OS about the > configuration. > > > > Your BIOS did not. > > > > > > > > > > > > > > in the bios, there's only one option to enable virtualization > > > > > support, which is ticked. > > > > > > > > > > The complete log is here: > > > > > > > > > > http://dpaste.com/28FDMJQ > > > > > > > > > Dmesg would not give you any useful information there. A DMAR table > > > > is either present, or is it not. In the later case, OS cannot use the > > > > hardware, and if no option in BIOS is present, your only choice is to > > > > complain to the machine/BIOS vendor. > > > > > > May be some OS utilites can do same work? > > > This is theoretically capable? > > > > No, OS must know the peculiarities of the particular chipset. But also, > > Someone may be know this and wrote support in utility. > May be chipset datashit available. > I am don't talk about 'universal, out of box support in OS'. > I am talk about theoretically utility, that perform some operations > after OS load. > > Also, I am interesting by OS-control interleaving memory (in > multi-socket configuration). > This is totaly imposible or just very complex? > I have a system where it is enabled via some BIOS setting that does not make it remotely obvious what it enables VT-d. I've had to ind it three times, once when the system was new, once when I had to send it in for warranty repair and they reset BIOS, and again when the CMOS battery had to be replaced. Every time it took me a while to figure out the magic, but it was there. (No, mine was not a Dell. It was a ZT systems.) -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com