Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

No.

--- On Mon, 4/13/09, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:

From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree
To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Christophe Saout" <christophe@xxxxxxxx>
Date: Monday, April 13, 2009, 9:28 AM

On Mon, Apr 13, 2009 at 11:18 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Sun, Apr 12, 2009 at 06:55:58PM +0200, Christophe Saout wrote:
>> Hi Pasi,
>>
>> > > Latest tree (as of today) doesn't seem to build for me:
>> > >
 [...]
>> > >
>> > > Known problem?
>> >
>> > [written by Jeremy Fitzhardine:]
>> >
>> > Yes, sorry.   I haven't been updating hackery much lately
during the
>> > merge window.  When we see what actually got merged next week,
I'll be
>> > rebuilding the xen.git branch structure into something a bit
cleaner to
>> > go on with.  I think push2/xen/dom0/master is in a workable
state.
>>
>> In the meantime, you can try to use that tree:
>>
>> http://git.saout.de/gitweb/?p=linux-dom0-pvops.git;a=summary
>>
>> It's the latest tip.git merged with one of the push branches from
>> Jeremy's git repo and cherry-picked commits from the backend,
blkback
>> and netback trees plus minor merge conflict and compile problem
fixups.
>> It seems
 feature-complete to me, stable and is able to run DomU
domains
>> without problems.


Can it run hvm domU?

>>
>
> Nice! I'll give it a try when I get back home from my easter trip :)
>
> Thanks!
>
> -- Pasi
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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

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