From owner-freebsd-xen@FreeBSD.ORG  Thu Jan 20 05:08:02 2011
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1A56B106564A
	for <freebsd-xen@freebsd.org>; Thu, 20 Jan 2011 05:08:02 +0000 (UTC)
	(envelope-from snabb@epipe.com)
Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2])
	by mx1.freebsd.org (Postfix) with ESMTP id D33348FC08
	for <freebsd-xen@freebsd.org>; Thu, 20 Jan 2011 05:08:01 +0000 (UTC)
Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2])
	by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0K57vmK092959
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 20 Jan 2011 05:07:57 GMT (envelope-from snabb@epipe.com)
X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0K57vmK092959
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default;
	t=1295500078; x=1296104878;
	bh=vpSPxx9k4+RFh7RLAiVsk5WRDODXmFYmjq0kW0q+6Us=;
	h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:
	MIME-Version:Content-Type;
	b=YN30JKWMmp7WNPlMULC0dO7fR/Syb5MZbr4iOsKujMvrBsfk4g68IzB/WVC4Vffwk
	Xq53r3saIGWW37s3GY6M4arhCK0uB90nmRqDyymPwLSUhwBFJXnGC3DV+QTVPanAFn
	0wKXsV3LPEY9sA+hNhjjW+dTQ2gbXXwHKVUYwq5Q=
Date: Thu, 20 Jan 2011 05:07:57 +0000 (UTC)
From: Janne Snabb <snabb@epipe.com>
To: Martin Cracauer <cracauer@cons.org>
In-Reply-To: <alpine.BSF.2.00.1101192327140.20212@tiktik.epipe.com>
Message-ID: <alpine.BSF.2.00.1101200450270.20212@tiktik.epipe.com>
References: <20110119204707.GA50536@cons.org>
	<alpine.BSF.2.00.1101192327140.20212@tiktik.epipe.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6
	(tiktik.epipe.com [IPv6:2001:1828:0:3::2]);
	Thu, 20 Jan 2011 05:07:58 +0000 (UTC)
Cc: freebsd-xen@freebsd.org
Subject: Re: FreeBSD-amd64 in Xen 4.0?
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.5
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/listinfo/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: Thu, 20 Jan 2011 05:08:02 -0000

On Thu, 20 Jan 2011, Janne Snabb wrote:

> I am not sure if this is the cause of your problem though, but your
> configuration might create an environment which is not suitable for
> the HVM kernel to run.

Martin,

I tried this out with Xen 4.0.1 and had the same effect as you:
"Xend died due to signal 11!" if I attempted loading the XENHVM
kernel with kernel = "/within/dom0/path/to/freebsd/kernel" in xen
config.

With kernel = "/path/to/hvmloader" things work fine (the FreeBSD
kernel and boot loader residing within the virtual disk of the
virtual machine, the same way as it would be on a physical machine).
This is the proper way to use the amd64 XENHVM kernel.

Best Regards,
--
Janne Snabb / EPIPE Communications
snabb@epipe.com - http://epipe.com/