From owner-freebsd-xen@freebsd.org  Mon Feb 22 10:12:51 2016
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 547EBAAF587
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon, 22 Feb 2016 10:12:51 +0000 (UTC)
 (envelope-from prvs=853c61c85=roger.pau@citrix.com)
Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0DE13110E
 for <freebsd-xen@freebsd.org>; Mon, 22 Feb 2016 10:12:50 +0000 (UTC)
 (envelope-from prvs=853c61c85=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.22,483,1449532800"; d="scan'208";a="339889711"
Subject: Re: Porting the block-iscsi hotplug script
To: =?UTF-8?Q?Gustau_P=c3=a9rez?= <gustau.perez@gmail.com>,
 =?UTF-8?Q?Gustau_P=c3=a9rez?= <gperez@entel.upc.edu>, FreeBSD XEN
 <freebsd-xen@freebsd.org>
References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu>
 <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com>
 <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com>
 <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com>
 <555EF542.3090002@citrix.com> <555F9B3F.1000600@entel.upc.edu>
 <55602512.1090702@citrix.com> <56C6FA2F.8040900@gmail.com>
 <56CAC8CB.8030107@gmail.com>
From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
Message-ID: <56CADEDA.4050007@citrix.com>
Date: Mon, 22 Feb 2016 11:11:38 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56CAC8CB.8030107@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-DLP: MIA2
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 10:12:51 -0000

El 22/2/16 a les 9:37, Gustau Pérez ha escrit:
> 
> 
> El 19/02/16 a les 12:19, Gustau Pérez ha escrit:
>>    I'm retaking this issue. I have an spare dual Xeon Intel(R) Xeon(R)
>> CPU E5-2420 box I can use for this. It currently uses 10.2-prerealse (as
>> of july 2015 more or less) but I can update it to head if necessary.
> 
>    Hi,
> 
>    Sorry, the box has two E5620 CPUs. I've checked in the ark and they
> support vt-d, but the xen kernel complains about the iommu (that is,
> vt-d support). Apparently iommu is there (acpidump -t | grep DMAR shows
> something). I tried booting forcing iommu [1] but no joy.

It might be that the IOMMU has an errata and Xen refuses to enable it.
Can you provide the serial output when you try to boot Xen + FreeBSD?
You might have to add console="com1,vga" to your xen_cmdline (although
AFAIK that's the default).

The command line looks fine IMHO.

>    On the other hand I'm still not sure whether the hotplug patches
> still need to be applied or not, I've checked them and I'd say that both
> the kernel and xen-tools need to be patched, am I right?

Yes, both series need to be applied. If you find issues applying them
ping me and I can rebase them if needed.

Roger.