Date: Sun, 30 Jan 2011 13:10:27 -0800 From: Nick Sayer <nsayer@kfu.com> To: freebsd-xen@freebsd.org Subject: Re: HOWTO: xen tools within FreeBSD domU Message-ID: <F57CE724-0FC9-4914-8BE1-2CEEF424C47D@kfu.com> In-Reply-To: <alpine.BSF.2.00.1101301413520.20212@tiktik.epipe.com> References: <alpine.BSF.2.00.1101301111350.20212@tiktik.epipe.com> <alpine.BSF.2.00.1101301413520.20212@tiktik.epipe.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F57CE724-0FC9-4914-8BE1-2CEEF424C47D>