search for: qemu_

...this reason,I've compiled qemu 5.1 from source. Below I shown how I have configured everything such as a little piece of compilation messages : # apt install libgtk-3-dev libpulse-dev libgbm-dev libspice-protocol-dev libspice-server-dev libusb-1.0-0-dev libepoxy-dev # cd /usr/share # mv qemu qemu_ # cd /usr/lib # mv qemu qemu_ # cd /usr/lib/arm-linux-gnueabihf # mv qemu qemu_ # cd /usr/lib/ipxe # mv qemu qemu_ # cd /usr/share/bash-completion/completions/ # mv qemu qemu_ # mv qemu-kvm qemu-kvm_ # mv qemu-system-i386 qemu-system-i386_ # mv qemu-system-x86_64 qemu-system-x86_64_ # cd /usr/...

...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...

...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_lev...

...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 libvirt...