Re: [libvirt] mingw: virsh event loop failure in current git

2011-04-02 Thread Matthias Bolte
2011/4/1 Eric Blake : > On 03/15/2011 02:29 AM, Matthias Bolte wrote: >> Commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 "Expose event loop >> implementation as a public API" turned a failure to initialize the >> default event loop into a fatal error in virsh on Windows. Before that >> commit such

Re: [libvirt] mingw: virsh event loop failure in current git

2011-03-31 Thread Eric Blake
On 03/15/2011 02:29 AM, Matthias Bolte wrote: > Commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 "Expose event loop > implementation as a public API" turned a failure to initialize the > default event loop into a fatal error in virsh on Windows. Before that > commit such a failure was ignored. Does

Re: [libvirt] mingw: virsh event loop failure in current git

2011-03-29 Thread Bastien ROUCARIES
On Tue, Mar 29, 2011 at 8:48 AM, Paolo Bonzini wrote: > On 03/29/2011 01:27 AM, Eric Blake wrote: >> >> Paolo, any thoughts on the best approach to take?  (I know which way I'm >> leaning, but want some feedback before I give away my bias). > > Without guessing what your bias is, I also :) prefer

Re: [libvirt] mingw: virsh event loop failure in current git

2011-03-28 Thread Paolo Bonzini
On 03/29/2011 01:27 AM, Eric Blake wrote: Paolo, any thoughts on the best approach to take? (I know which way I'm leaning, but want some feedback before I give away my bias). Without guessing what your bias is, I also :) prefer to implement {g,s}et_nonblock_flag functions. It would use eithe

Re: [libvirt] mingw: virsh event loop failure in current git

2011-03-28 Thread Eric Blake
On 03/15/2011 05:02 AM, Daniel P. Berrange wrote: > On Tue, Mar 15, 2011 at 09:29:14AM +0100, Matthias Bolte wrote: >> Commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 "Expose event loop >> implementation as a public API" turned a failure to initialize the >> default event loop into a fatal error in

Re: [libvirt] mingw: virsh event loop failure in current git

2011-03-28 Thread Eric Blake
[adding bug-gnulib and Paolo as author of rpl_ioctl] On 03/15/2011 02:29 AM, Matthias Bolte wrote: > Commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 "Expose event loop > implementation as a public API" turned a failure to initialize the > default event loop into a fatal error in virsh on Windows.

Re: [libvirt] mingw: virsh event loop failure in current git

2011-03-15 Thread Daniel P. Berrange
On Tue, Mar 15, 2011 at 09:29:14AM +0100, Matthias Bolte wrote: > Commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 "Expose event loop > implementation as a public API" turned a failure to initialize the > default event loop into a fatal error in virsh on Windows. Before that > commit such a failure

[libvirt] mingw: virsh event loop failure in current git

2011-03-15 Thread Matthias Bolte
Commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 "Expose event loop implementation as a public API" turned a failure to initialize the default event loop into a fatal error in virsh on Windows. Before that commit such a failure was ignored. virEventRegisterDefaultImpl calls virEventPollInit that ca