search for: vserport_chang

Displaying 4 results from an estimated 4 matches for "vserport_chang".

Did you mean: vserport_change
2014 Nov 12
3
Re: Problem with the use of domfsfreeze mountpoint option
On 11.11.2014 22:51, Eric Blake wrote: > On 11/11/2014 01:58 PM, Payes Anand wrote: >> Hi everybody, >> >> I am having a problem with the use of domfsfreeze command. >> >> It is freezing all the filesystems present on the domain, >> >> instead of freezing just the mountpoints provided. >> >> I am issuing the command-- >> >> #
2014 Nov 14
2
Re: Problem with the use of domfsfreeze mountpoint option
...capabilities and make good >> decisions. And whenever we see a disconnect, we may just forget the >> qemu-ga capabilities and claim guest agent unresponsive (instead of this >> ping algorithm I'd came up with). > > Yes, qemu now provides that, as of qemu 2.1. It is the VSERPORT_CHANGE > event that fires whenever the guest opens or closes its connection to > the channel. And yes, we have more than one reason why we should wire > up libvirt to track when that event happens - we ALSO have people > requesting that we expose the information to management apps as a >...
2014 Nov 12
0
Re: Problem with the use of domfsfreeze mountpoint option
...uld query the qemu-ga capabilities and make good > decisions. And whenever we see a disconnect, we may just forget the > qemu-ga capabilities and claim guest agent unresponsive (instead of this > ping algorithm I'd came up with). Yes, qemu now provides that, as of qemu 2.1. It is the VSERPORT_CHANGE event that fires whenever the guest opens or closes its connection to the channel. And yes, we have more than one reason why we should wire up libvirt to track when that event happens - we ALSO have people requesting that we expose the information to management apps as a libvirt event. -- Eric...
2014 Nov 17
0
Re: Problem with the use of domfsfreeze mountpoint option
...od > >> decisions. And whenever we see a disconnect, we may just forget the > >> qemu-ga capabilities and claim guest agent unresponsive (instead of this > >> ping algorithm I'd came up with). > > > > Yes, qemu now provides that, as of qemu 2.1. It is the VSERPORT_CHANGE > > event that fires whenever the guest opens or closes its connection to > > the channel. And yes, we have more than one reason why we should wire > > up libvirt to track when that event happens - we ALSO have people > > requesting that we expose the information to manage...