From owner-freebsd-xen@FreeBSD.ORG  Wed May 13 10:44:22 2015
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@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 ACF95F7A
 for <freebsd-xen@freebsd.org>; Wed, 13 May 2015 10:44:22 +0000 (UTC)
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 "Cybertrust Public SureServer SV CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 606EE12EF
 for <freebsd-xen@freebsd.org>; Wed, 13 May 2015 10:44:21 +0000 (UTC)
X-IronPort-AV: E=Sophos;i="5.13,420,1427760000"; d="scan'208";a="264577902"
Message-ID: <55532B00.1000509@citrix.com>
Date: Wed, 13 May 2015 12:44:16 +0200
From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ruslan Makhmatkhanov <cvs-src@yandex.ru>, <freebsd-xen@freebsd.org>
Subject: Re: [solved] iommu must be enabled for PVH hardware domain
References: <55521A29.9080409@yandex.ru> <5552212D.8090308@citrix.com>
 <55530582.2070008@yandex.ru> <555307DA.2060303@citrix.com>
 <55530F6B.5090604@yandex.ru> <5553107C.4070505@citrix.com>
 <555328B6.7070709@yandex.ru>
In-Reply-To: <555328B6.7070709@yandex.ru>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-DLP: MIA1
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: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 10:44:22 -0000

El 13/05/15 a les 12.34, Ruslan Makhmatkhanov ha escrit:
> My bad. `ulimit -l unlimited` doesn't worked for me, but changing the
> limit via /etc/login.conf did. Now it works flawlessly. Thank you!
> Is there any resource where these cases covered ("Cannot allocate
> memory" and disabling IOMMU because of erratas)? Just want to know
> bloody details.

I don't thinks there's any generic resource about this issues, your best
bet is to google for them, this is for example the patch related to that
hw errata:

http://lists.xen.org/archives/html/xen-devel/2013-01/msg01016.html

It contains a link to the Intel SDM that has more info about the erratas.

> And one more question, am I right that PV-guests are no more supported
> in FreeBSD? We tried to run Debian guest in PV mode like described here:
> http://wiki.xen.org/wiki/FreeBSD_Dom0#Creating_your_first_PV_guest
> 
> but guest's kernel panicking like that:
> 
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> Full log: http://dpaste.com/2GZTJMH
> Or it's some bad zfs setup on dom0 system?

Can you paste the DomU configuration file (debian.cfg)?

> This is FreeBSD HVM attempt:
> libxl: error: libxl_dm.c:1482:device_model_spawn_outcome: domain 5
> device model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1319:domcreate_devmodel_started: device
> model did not start: -3
> libxl: error: libxl_dm.c:1586:kill_device_model: Device Model already
> exited

Can you run the same command with xl -vvv instead (it will print more
verbose debug info)? Also, can you paste the contents of
/var/log/xen/qemu-dm-freebsd.log?

Roger.