From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 08:27:58 2014 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 4FBD42FC for ; Tue, 9 Dec 2014 08:27:58 +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 80B68F21 for ; Tue, 9 Dec 2014 08:27:56 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.07,543,1413244800"; d="scan'208";a="202180134" Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.3.210.2; Tue, 9 Dec 2014 03:27:52 -0500 Message-ID: <5486B287.7070302@citrix.com> Date: Tue, 9 Dec 2014 09:27:51 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "David P. Discher" Subject: Re: Attempting to Get Xen FreeBSD Dom0 working References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> <547F6AC1.9060709@citrix.com> <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com> <54801F77.5050700@citrix.com> <54819D6A.4050603@citrix.com> <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> In-Reply-To: <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 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: Tue, 09 Dec 2014 08:27:58 -0000 Hello, El 08/12/14 a les 23.45, David P. Discher ha escrit: > > Sent SIGTERM to all processes │ > Sent SIGKILL to all processes───────────────────────────────────────────────┘ > Requesting system reboot > [ 1157.299205] Restarting system. > root@borg:/zdata/debian # > root@borg:/zdata/debian # > root@borg:/zdata/debian # xl create -c debian.cfg > root@borg:/zdata/debian # xl destroy debian > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > libxl: error: libxl.c:658:libxl_list_domain: getting domain info list: Resource temporarily unavailable > debian is an invalid domain identifier (rc=-5) > root@borg:/zdata/debian # > > I’m running AHCI with MSI off in the FreeBSD kernel, and so far, so good on that front. The great thing is now I got the Xen console working, so can get the debug output. However the bounce buffer/hypercall issue i would think is far more important than MSI interrupts at the monument. Glad to know you got it working at the end! I've already pointed this out in my last email, but did you try to increase vm.max_wired even further? This usually happens when mlock in freebsd_privcmd_alloc_hypercall_buffer (xc_freebsd_osdep.c) fails to wire down the memory that would be used by the hypercalls. Roger.