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"