From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 09:53:48 2011 Return-Path: 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 EBDC1106564A for ; Sun, 30 Jan 2011 09:53:48 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD8E8FC13 for ; Sun, 30 Jan 2011 09:53:47 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0U9riOw016230; Sun, 30 Jan 2011 20:53:45 +1100 Message-ID: <4D453528.5000604@joovke.com> Date: Sun, 30 Jan 2011 20:53:44 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: gibbs@FreeBSD.org References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> <4D4350C2.6050806@FreeBSD.org> In-Reply-To: <4D4350C2.6050806@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-xen@FreeBSD.org Subject: Re: xenbusb_nop_confighook_cb timeout 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 09:53:49 -0000 Hi Justin, I am using FreeBSD as the OS on a VPS (Xen HVM). Do you think the VPS provider will provide that information without too much drama? On 29/01/11 10:26, Justin T. Gibbs wrote: > On 1/27/2011 2:29 PM, Alex wrote: >> I've had that geom warning before on real hardware and it's never >> stopped it from working. >> >> In my screenshot, it appears the time out is originating from: >> >> xenbusb.c:xenbusb_nop_confighook_cb > This means that one of the PV devices is not transitioning into either the Connected or Closed > state. Can you provide the output of "xenstore-ls" from your DOM0 to me privately so I can > help you track this down? > > Thanks, > Justin > From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 11:27:10 2011 Return-Path: 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 DD968106566B for ; Sun, 30 Jan 2011 11:27:10 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id 6F30A8FC08 for ; Sun, 30 Jan 2011 11:27:10 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0UBR7GA008299 for ; Sun, 30 Jan 2011 22:27:08 +1100 Message-ID: <4D454B0B.1030208@joovke.com> Date: Sun, 30 Jan 2011 22:27:07 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> In-Reply-To: <4D41E3D1.7040100@joovke.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: xenbusb_nop_confighook_cb timeout 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 11:27:10 -0000 This problem seems to have disappeared, the only thing i have done in the config at my VPS provider was mount a cdrom image.. On 28/01/11 08:29, Alex wrote: > I've had that geom warning before on real hardware and it's never > stopped it from working. > > In my screenshot, it appears the time out is originating from: > > xenbusb.c:xenbusb_nop_confighook_cb > > xenbusb_nop_confighook_cb(void *arg __unused) > { > } > > called in xenbusb_attach(device_t dev, char *bus_node, u_int > id_components) > > /* > * Since XenBus busses are attached to the XenStore, and > * the XenStore does not probe children until after interrupt > * services are available, this config hook is used solely > * to ensure that the remainder of the boot process (e.g. > * mount root) is deferred until child devices are adequately > * probed. We unblock the boot process as soon as the > * connecting child count in our softc goes to 0. > */ > xbs->xbs_attach_ch.ich_func = xenbusb_nop_confighook_cb; > > > Regarding the partitioning, I am not sure what you mean. I have this > configured as a VPS so I want to avoid doing anything that may destroy > data on the disk. > > > > On 28/01/11 06:29, Nick Sayer wrote: >> On Jan 27, 2011, at 1:43 AM, Alex wrote: >> >>> I've applied this patch, I now get past the ethernet issue, and have >>> run into another problem, see screenshot: >>> >>> http://ahhyes.net/xen1.jpg >>> >>> any ideas? >>> >> The disk geometry differs from the PV device and the emulated >> hardware, I suspect. >> >> I was using GPT when I migrated, so I suspect that the issue was >> moot. What is your partitioning schema for this disk? Can you switch >> over to GPT... uh... >> somehow?_______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 11:36:13 2011 Return-Path: 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 2F3BB1065672 for ; Sun, 30 Jan 2011 11:36:13 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.freebsd.org (Postfix) with ESMTP id B5A698FC1A for ; Sun, 30 Jan 2011 11:36:12 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0UBa9BZ022113 for ; Sun, 30 Jan 2011 22:36:10 +1100 Message-ID: <4D454D28.8050106@joovke.com> Date: Sun, 30 Jan 2011 22:36:08 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: terrible performance with xn0 interface and PF 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 11:36:13 -0000 Hi guys, I managed to get the XENHVM kernel working, obviously I had to adjust my pf.conf as the network interface is now xn0 instead of re0. All i did was edit the config, and replace all instances of re0 with xn0. The performance seems to be aweful. I was wondering why network connectivity was so slow. A download test struggled to do 2KB/s. I disabled pf and suddenly the speed skyrocketed. Any ideas where to look? I have the following in my kernel for PF: device pf device pflog device pfsync options ALTQ options ALTQ_CBQ # Class Bases Queuing (CBQ) options ALTQ_RED # Random Early Detection (RED) options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) options ALTQ_PRIQ # Priority Queuing (PRIQ) options ALTQ_NOPCC # Required for SMP build and pf.conf (very basic setup): mailblocklist = "{ 69.6.26.0/24 }" #blacklist = "{ 202.16.0.11 }" # Rule 0 (xn0) #pass in quick on xn0 inet proto icmp from any to (xn0) label "RULE 0 -- ACCEPT " #block mail server(s) that continue to try and send me junk block in quick on xn0 inet proto tcp from $mailblocklist to (xn0) port 25 #block anyone else who's in the blacklist #block in quick on xn0 inet from $blacklist to (xn0) pass in quick on xn0 inet proto tcp from any to (xn0) port { 110, 25, 80, 443, 21, 53 } flags any label "RULE 0 -- ACCEPT " pass in quick on xn0 inet proto udp from any to (xn0) port 53 label "RULE 0 -- ACCEPT " # # Rule 1 (lo0) pass quick on lo0 inet from any to any no state label "RULE 1 -- ACCEPT " # # Rule 2 (xn0) -- allow all outbound connectivity pass out quick on xn0 inet from any to any label "RULE 2 -- ACCEPT " # Rule 3 (xn0) # deny all not matched by above block in quick on xn0 inet from any to any no state label "RULE 3 -- DROP " -------------------------- Any ideas why I would be seeing such a performance hit? The only thing that's changed is the kernel+network interface type. From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 12:56:35 2011 Return-Path: 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 9F315106566B for ; Sun, 30 Jan 2011 12:56:35 +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 681F68FC13 for ; Sun, 30 Jan 2011 12:56:35 +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 p0UCuYqO045336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 30 Jan 2011 12:56:34 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0UCuYqO045336 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296392194; x=1296996994; bh=Fuh14w857fIACwNUzdsYOLrUEev6IVL3zExOdQ/lAGc=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=H/eLcX+qmhyVLXyCcGiG/97eXy+n2u6g6tCh7G9B75tdojrpN7oOCTL/ueCY1JIXu MmIZd5/wHdHj55472K6VorkTgETVVOW6Ucm0ffVQQeAmFC5cVkuPwPXIf16Jl36qe3 7X6ziUIO9hbExmdsAuMCXcH4YFopOnhNyUOM7HMc= Date: Sun, 30 Jan 2011 12:56:34 +0000 (UTC) From: Janne Snabb To: freebsd-xen@freebsd.org Message-ID: 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]); Sun, 30 Jan 2011 12:56:34 +0000 (UTC) Subject: HOWTO: xen tools within FreeBSD domU 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 12:56:35 -0000 I wanted to look at xenstore contents from my domU. domU does not have access to all data but the entries related to the domU instance in question are available. I am posting this in case it happens to be useful to someone else. It would be easy to make a xenstore-clients or xen-tools-domU port. Here is how to get a working "xenstore-ls" command and other xen tools for your FreeBSD domU: Building & installation ----------------------- Prerequisites: gmake, XENHVM or XEN kernel (GENERIC will not work) 1. ftp http://bits.xensource.com/oss-xen/release/4.0.1/xen-4.0.1.tar.gz 2. tar xvfz xen-4.0.1.tar.gz 3. cd xen-4.0.1/tools 4. gmake -C include 5. cd misc 6. gmake xen-detect 7. install xen-detect /usr/local/bin 8. cd ../xenstore 9. Build client library and programs: gmake clients 10. Install client library and programs: install libxenstore.so.3.0 /usr/local/lib install xenstore xenstore-control /usr/local/bin cd /usr/local/bin ln xenstore xenstore-chmod ln xenstore xenstore-exists ln xenstore xenstore-list ln xenstore xenstore-ls ln xenstore xenstore-read ln xenstore xenstore-rm ln xenstore xenstore-write Usage ----- 1. Set required environment variable: export XENSTORED_PATH=/dev/xen/xenstore (Alternatively you could patch tools/xenstore/xs_lib.c function xs_domain_dev() before compiling.) 2. Now you can do things such as: xen-detect xenstore-ls device xenstore-ls -f /local/domain/0/backend/vif/11/0 xenstore-read name Best Regards, -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 14:16:28 2011 Return-Path: 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 DD5BC106564A for ; Sun, 30 Jan 2011 14:16:28 +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 A3AD48FC0A for ; Sun, 30 Jan 2011 14:16:28 +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 p0UEGR3P053037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 30 Jan 2011 14:16:27 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0UEGR3P053037 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296396987; x=1297001787; bh=erZIxCuJ7K+WTys+PmtH7bjRfkVLYTDEdMxK1pcFvNM=; h=Date:From:To:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=HbQwhNSCcgHaKYZ/W9qX4/YqksoA8tyoGp+FTUGSxTXEmfVWZmKczxgs7dqIvCWOj v8BwfGTh7Uod79mlBivGZ/cRnOHrOqiuXYBuj/3KsNbcmuS8pV1ltJ7lDMVc0qFBTe 2TsqAeaR123RaWUskJkX8bm9IXlhBXbbNKo1EhaU= Date: Sun, 30 Jan 2011 14:16:27 +0000 (UTC) From: Janne Snabb To: freebsd-xen@freebsd.org In-Reply-To: Message-ID: References: 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]); Sun, 30 Jan 2011 14:16:27 +0000 (UTC) Subject: Re: HOWTO: xen tools within FreeBSD domU 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 14:16:28 -0000 On Sun, 30 Jan 2011, Janne Snabb wrote: > Prerequisites: gmake, XENHVM or XEN kernel (GENERIC will not work) Python is also needed. I put a copy of the (updated) document at: http://dist.epipe.com/freebsd/HOWTO-xen-tools.txt -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 17:20:03 2011 Return-Path: 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 60FC7106566B for ; Sun, 30 Jan 2011 17:20:03 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 20DAA8FC0C for ; Sun, 30 Jan 2011 17:20:02 +0000 (UTC) Received: by yie19 with SMTP id 19so1797636yie.13 for ; Sun, 30 Jan 2011 09:20:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.102.165 with SMTP id d25mr10381356yhg.78.1296406136847; Sun, 30 Jan 2011 08:48:56 -0800 (PST) Received: by 10.236.109.166 with HTTP; Sun, 30 Jan 2011 08:48:56 -0800 (PST) In-Reply-To: References: Date: Sun, 30 Jan 2011 16:48:56 +0000 Message-ID: From: David Markey To: Janne Snabb Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@freebsd.org Subject: Re: HOWTO: xen tools within FreeBSD domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com 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: Sun, 30 Jan 2011 17:20:03 -0000 Sweet, from this it should be possible to get XenServer tool to work. Thanks! On 30 January 2011 14:16, Janne Snabb wrote: > On Sun, 30 Jan 2011, Janne Snabb wrote: > > > Prerequisites: gmake, XENHVM or XEN kernel (GENERIC will not work) > > Python is also needed. > > > I put a copy of the (updated) document at: > > http://dist.epipe.com/freebsd/HOWTO-xen-tools.txt > > -- > Janne Snabb / EPIPE Communications > snabb@epipe.com - http://epipe.com/ > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 21:10:39 2011 Return-Path: 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 63FBB10656EC for ; Sun, 30 Jan 2011 21:10:39 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:95a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0C8F68FC14 for ; Sun, 30 Jan 2011 21:10:38 +0000 (UTC) Received: from [192.168.1.108] (ip174-65-96-58.sd.sd.cox.net [174.65.96.58]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0ULAWjs037077 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 30 Jan 2011 13:10:37 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0ULAWjs037077 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296421838; bh=pHB7bc7iWCctNvauYg/kBxivHuCU7ycpBbJHGs3Co/M=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=LkBuUQDUasshPxYZtnVfxO7tl5c1Zck5zeleuGGEQ6eYfTltnJJ2vrD621fKC2Zbp 3LvPuF608j96g1aPboxSrjL3RqlX1ugAFh86AzUuhfHxHp0CFBjSkPLDZu4HPYhCxj ZrzriOImLTPCM27gTeDL71rAnmZkhiOX9lxpABNc= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Nick Sayer In-Reply-To: Date: Sun, 30 Jan 2011 13:10:27 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [204.109.60.138]); Sun, 30 Jan 2011 13:10:38 -0800 (PST) Subject: Re: HOWTO: xen tools within FreeBSD domU 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 21:10:39 -0000 This works exactly as described. I sort of assume that the xen = developers have taken great pains to insure that there are no exploits = through the xenstore to escape from a domU to either a neighbor or the = dom0. Nevertheless, I did open a ticket to my provider to let them know = that I built this tool and to let me know if there was anything to stay = away from. I didn't want them to think I was up to no good. :) That said, an ls on device gives me back the two network interfaces, the = block device, the console, and a vfb device. dmesg shows me PV drivers (xn? xbd?) for the network and disk, but I = still see atkbdc/atkbd, psm and vgapci attaching to the console. Is this = the current state of the art for RELENG_8_2? What's also a little odd is that I see both psm0 and ums0 show up. None of this matters too much to me, because the only use I have for the = console is if things go sour and I need to boot single user or some = such. But I'm a curious sort. On Jan 30, 2011, at 6:16 AM, Janne Snabb wrote: > On Sun, 30 Jan 2011, Janne Snabb wrote: >=20 >> Prerequisites: gmake, XENHVM or XEN kernel (GENERIC will not work) >=20 > Python is also needed. >=20 >=20 > I put a copy of the (updated) document at: >=20 > http://dist.epipe.com/freebsd/HOWTO-xen-tools.txt >=20 > -- > Janne Snabb / EPIPE Communications > snabb@epipe.com - http://epipe.com/ > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 00:00:15 2011 Return-Path: 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 36060106564A for ; Mon, 31 Jan 2011 00:00:15 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:95a::2]) by mx1.freebsd.org (Postfix) with ESMTP id D63858FC0C for ; Mon, 31 Jan 2011 00:00:14 +0000 (UTC) Received: from [192.168.1.108] (ip174-65-96-58.sd.sd.cox.net [174.65.96.58]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0V00AHj039176 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 30 Jan 2011 16:00:14 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0V00AHj039176 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296432014; bh=xRoYRM98Ko66lD+6A5b5/X9Ji/fZPATCIU528WdhlPU=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=RblQWhsywGF/dGbMVcyxY4Il22xK696MBM4Gm1Q8h0GA/9JC2KG0FywSobaWRVpGZ gHohFuPb9Z5HQmeSEc7O7fd0CBRBfq4HgkXc3uJ0Vmi5GekG7GB60isOvIATPxkha6 ovknLbEA+SswwtJkMcaG6SUouACnBA4LbJwOTLYE= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Nick Sayer In-Reply-To: Date: Sun, 30 Jan 2011 16:00:05 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <034C454F-CE2B-4310-BD09-2A9989E544E9@kfu.com> References: To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [204.109.60.138]); Sun, 30 Jan 2011 16:00:14 -0800 (PST) Subject: Re: HOWTO: xen tools within FreeBSD domU 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 00:00:15 -0000 The web page previously referenced says in part: > Usage > ----- >=20 > Set required environment variable: >=20 > export XENSTORED_PATH=3D/dev/xen/xenstore >=20 > (Alternatively you could patch tools/xenstore/xs_lib.c function > xs_domain_dev() before compiling.) >=20 >=20 A patch to do this is: --- xs_lib.c.orig 2011-01-30 15:56:52.985324929 -0800 +++ xs_lib.c 2011-01-30 15:55:14.024346135 -0800 @@ -84,6 +84,8 @@ return "/proc/xen/xenbus"; #elif defined(__NetBSD__) return "/kern/xen/xenbus"; +#elif defined(__FreeBSD__) + return "/dev/xen/xenstore"; #else return "/dev/xen/xenbus"; #endif If no one else is working on it, I might take a cut at a xen-domU-tools = port that does what that page lists. From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 01:09:25 2011 Return-Path: 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 194FA106566C for ; Mon, 31 Jan 2011 01:09:25 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id D01978FC14 for ; Mon, 31 Jan 2011 01:09:24 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.4/8.14.4) with ESMTP id p0V19BVt039325; Mon, 31 Jan 2011 02:09:11 +0100 (CET) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.4/8.14.4/Submit) id p0V19ACP039324; Sun, 30 Jan 2011 20:09:10 -0500 (EST) (envelope-from cracauer) Date: Sun, 30 Jan 2011 20:09:10 -0500 From: Martin Cracauer To: Janne Snabb Message-ID: <20110131010910.GA34878@cons.org> References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-xen@freebsd.org Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 01:09:25 -0000 Janne Snabb wrote on Wed, Jan 26, 2011 at 09:05:49AM +0000: > On Fri, 21 Jan 2011, Nick Sayer wrote: > > > +1 to the patch Janne Snabb posted. I have a domU at rootbsd and > > had suffered the exact same "do something smart" panic when I tried > > to build a xen kernel, but his patch fixed it for me. > > Thanks for confirming that I am not the only one suffering of this. > I was wondering if I am doing something wrong. > > I did send-pr this with my patch so that it does not get forgotten. > PR kern/154302 I can confirm that I had the same smart error and it went away with the patch. amd64/-current/hvm/pxe Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 02:47:27 2011 Return-Path: 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 D1095106566B for ; Mon, 31 Jan 2011 02:47:27 +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 953C28FC0A for ; Mon, 31 Jan 2011 02:47:27 +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 p0V2lPUL019194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 02:47:25 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0V2lPUL019194 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296442045; x=1297046845; bh=2xf6JY9W/7TizmKA7i5grrMTwTm8lQ4ZvMDif/aquzQ=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=Fou1SSiMERriSv0APmCc2SAQF3C1uEwZoFb77shAMsYot23WywXH3fP5LR75N60Kp 6vAc1Wi6jfcaV41gU36IGPe3jNQ3fDsaK8dCVyYtEafjrS7gGeYQwzdRxlZ6MQ+z1m d9OOd26/eKA5uncu2JC+rIR/2hmSmlR9YakfwCDs= Date: Mon, 31 Jan 2011 02:47:25 +0000 (UTC) From: Janne Snabb To: Nick Sayer In-Reply-To: <034C454F-CE2B-4310-BD09-2A9989E544E9@kfu.com> Message-ID: References: <034C454F-CE2B-4310-BD09-2A9989E544E9@kfu.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]); Mon, 31 Jan 2011 02:47:25 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: HOWTO: xen tools within FreeBSD domU 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 02:47:27 -0000 On Sun, 30 Jan 2011, Nick Sayer wrote: > If no one else is working on it, I might take a cut at a > xen-domU-tools port that does what that page lists. I say give it a shot. It would be useful. Send me a message if you wish me to check/review the port before you send-pr it. In addition to patching the xenstore device name, I suppose that the shared library version numbering should be changed to match what it says in the Porters Handbook[1]: > Try to keep shared library version numbers in the libfoo.so.0 format. > Our runtime linker only cares for the major (first) number. This probably requires patching tools/xenstore/Makefile. [1]: http://www.freebsd.org/doc/en/books/porters-handbook/special.html#PORTING-SHLIBS -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 03:20:56 2011 Return-Path: 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 C7294106566B for ; Mon, 31 Jan 2011 03:20:56 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by mx1.freebsd.org (Postfix) with ESMTP id 8CD8E8FC0A for ; Mon, 31 Jan 2011 03:20:56 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [IPv6:2001:470:1f0b:105e::1e6]) by koef.zs64.net (8.14.4/8.14.4) with ESMTP id p0V3KtsP091991 for ; Mon, 31 Jan 2011 04:20:55 +0100 (CET) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.4/8.14.4/Submit) id p0V3Ksec091990 for freebsd-xen@freebsd.org; Sun, 30 Jan 2011 22:20:54 -0500 (EST) (envelope-from cracauer) Date: Sun, 30 Jan 2011 22:20:54 -0500 From: Martin Cracauer To: freebsd-xen@freebsd.org Message-ID: <20110131032054.GA87099@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: What's a working BIOS/client-side PXE for Xen/HVM? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 03:20:56 -0000 What do you guys use to bring up HVM installes inside Xen with PXE? I am tangling with iPXE but it screws up parsing the filename and root-path options into service/host/filename parts. After fixing that for the NFS-mount case I get http://wavehh.dyndns.org/tmp/debug-xen/nfs.gif which is generally a hard to debug "broken PXE" problem. Using FreeBSD's pxeboot compiled with tftp instead of NFS I get further but root-path is still ignored. Manually placing all things into default places not requiring root-path I get http://wavehh.dyndns.org/tmp/debug-xen/nfs-error.gif "nfs_diskless: no NFS handle" According to the source code this means it doesn't have an NFS handle, specifically boot.nfsroot.nfshandle I have seen a few people post questions like this to questions@ but no answer. I assume this is a chicken-and-egg problem with not having a root-path at start of the kernel, and this message is printed before attempting to mount what I specified as root device in loader.conf. I think it's better for me to look for a working PXE so that I can use a regular NFS pxeboot, hence the question - anyone got anything working? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 03:35:08 2011 Return-Path: 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 7A18B1065673 for ; Mon, 31 Jan 2011 03:35:08 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:95a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3FFE58FC08 for ; Mon, 31 Jan 2011 03:35:08 +0000 (UTC) Received: from [10.66.67.1] (166-205-136-019.mobile.mymmode.com [166.205.136.19] (may be forged)) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0V3Yo2T041661 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 30 Jan 2011 19:35:07 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0V3Yo2T041661 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296444907; bh=7stxj8hP8ep2kN7Eup3ss0EIJgMJKV8R+PDiN5y9WDg=; h=Subject:From:Content-Type:Message-Id:Date:To: Content-Transfer-Encoding:Mime-Version; b=jzFwP9cO9nNGDil8zB8C9Fhc9uR2fTwMg+rV/dA0HadTPVT8tQJXJtrcoKmrpRd/P OrNYFV6ezoLKefRn+1fzEa/DAeKa3WyK5nDqHqnugYod/YfuDXIgBJhVxiRfckOvvO RCup8/vLSSRp+5naZ4H6YxFHyCBPZQk4NF14PB0s= From: Nick Sayer Content-Type: text/plain; charset=us-ascii Message-Id: <4E0B035D-659D-4724-B494-C1EF73EDEC17@kfu.com> Date: Sun, 30 Jan 2011 18:44:09 -0800 To: "freebsd-xen@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8F5153d) X-Mailer: iPhone Mail (8F5153d) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [204.109.60.138]); Sun, 30 Jan 2011 19:35:07 -0800 (PST) Subject: XENHVM amd64 mouse issue 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 03:35:08 -0000 I have 8.2-RC2 + the netfront patch and a XENHVM kernel. I note that I wind u= p with both ums0 and psm0, but it turns out neither appears to work. My VNC c= onsole works for text video and keyboard, but trying to run a moused for eit= her device doesn't result in the text console mouse pointer moving. Mouse cl= icks do appear to do something, however. I don't ever see the psm device sho= w up in the vmstat -i output, FWIW.=20 Has anyone else seen anything similar? I hope it's not that I've forgotten some elementary moused configuration ste= p. :/= From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 11:07:14 2011 Return-Path: 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 D56DE10656A7 for ; Mon, 31 Jan 2011 11:07:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C4B6B8FC12 for ; Mon, 31 Jan 2011 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0VB7Eov091962 for ; Mon, 31 Jan 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0VB7EdL091960 for freebsd-xen@FreeBSD.org; Mon, 31 Jan 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 31 Jan 2011 11:07:14 GMT Message-Id: <201101311107.p0VB7EdL091960@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 11:07:14 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 18 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 12:57:27 2011 Return-Path: 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 43C52106566C for ; Mon, 31 Jan 2011 12:57:27 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from worf.ds9.tecnik93.com (worf.ds9.tecnik93.com [81.196.207.130]) by mx1.freebsd.org (Postfix) with ESMTP id ED8118FC17 for ; Mon, 31 Jan 2011 12:57:26 +0000 (UTC) Received: from it.buh.tecnik93.com (unknown [188.27.99.221]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by worf.ds9.tecnik93.com (Postfix) with ESMTPSA id BC33422C5505; Mon, 31 Jan 2011 14:39:16 +0200 (EET) Date: Mon, 31 Jan 2011 14:39:07 +0200 From: Ion-Mihai Tetcu To: Janne Snabb Message-ID: <20110131143907.08e8402d@it.buh.tecnik93.com> In-Reply-To: References: <034C454F-CE2B-4310-BD09-2A9989E544E9@kfu.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/5rkW/O0FaKjUUpTeNB_1zMm"; protocol="application/pgp-signature" Cc: freebsd-xen@freebsd.org Subject: Re: HOWTO: xen tools within FreeBSD domU 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 12:57:27 -0000 --Sig_/5rkW/O0FaKjUUpTeNB_1zMm Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 31 Jan 2011 02:47:25 +0000 (UTC) Janne Snabb wrote: > On Sun, 30 Jan 2011, Nick Sayer wrote: >=20 > > If no one else is working on it, I might take a cut at a > > xen-domU-tools port that does what that page lists. >=20 > I say give it a shot. It would be useful. Send me a message if you > wish me to check/review the port before you send-pr it. >=20 > In addition to patching the xenstore device name, I suppose that > the shared library version numbering should be changed to match > what it says in the Porters Handbook[1]: >=20 > > Try to keep shared library version numbers in the libfoo.so.0 > > format. Our runtime linker only cares for the major (first) number. >=20 > This probably requires patching tools/xenstore/Makefile. >=20 > [1]: > http://www.freebsd.org/doc/en/books/porters-handbook/special.html#PORTING= -SHLIBS Ping/CC me if you have any questions on the ports side. --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B --Sig_/5rkW/O0FaKjUUpTeNB_1zMm Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk1GrXMACgkQJ7GIuiH/oeVghQCfS790pWeuU76Ue8qsuarhQf1X o+4An2rwlJidLKK3O3+IR1PM4jdzLOvy =rSS4 -----END PGP SIGNATURE----- --Sig_/5rkW/O0FaKjUUpTeNB_1zMm-- From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 15:45:52 2011 Return-Path: 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 688A0106564A for ; Mon, 31 Jan 2011 15:45:52 +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 2DE3B8FC13 for ; Mon, 31 Jan 2011 15:45:52 +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 p0VFjprv083608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 15:45:51 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0VFjprv083608 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296488751; x=1297093551; bh=7dyvR1aYHtpGhuxIxNodHh10NCmxmrP5I5wr2IuNZfk=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=Dys1yaMPqU0TjvX5fyF1w4MUvUYCbHElCeZaBQZW1aZ6n90vkkr3FgF1Oe2Jr2EsC me5PyJfvPCdo0S/iOTo085idzrttjhwwDyu0Wj/fX+Wt+1Rt5cSmzfU812nzSQSrHY gs1GFRekIwmW9UjlZkA8wuoJK5lcj5I8I0hlCVCo= Date: Mon, 31 Jan 2011 15:45:51 +0000 (UTC) From: Janne Snabb To: Nick Sayer In-Reply-To: <4E0B035D-659D-4724-B494-C1EF73EDEC17@kfu.com> Message-ID: References: <4E0B035D-659D-4724-B494-C1EF73EDEC17@kfu.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]); Mon, 31 Jan 2011 15:45:51 +0000 (UTC) Cc: "freebsd-xen@freebsd.org" Subject: Re: XENHVM amd64 mouse issue 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 15:45:52 -0000 On Sun, 30 Jan 2011, Nick Sayer wrote: > I have 8.2-RC2 + the netfront patch and a XENHVM kernel. I note > that I wind up with both ums0 and psm0, but it turns out neither > appears to work. My VNC console works for text video and keyboard, > but trying to run a moused for either device doesn't result in the > text console mouse pointer moving. Mouse clicks do appear to do > something, however. I don't ever see the psm device show up in the > vmstat -i output, FWIW. I do not use a mouse much with Xen myself and have not had issues with it when I had to, but in the past people have reported a lot of issues with Xen and broken mouse. The solution for some people seems to be to use a tablet emulation instead of mouse. Google for "xen tablet". I do not know if FreeBSD has the corresponding driver and moused support, but it might be worth checking out. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 23:57:06 2011 Return-Path: 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 462A9106566B for ; Mon, 31 Jan 2011 23:57:06 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id 1BAD18FC21 for ; Mon, 31 Jan 2011 23:57:05 +0000 (UTC) Received: from [192.168.4.138] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.4/8.14.4) with ESMTP id p0VNupVZ075631 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 16:56:52 -0700 (MST) (envelope-from gibbs@FreeBSD.org) Message-ID: <4D474C3F.1010407@FreeBSD.org> Date: Mon, 31 Jan 2011 16:56:47 -0700 From: "Justin T. Gibbs" Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110123 Thunderbird/3.1.8 MIME-Version: 1.0 To: Janne Snabb References: <1295969742.3187.48.camel@pow> In-Reply-To: X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (aslan.scsiguy.com [70.89.174.89]); Mon, 31 Jan 2011 16:56:53 -0700 (MST) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@FreeBSD.org, luke@hybrid-logic.co.uk Subject: Re: I have a problem with iSCSI on AMD64 Xen HVM X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gibbs@FreeBSD.org 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: Mon, 31 Jan 2011 23:57:06 -0000 On 1/25/2011 6:30 PM, Janne Snabb wrote: > > (I wish there was a bit more comments in the non-obvious parts of > the code. Now it is difficult for a FreeBSD/Xen PV newbie to work > on it without intimate knowledge of the history of the odd bits of > the code. It clearly needs more care than what it is being given > now. Things like the "do something useful" panic also indicate that > there is no more than few people who actually play with and try out > the code currently.) Xen use models in our community are quite varried and that is reflected in the relative stability and quality of the different areas of FreeBSD's Xen support. In my day job at SpectraLogic, we rely heavily on FreeBSD's amd64 HVM Xen support, but only for serving block storage. While we've invested heavily in the PV driver framework and the blkback driver (and to a lesser extent blkfront), we haven't done much to netfront since it is not a road block for developing our product. There are only so many hours in the day... :-) It seems that the use of Xen in FreeBSD is increasing, so I'm hopeful more folks will step forward to improve other areas of our Xen support. I sympathize with your desire for more code comments to make it easier to ramp up on Xen. Unfortunately, there is little documentation about Xen other than the "Linux reference implementation", and it is usually quite terse in the comments department. I've done my best to improve this situation in the areas on which I've worked. Hopefully others will do the same and perhaps even give netfront the rewrite it deserves. -- Justin From owner-freebsd-xen@FreeBSD.ORG Tue Feb 1 00:18:30 2011 Return-Path: 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 89E431065675 for ; Tue, 1 Feb 2011 00:18:30 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (mail.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0BE8FC1D for ; Tue, 1 Feb 2011 00:18:30 +0000 (UTC) Received: from [192.168.4.138] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.4/8.14.4) with ESMTP id p110IOPS075740 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 17:18:25 -0700 (MST) (envelope-from gibbs@FreeBSD.org) Message-ID: <4D47514C.7090706@FreeBSD.org> Date: Mon, 31 Jan 2011 17:18:20 -0700 From: "Justin T. Gibbs" Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110123 Thunderbird/3.1.8 MIME-Version: 1.0 To: Janne Snabb References: In-Reply-To: X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (aslan.scsiguy.com [70.89.174.89]); Mon, 31 Jan 2011 17:18:25 -0700 (MST) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@FreeBSD.org Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gibbs@FreeBSD.org 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, 01 Feb 2011 00:18:30 -0000 On 1/15/2011 3:12 AM, Janne Snabb wrote: > On Sat, 15 Jan 2011, Janne Snabb wrote: > >> It appears that that the netfront driver fails to get the vif mac >> address which leads to panic shortly afterwards. > > The patch at the bottom of this message solves the problem for me. > After that the current 8.2RC2 system works fine on amd64 with XENHVM > kernel with Xen 4.0.1 (have not tested other versions). > > If the "mac" node does not appear in the front-end vif directory > (does it ever appear there? in my experience no), we fetch a link > to the backend directory for the same vif and try to get the "mac" > node from there. > > I am not sure if this is the proper way to fix this, but it works > for me. As with most things Xen, there is no official specification for what xenstore nodes are where. If we assume the Linux driver is the definitive reference, then the current FreeBSD driver behavior is correct: http://xenbits.xensource.com/linux-2.6.18-xen.hg?file/5e08fff8dc05/drivers/xen/netfront/netfront.c See talk_to_backend() and the xen_net_read_mac() function. There are two environments that setup the xenstore nodes: the Xen cloud platform, and the more common phython tool stack (aka xend). I haven't reviewed XCP, but Xend populates the MAC node in the frontend's tree unless the "ioemu" tag is in the VIF configuration line for that interface. Why this is the case, I have no idea - again the behavior is not documented. However, it seems reasonable to do what you've done in this patch and to rely on the backend's copy if the frontend's doesn't exist. It would also be good to add support to netfront to maintain the mac node in the frontend tree and to allow it to be set just like a real device. I believe netback will pick up and use the updated MAC value if you bounce the Xenbus connection after making the change. -- Justin From owner-freebsd-xen@FreeBSD.ORG Tue Feb 1 04:53:36 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D06A2106564A; Tue, 1 Feb 2011 04:53:36 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 99B428FC1B; Tue, 1 Feb 2011 04:53:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p114rakg039544; Tue, 1 Feb 2011 04:53:36 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p114raTJ039540; Tue, 1 Feb 2011 04:53:36 GMT (envelope-from linimon) Date: Tue, 1 Feb 2011 04:53:36 GMT Message-Id: <201102010453.p114raTJ039540@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154428: [xen] xn0 network interface and PF - Massive performance drop 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2011 04:53:36 -0000 Old Synopsis: xn0 network interface and PF - Massive performance drop New Synopsis: [xen] xn0 network interface and PF - Massive performance drop Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Tue Feb 1 04:53:08 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154428 From owner-freebsd-xen@FreeBSD.ORG Tue Feb 1 05:40:12 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CEFC1065674 for ; Tue, 1 Feb 2011 05:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 516568FC36 for ; Tue, 1 Feb 2011 05:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p115eC5D089393 for ; Tue, 1 Feb 2011 05:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p115eCXp089392; Tue, 1 Feb 2011 05:40:12 GMT (envelope-from gnats) Date: Tue, 1 Feb 2011 05:40:12 GMT Message-Id: <201102010540.p115eCXp089392@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Alex Cc: Subject: Re: kern/154428: xn0 network interface and PF - Massive performance drop X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex 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, 01 Feb 2011 05:40:12 -0000 The following reply was made to PR kern/154428; it has been noted by GNATS. From: Alex To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/154428: xn0 network interface and PF - Massive performance drop Date: Tue, 01 Feb 2011 14:29:58 +1100 Confirmed problem still evident in 8.2 RC3 (did a full source csup and buildworld). From owner-freebsd-xen@FreeBSD.ORG Fri Feb 4 19:31:47 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C86F1106564A; Fri, 4 Feb 2011 19:31:47 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9EA0F8FC08; Fri, 4 Feb 2011 19:31:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p14JVlrE033473; Fri, 4 Feb 2011 19:31:47 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p14JVlw6033463; Fri, 4 Feb 2011 19:31:47 GMT (envelope-from linimon) Date: Fri, 4 Feb 2011 19:31:47 GMT Message-Id: <201102041931.p14JVlw6033463@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154472: [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel rebooting on compile port libgcrypt 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2011 19:31:47 -0000 Old Synopsis: xen 4.0 - DomU freebsd8.1 i386 xen kernel rebooting on compile port libgcrypt New Synopsis: [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel rebooting on compile port libgcrypt Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Fri Feb 4 19:31:33 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154472 From owner-freebsd-xen@FreeBSD.ORG Fri Feb 4 19:32:04 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A0AD106564A; Fri, 4 Feb 2011 19:32:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 307568FC14; Fri, 4 Feb 2011 19:32:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p14JW4YQ033726; Fri, 4 Feb 2011 19:32:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p14JW4cH033722; Fri, 4 Feb 2011 19:32:04 GMT (envelope-from linimon) Date: Fri, 4 Feb 2011 19:32:04 GMT Message-Id: <201102041932.p14JW4cH033722@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154473: [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not Work SMP 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2011 19:32:04 -0000 Old Synopsis: xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not Work SMP New Synopsis: [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not Work SMP Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Fri Feb 4 19:31:51 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154473 From owner-freebsd-xen@FreeBSD.ORG Sat Feb 5 00:20:12 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C63AD106564A for ; Sat, 5 Feb 2011 00:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9B32A8FC0A for ; Sat, 5 Feb 2011 00:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p150KC1C032068 for ; Sat, 5 Feb 2011 00:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p150KCeC032067; Sat, 5 Feb 2011 00:20:12 GMT (envelope-from gnats) Date: Sat, 5 Feb 2011 00:20:12 GMT Message-Id: <201102050020.p150KCeC032067@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: "Likarpenkov ALexander" Cc: Subject: kern/154472: [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel rebooting on compile port libgcrypt X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Likarpenkov ALexander 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: Sat, 05 Feb 2011 00:20:12 -0000 The following reply was made to PR kern/154472; it has been noted by GNATS. From: "Likarpenkov ALexander" To: , Cc: Subject: kern/154472: [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel rebooting on compile port libgcrypt Date: Sat, 05 Feb 2011 02:18:56 +0200 Problem fixed on http://www.freebsd.org/cgi/query-pr.cgi?pr=140313 Src need patching /usr/src/sys/i386/xen/pmap.c on line 1075