From owner-freebsd-xen@FreeBSD.ORG Wed May 13 10:35:12 2015 Return-Path: Delivered-To: freebsd-xen@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 ECD24A47 for ; Wed, 13 May 2015 10:35:11 +0000 (UTC) Received: from forward8l.mail.yandex.net (forward8l.mail.yandex.net [IPv6:2a02:6b8:0:1819::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2DF211C0 for ; Wed, 13 May 2015 10:35:11 +0000 (UTC) Received: from smtp3m.mail.yandex.net (smtp3m.mail.yandex.net [77.88.61.130]) by forward8l.mail.yandex.net (Yandex) with ESMTP id BF9DA1A41701; Wed, 13 May 2015 13:35:06 +0300 (MSK) Received: from smtp3m.mail.yandex.net (localhost [127.0.0.1]) by smtp3m.mail.yandex.net (Yandex) with ESMTP id 50E0A27A0452; Wed, 13 May 2015 13:35:06 +0300 (MSK) Received: from unknown (unknown [77.66.213.135]) by smtp3m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 2VDb83inll-Z5pqp84c; Wed, 13 May 2015 13:35:05 +0300 (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1431513305; bh=6S28iMa8dOsb4uJxMYXI/7PtZU6WIh2yI3bYNhpEkFY=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=DhyI624piFND2vcDYMMxAO8jwxqWZmMIomOiUFdZF9aQnORVfIozn+5JWe/ymeqqC PCiww/0D8E2fFRyikRWHik1lSvuFgx6MvqUEkliDPd6uFFQfKzVO91a45sltsFy5yG 0FxhfTvG6ATpRKLR3dAkuGeY9bXabvvwY47IA4/Q= Authentication-Results: smtp3m.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <555328B6.7070709@yandex.ru> Date: Wed, 13 May 2015 13:34:30 +0300 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= , 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> In-Reply-To: <5553107C.4070505@citrix.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 10:35:12 -0000 Roger Pau Monné wrote on 05/13/15 11:51: > 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. 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. 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? 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 Full log: http://dpaste.com/0499WH8 -- Regards, Ruslan T.O.S. Of Reality