From owner-freebsd-xen@FreeBSD.ORG Wed May 13 08:51:19 2015 Return-Path: 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 232E0736 for ; Wed, 13 May 2015 08:51:19 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (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 CBE8E1389 for ; Wed, 13 May 2015 08:51:18 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,420,1427760000"; d="scan'208";a="262165195" Message-ID: <5553107C.4070505@citrix.com> Date: Wed, 13 May 2015 10:51:08 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= 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 , Subject: Re: 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> In-Reply-To: <55530F6B.5090604@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2015 08:51:19 -0000 Hello, El 13/05/15 a les 10.46, Ruslan Makhmatkhanov ha escrit: > Yes, the system is now booted successfully! But `xl list` doesn't work > with: > > root@:~ # xl list > libxl: error: libxl.c:669:libxl_list_domain: getting domain info list: > Cannot allocate memory > libxl_list_domain failed. [...] > Shell memory values are unlimited too: > > root@:~ # ulimit -a > cpu time (seconds, -t) unlimited > file size (512-blocks, -f) unlimited > data seg size (kbytes, -d) 33554432 > stack size (kbytes, -s) 524288 > core file size (512-blocks, -c) unlimited > max memory size (kbytes, -m) unlimited > locked memory (kbytes, -l) 64 Shell memory is not unlimited, as the output above shows. `ulimit -l unlimited` should fix that. Roger.