Eric Blake wrote:
> On 03/10/2011 01:54 AM, Daniel Veillard wrote:
>
>>> AC_MSG_NOTICE([VBox: $with_vbox])
>>> AC_MSG_NOTICE([ XenAPI: $with_xenapi])
>>> +AC_MSG_NOTICE([libxenlight: $with_libxl])
>>>
>> instead
>>AC_MSG_NOTICE([ libxl: $with_libxl])
>> or
>>AC_MSG_NOTICE
On 03/10/2011 01:54 AM, Daniel Veillard wrote:
>> AC_MSG_NOTICE([VBox: $with_vbox])
>> AC_MSG_NOTICE([ XenAPI: $with_xenapi])
>> +AC_MSG_NOTICE([libxenlight: $with_libxl])
>
> instead
>AC_MSG_NOTICE([ libxl: $with_libxl])
> or
>AC_MSG_NOTICE([xenlight: $with_libxl])
> would keep m
Markus Groß wrote:
> Am Donnerstag 10 März 2011 07:45:49 schrieb Jim Fehlig:
>
>> Add a new xen driver based on libxenlight [1], which is the primary
>> toolstack starting with Xen 4.1.0. The driver is stateful, runs
>> privileged only, and is accessed with libxl:/// URI.
>>
>> V5:
>> - Ensure
Am Donnerstag 10 März 2011 07:45:49 schrieb Jim Fehlig:
> Add a new xen driver based on libxenlight [1], which is the primary
> toolstack starting with Xen 4.1.0. The driver is stateful, runs
> privileged only, and is accessed with libxl:/// URI.
>
> V5:
> - Ensure events are unregistered when do
Daniel Veillard wrote:
> On Thu, Mar 10, 2011 at 07:53:58PM -0700, Jim Fehlig wrote:
>
>> Jim Fehlig wrote:
>>
>>> Daniel Veillard wrote:
>>>
Sure the URI is a very minimal
part compared to the actual XML description and code but the fact we are
using a different driv
On Fri, 11 Mar 2011, Jim Fehlig wrote:
> Daniel Veillard wrote:
> >
> > Okay, I tried t make sure libxl_domain_shutdown() is really
> > asynchronous in all cases, I somehow failed, can you confirm ?
> >
>
> Yes, AFAIK that is the case. Stefano, is that true?
>
Yes, libxl_domain_shutdown i
On Thu, Mar 10, 2011 at 07:36:08PM -0700, Jim Fehlig wrote:
> Daniel Veillard wrote:
> > On Wed, Mar 09, 2011 at 11:45:49PM -0700, Jim Fehlig wrote:
> > Okay, I tried t make sure libxl_domain_shutdown() is really
> > asynchronous in all cases, I somehow failed, can you confirm ?
> >
>
> Yes
On Thu, Mar 10, 2011 at 07:53:58PM -0700, Jim Fehlig wrote:
> Jim Fehlig wrote:
> > Daniel Veillard wrote:
> >> Sure the URI is a very minimal
> >> part compared to the actual XML description and code but the fact we are
> >> using a different driver internally could possibly be masked to the user
Hello,
Am Donnerstag 10 März 2011 09:54:52 schrieb Daniel Veillard:
> Okay, overall I would tend to ACK that patch based purely on the code,
> but I would like to get first a small discussion about somehow merging
> it in the xen:/// framework. Once commited it will be hard to change
> and impos
Jim Fehlig wrote:
> Daniel Veillard wrote:
>
>> On Wed, Mar 09, 2011 at 11:45:49PM -0700, Jim Fehlig wrote:
>>
>>
>>> Add a new xen driver based on libxenlight [1], which is the primary
>>> toolstack starting with Xen 4.1.0. The driver is stateful, runs
>>> privileged only, and is acces
Daniel Veillard wrote:
> On Wed, Mar 09, 2011 at 11:45:49PM -0700, Jim Fehlig wrote:
>
>> Add a new xen driver based on libxenlight [1], which is the primary
>> toolstack starting with Xen 4.1.0. The driver is stateful, runs
>> privileged only, and is accessed with libxl:/// URI.
>>
>> V5:
>>
On Wed, Mar 09, 2011 at 11:45:49PM -0700, Jim Fehlig wrote:
> Add a new xen driver based on libxenlight [1], which is the primary
> toolstack starting with Xen 4.1.0. The driver is stateful, runs
> privileged only, and is accessed with libxl:/// URI.
>
> V5:
> - Ensure events are unregistered wh
12 matches
Mail list logo