WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] ### Problem with Xen4 on Debian as FreeBSD DomU ###

To: chrupol <gregor@xxxxxx>
Subject: Re: [Xen-users] ### Problem with Xen4 on Debian as FreeBSD DomU ###
From: Florian Heigl <florian.heigl@xxxxxxxxx>
Date: Mon, 14 Nov 2011 22:52:14 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 14 Nov 2011 14:02:38 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fV9622EEM9OiwPTOQniNtUdoT/634+pA/TjkidsAUow=; b=pt61iHRzBe1mkpw5th9qgJfH1UI7lVgTA0BezJlYc5dMeP/cZ37D3+mAz2KDcjrcj/ ZproPTjftuZZhCjjLV5OT7aE9+mUSnGjunyHgtUutGiEkCw+EDaNmlSDUoPXdQktHsNs gbrdk3CuTXpKK/Bdg4V5a+Cj412lZcEl0s02U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAFivhPn=Y4SNEuLgdMSPpBikR4gWOnPSFSJQ1dnRjypWhgRGqw@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1321089488849-4986590.post@xxxxxxxxxxxxx> <CAFivhPn=Y4SNEuLgdMSPpBikR4gWOnPSFSJQ1dnRjypWhgRGqw@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I just had to grab the wrong kernel config, didn't I?

This is the amd64 config, much shorter.

Include         GENERIC
ident           XENHVM

makeoptions     MODULES_OVERRIDE=""

device          pf
device          pflog
device          pfsync


#
# Adaptive locks rely on a lock-free pointer read to determine the run state
# of the thread holding a lock when under contention; under a virtualisation
# system, the thread run state may not accurately reflect whether the thread
# (or rather its host VCPU) is actually executing.  As such, disable this
# optimisation.
#
options         NO_ADAPTIVE_MUTEXES
options         NO_ADAPTIVE_RWLOCKS

# Xen HVM support
options         XENHVM
device          xenpci


Sorry :)
Florian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>