On Fri, Nov 01, 2013 at 09:04:09AM +0800, jj zhong wrote: > I found the poll in virEventPollRunOnce (vireventpoll.c), a POLLHUP event > occurred for a pipe descriptor, thus the poll always returned because of > it.( the pipe broken). this may be the best I could track temporarily，I > don't know what to do netx , to mask the hangup event or to do something to > handle the hangup event , what to do ? Is it a bug or something ? Obviously there is a bug, since we should never go 100% CPU burn. We are already handling POLLHUP though - it gets mapped to VIR_EVENT_HANDLE_HANGUP Not sure why we continue to burn cycles though. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list