On Wed, 2020-02-19 at 01:31 +0100, Ján Tomko wrote: > To more closely match the previous usage in virEventPollDispatchHandles, > where called the handle callback for any revents returned by poll. > > This should fix the virtlogd error on subsequent domain startup: > error: can't connect to virtlogd: Cannot open log file: > '/var/log/libvirt/qemu/f28live.log': Device or resource busy > as well as virtlogd spinning caused by virLogHandlerDomainLogFileEvent > never being called on hangup. > > Signed-off-by: Ján Tomko <jto...@redhat.com> > Fixes: f8ab47cb4491dd72d866c1a96a9d94b8c3341de9 > Fixes: 946a25274c46ffff46323c62f567ae7e753aa921 > --- > src/util/vireventglibwatch.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-)
Dan and Pavel should confirm this is the correct way to address the issue, but it makes the problem go away on my machine so Tested-by: Andrea Bolognani <abolo...@redhat.com> -- Andrea Bolognani / Red Hat / Virtualization