About mdns, do you think it would be a good thing to *not* follow the
Avahi advise and explicitly set the host the service is running on? In my
humble opinion I think that would be a wise decision.
hostThe host this services is residing on. We recommend to pass NULL
here, the daemon will than
On Sat, 10 May 2008, Daniel P. Berrange wrote:
> I don't believe it is possible to distinguish shutdown vs destroy reliably.
If it was initiated by libvirt itself, I guess we can fire it after we
suddenly miss the domain. Destroy would be a direct miss that isn't marked
as crashed. (directly lead
On Sat, 10 May 2008, Daniel P. Berrange wrote:
> The code all looks good to me, but can you also provide an update for
> the default configuration file in qemud/libvirtd.conf with a (commented
> out) example setting.
Oops :) That didn't make it in the patch. But was already written. (Please
fix m
On Sat, May 10, 2008 at 06:12:23PM +0200, Stefan de Konink wrote:
> Hi,
>
> In the TODO list I find this line:
>
> - event on big domain state change (create, crashed, paused, shutdown,
> destroy)
>
>
> Because this is a feature that is very useful, I first wonder how libvirt
> reliably get 'ev
On Sat, May 10, 2008 at 05:31:53PM +0200, Stefan de Konink wrote:
> Hi,
>
>
> Mainly because I think Daniel always gives good feedback and comments,
> plus I don't want to be a troll on this list, I decided the time had come
> to spend some minutes to hack up a patch :)
>
> It has been tested:
>
Hi,
In the TODO list I find this line:
- event on big domain state change (create, crashed, paused, shutdown,
destroy)
Because this is a feature that is very useful, I first wonder how libvirt
reliably get 'events' itself for example from Xen? From what I can read
from xen_internal there is a x
Hi,
Mainly because I think Daniel always gives good feedback and comments,
plus I don't want to be a troll on this list, I decided the time had come
to spend some minutes to hack up a patch :)
It has been tested:
tcp0 0 192.168.0.5:16509 *:* LISTEN
vs
tc
