On Wed, Jan 30, 2008 at 09:41:36AM +, Keir Fraser wrote:
> A new releaase candidate is tagged in
> http://xenbits.xensource.com/xen-3.1-testing.hg. Assuming no problems are
> revealed by testing, I'd like to make this the proper 3.1.3 release asap.
I did some very basic testing of bits based
On Sun, Oct 22, 2006 at 05:09:35PM -0400, Jimi Xenidis wrote:
> Hollis and I touched on this and has been the bane of our existence
> since we were required to have Xen interpret user level pointers,
> thread started here:
> http://lists.xensource.com/archives/html/xen-devel/2005-08/
> msg0
On Thu, Aug 10, 2006 at 04:12:37PM -0500, Hollis Blanchard wrote:
> John, would you extend this scheme to cover host OS differences? I think
I think it makes sense to use a parallel scheme of xen/xend/host/ for
those parameters. That is, the way you've done this looks good to me.
> tools/python/
On Tue, Aug 08, 2006 at 11:15:18AM -0500, Hollis Blanchard wrote:
> > On Solaris some of the Xen binaries/scripts live
> > in different locations in order to meet our file system requirements.
>
> Does that impact code under tools/python/xen much?
Very little, but it does affect the location of
On Tue, Aug 08, 2006 at 10:34:25AM -0500, Hollis Blanchard wrote:
> Rather than having these inline tests everywhere ("if os.uname()[4] in
> ('ia64', 'ppc64'):"), would it make more sense to have some sort of
> "architecture" object, and do things like:
It'd be good if it were slightly more gener
