search for: qemu_monitor_

...disrupting libvirt in its initialization phase, it looks like nothing works. You could grab a backtrace of the qemu process and try on qemu-devel ML. Also, if you want to make sure (or see after what command gets stuck), you can enable debug logs for libvirt into some file and then grep that for QEMU_MONITOR_ and you'll see. [1] http://wiki.libvirt.org/page/DebugLogs [2] I'm not sure about the whole thing to look for, but this is enough)

...ts initialization phase, it looks like nothing works. > > You could grab a backtrace of the qemu process and try on qemu-devel > ML. Also, if you want to make sure (or see after what command gets > stuck), you can enable debug logs for libvirt into some file and then > grep that for QEMU_MONITOR_ and you'll see. > What should I be looking for? I see QEMU_MONITOR_ in the source (https://github.com/libvirt/libvirt/tree/v2.2-maint) but never see it in the logs. # pwd /etc/libvirt # diff libvirtd.conf libvirtd.conf.hold 1,4d0 < log_level = 1 < log_filters="3:remote 4:event...

...ase, it looks like nothing works. >> >> You could grab a backtrace of the qemu process and try on qemu-devel >> ML. Also, if you want to make sure (or see after what command gets >> stuck), you can enable debug logs for libvirt into some file and then >> grep that for QEMU_MONITOR_ and you'll see. >> >What should I be looking for? I see QEMU_MONITOR_ in the source >(https://github.com/libvirt/libvirt/tree/v2.2-maint) but never see it in >the logs. > ># pwd >/etc/libvirt ># diff libvirtd.conf libvirtd.conf.hold >1,4d0 >< log_level = 1 &...

...othing works. >>> >>> You could grab a backtrace of the qemu process and try on qemu-devel >>> ML. Also, if you want to make sure (or see after what command gets >>> stuck), you can enable debug logs for libvirt into some file and then >>> grep that for QEMU_MONITOR_ and you'll see. >>> >> What should I be looking for? I see QEMU_MONITOR_ in the source >> (https://github.com/libvirt/libvirt/tree/v2.2-maint) but never see it in >> the logs. >> >> # pwd >> /etc/libvirt >> # diff libvirtd.conf libvirtd.conf.h...

...6_64 (for example) and create a script with that >> filename that for example execs as qemu in strace with the output of >> strace put in some file, or similar. I can't think of anything else for >> now, sorry. > >I'll try this ASAP. First I'll look at all the QEMU_MONITOR_* log >entries that contain "error" that I *am* getting with qemu installed >from source (in /usr/local/bin/qemu-*) > >2017-06-05 23:06:39.884+0000: 15559: info : >virEventPollDispatchHandles:506 : EVENT_POLL_DISPATCH_HANDLE: watch=11 >events=1 >2017-06-05 23:06:39.884...

...ipt with that >>> filename that for example execs as qemu in strace with the output of >>> strace put in some file, or similar. I can't think of anything else >>> for >>> now, sorry. >> >> I'll try this ASAP. First I'll look at all the QEMU_MONITOR_* log >> entries that contain "error" that I *am* getting with qemu installed >> from source (in /usr/local/bin/qemu-*) >> >> 2017-06-05 23:06:39.884+0000: 15559: info : >> virEventPollDispatchHandles:506 : EVENT_POLL_DISPATCH_HANDLE: watch=11 >> events=...

On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >I've upgraded from Fedora 20; probably missed a merge of rpmnew with >existing .conf; permission problem, some other mistake along the way to >Fedora 25. > Yeah, probably some 'rpm -qV' (or whatever the command to verify all packages is) could help as well. >Is there a "how to" similar to [1]

...r/bin/qemu-system-x86_64 (for example) and create a script with that > filename that for example execs as qemu in strace with the output of > strace put in some file, or similar. I can't think of anything else for > now, sorry. I'll try this ASAP. First I'll look at all the QEMU_MONITOR_* log entries that contain "error" that I *am* getting with qemu installed from source (in /usr/local/bin/qemu-*) 2017-06-05 23:06:39.884+0000: 15559: info : virEventPollDispatchHandles:506 : EVENT_POLL_DISPATCH_HANDLE: watch=11 events=1 2017-06-05 23:06:39.884+0000: 15559: info : vir...

On Sat, Jun 03, 2017 at 09:22:58AM -0400, Michael C Cambria wrote: > > >On 06/02/2017 09:53 AM, Michael C. Cambria wrote: >> >> >> On 06/02/2017 09:43 AM, Martin Kletzander wrote: >>> [adding back the ML, you probably hit reply instead of reply-all, this >>> way other people might help if they know more] >>> >>> On Fri, Jun 02, 2017 at