Re: using libvirt 4.5 with upstream qemu
On 3/2/21 7:40 AM, Thanos Makatos wrote: -Original Message- From: Daniel Henrique Barboza Sent: 01 March 2021 18:07 To: Peter Krempa ; Thanos Makatos Cc: libvir-list@redhat.com Subject: Re: using libvirt 4.5 with upstream qemu On 3/1/21 12:47 PM, Peter Krempa wrote: On Mon, Mar 01, 2021 at 15:30:58 +, Thanos Makatos wrote: I'm trying to use QEMU master with libvirt 4.5 and QEMU seems to be hanging when I try to start a guest. My environment is a modified CentOS 7.9 installation using libvirt 4.5.0. When I use a modified version of QEMU 2.12 (reasonably close to the stock CentOS version) everything works fine. When I try to use a fairly recent version of QEMU (e.g. v5.2.0-729-g89ff714f4b). qemu 118657 1.6 0.0 0 0 ?Z14:50 0:00 [qemu-kvm] qemu 118664 0.0 0.0 207340 3560 ?Ssl 14:50 0:00 /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize qemu 118666 0.0 0.0 275008 13916 ?Sl 14:50 0:00 /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize These are possibly a leftover from libvirt's capability probing. I recall that we had some issue with capability detection qemu instances getting stuck but I don't remember the details any more. Not sure if related to this reported problem, but upstream QEMU when compiled with the trace backend was having problems daemonizing. I experienced a similar issue in the start of the year when running upstream Libvirt with upstream QEMU. I posted a patch fixing it in QEMU [1] but it wasn't pushed as of today. I am not sure if the problem was fixed in another way or if the patch I posted ended up left behind. Thanos, if you're compiling QEMU with a trace backend (e.g. with --enable- trace-backend= in ../configure) it might be worth compiling it without this option. There is a chance you're hitting same problem I mentioned above. Thanks Daniel, removing --enable-trace-backend did fix the issue! Glad I could help. Thanks for checking it out. Guess I'll ping the QEMU mailing list about the fix I posted. Seems like the daemonization is still broken upstream with the trace backend enabled. DHB
RE: using libvirt 4.5 with upstream qemu
> -Original Message- > From: Daniel Henrique Barboza > Sent: 01 March 2021 18:07 > To: Peter Krempa ; Thanos Makatos > > Cc: libvir-list@redhat.com > Subject: Re: using libvirt 4.5 with upstream qemu > > > > On 3/1/21 12:47 PM, Peter Krempa wrote: > > On Mon, Mar 01, 2021 at 15:30:58 +, Thanos Makatos wrote: > >> I'm trying to use QEMU master with libvirt 4.5 and QEMU seems to be > >> hanging when I try to start a guest. > >> > >> My environment is a modified CentOS 7.9 installation using libvirt > >> 4.5.0. When I use a modified version of QEMU 2.12 (reasonably close > >> to the stock CentOS > >> version) everything works fine. When I try to use a fairly recent > >> version of QEMU (e.g. v5.2.0-729-g89ff714f4b). > >> > >>qemu 118657 1.6 0.0 0 0 ?Z14:50 0:00 > >> [qemu-kvm] > > >>qemu 118664 0.0 0.0 207340 3560 ?Ssl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > >>qemu 118666 0.0 0.0 275008 13916 ?Sl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > > > > These are possibly a leftover from libvirt's capability probing. I > > recall that we had some issue with capability detection qemu instances > > getting stuck but I don't remember the details any more. > > Not sure if related to this reported problem, but upstream QEMU when > compiled with the trace backend was having problems daemonizing. I > experienced a similar issue in the start of the year when running upstream > Libvirt with upstream QEMU. > > I posted a patch fixing it in QEMU [1] but it wasn't pushed as of today. > I am not sure if the problem was fixed in another way or if the patch I posted > ended up left behind. > > Thanos, if you're compiling QEMU with a trace backend (e.g. with --enable- > trace-backend= in ../configure) it might be worth compiling it without this > option. There is a chance you're hitting same problem I mentioned above. Thanks Daniel, removing --enable-trace-backend did fix the issue!
Re: using libvirt 4.5 with upstream qemu
On 3/1/21 12:47 PM, Peter Krempa wrote: On Mon, Mar 01, 2021 at 15:30:58 +, Thanos Makatos wrote: I'm trying to use QEMU master with libvirt 4.5 and QEMU seems to be hanging when I try to start a guest. My environment is a modified CentOS 7.9 installation using libvirt 4.5.0. When I use a modified version of QEMU 2.12 (reasonably close to the stock CentOS version) everything works fine. When I try to use a fairly recent version of QEMU (e.g. v5.2.0-729-g89ff714f4b). qemu 118657 1.6 0.0 0 0 ?Z14:50 0:00 [qemu-kvm] qemu 118664 0.0 0.0 207340 3560 ?Ssl 14:50 0:00 /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize qemu 118666 0.0 0.0 275008 13916 ?Sl 14:50 0:00 /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize These are possibly a leftover from libvirt's capability probing. I recall that we had some issue with capability detection qemu instances getting stuck but I don't remember the details any more. Not sure if related to this reported problem, but upstream QEMU when compiled with the trace backend was having problems daemonizing. I experienced a similar issue in the start of the year when running upstream Libvirt with upstream QEMU. I posted a patch fixing it in QEMU [1] but it wasn't pushed as of today. I am not sure if the problem was fixed in another way or if the patch I posted ended up left behind. Thanos, if you're compiling QEMU with a trace backend (e.g. with --enable-trace-backend= in ../configure) it might be worth compiling it without this option. There is a chance you're hitting same problem I mentioned above. [1] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg00541.html Thanks, DHB /var/lib/libvirt/qemu/capabilities.pidfile contains the PID of the 2nd QEMU process and by experimenting I found that by killing the QEMU process NOT in the PID file the same thing happens again (maybe once more or twice) and then the guest boots fine. Does libvirt have some specific QEMU dependency? Is there some compatibility matrix I might have missed? I understand this may not be a supported configuration given that I'm not using vanilla libvirt/QEMU, however I'd appreciate some pointers so I can further debug this. I've trying debugging this in case there's some obvious error but didn't find anything interesting. Any ideas? In general, libvirt can't guarantee support of future qemu versions as qemu evolving and recently also deprecating and removing superseded configuration approaches, so you must cross-check with qemu's support policy. For debugging, debug logs may be helpful. In case a real VM getting stuck also the VM log file, but in your case the capability processes don't have that.
Re: using libvirt 4.5 with upstream qemu
On Mon, Mar 01, 2021 at 15:30:58 +, Thanos Makatos wrote: > I'm trying to use QEMU master with libvirt 4.5 and QEMU seems to be hanging > when I try to start a guest. > > My environment is a modified CentOS 7.9 installation using libvirt 4.5.0. When > I use a modified version of QEMU 2.12 (reasonably close to the stock CentOS > version) everything works fine. When I try to use a fairly recent version of > QEMU (e.g. v5.2.0-729-g89ff714f4b). > > qemu 118657 1.6 0.0 0 0 ?Z14:50 0:00 > [qemu-kvm] > qemu 118664 0.0 0.0 207340 3560 ?Ssl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > qemu 118666 0.0 0.0 275008 13916 ?Sl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize These are possibly a leftover from libvirt's capability probing. I recall that we had some issue with capability detection qemu instances getting stuck but I don't remember the details any more. > /var/lib/libvirt/qemu/capabilities.pidfile contains the PID of the 2nd QEMU > process and by experimenting I found that by killing the QEMU process NOT in > the PID file the same thing happens again (maybe once more or twice) and then > the guest boots fine. > > Does libvirt have some specific QEMU dependency? Is there some compatibility > matrix I might have missed? I understand this may not be a supported > configuration given that I'm not using vanilla libvirt/QEMU, however I'd > appreciate some pointers so I can further debug this. I've trying debugging > this in case there's some obvious error but didn't find anything interesting. > > Any ideas? In general, libvirt can't guarantee support of future qemu versions as qemu evolving and recently also deprecating and removing superseded configuration approaches, so you must cross-check with qemu's support policy. For debugging, debug logs may be helpful. In case a real VM getting stuck also the VM log file, but in your case the capability processes don't have that.
RE: using libvirt 4.5 with upstream qemu
> -Original Message- > From: Daniel P. Berrangé > Sent: 01 March 2021 15:39 > To: Thanos Makatos > Cc: libvir-list@redhat.com > Subject: Re: using libvirt 4.5 with upstream qemu > > On Mon, Mar 01, 2021 at 03:30:58PM +, Thanos Makatos wrote: > > I'm trying to use QEMU master with libvirt 4.5 and QEMU seems to be > > hanging when I try to start a guest. > > > > My environment is a modified CentOS 7.9 installation using libvirt > > 4.5.0. When I use a modified version of QEMU 2.12 (reasonably close to > > the stock CentOS > > version) everything works fine. When I try to use a fairly recent > > version of QEMU (e.g. v5.2.0-729-g89ff714f4b). > > > > qemu 118657 1.6 0.0 0 0 ?Z14:50 0:00 > > [qemu-kvm] > > > qemu 118664 0.0 0.0 207340 3560 ?Ssl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > > qemu 118666 0.0 0.0 275008 13916 ?Sl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > > > > /var/lib/libvirt/qemu/capabilities.pidfile contains the PID of the 2nd > > QEMU process and by experimenting I found that by killing the QEMU > > process NOT in the PID file the same thing happens again (maybe once > > more or twice) and then the guest boots fine. > > > > Does libvirt have some specific QEMU dependency? Is there some > > compatibility matrix I might have missed? I understand this may not be > > a supported configuration given that I'm not using vanilla > > libvirt/QEMU, however I'd appreciate some pointers so I can further > > debug this. I've trying debugging this in case there's some obvious error > > but > didn't find anything interesting. > > You want libvirt to be the same age as the QEMU you're using, or newer. Makes sense, thanks. > > New libvirt is expected to work with old QEMU. > > Old libvirt may not work with new QEMU. > > QEMU's deprecation process leads to code/behaviour being > removed/changed over time and this may break old libvirt. I don't know the > cause of the problem in your specific case, but personally i wouldn't spend > time trying to debug it as it isn't a scenario we attempt to support.
Re: using libvirt 4.5 with upstream qemu
On Mon, Mar 01, 2021 at 03:30:58PM +, Thanos Makatos wrote: > I'm trying to use QEMU master with libvirt 4.5 and QEMU seems to be hanging > when I try to start a guest. > > My environment is a modified CentOS 7.9 installation using libvirt 4.5.0. When > I use a modified version of QEMU 2.12 (reasonably close to the stock CentOS > version) everything works fine. When I try to use a fairly recent version of > QEMU (e.g. v5.2.0-729-g89ff714f4b). > > qemu 118657 1.6 0.0 0 0 ?Z14:50 0:00 > [qemu-kvm] > qemu 118664 0.0 0.0 207340 3560 ?Ssl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > qemu 118666 0.0 0.0 275008 13916 ?Sl 14:50 0:00 > /usr/libexec/qemu-kvm -S -no-user-config -nodefaults -nographic -machine > none,accel=kvm:tcg -qmp > unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile > /var/lib/libvirt/qemu/capabilities.pidfile -daemonize > > /var/lib/libvirt/qemu/capabilities.pidfile contains the PID of the 2nd QEMU > process and by experimenting I found that by killing the QEMU process NOT in > the PID file the same thing happens again (maybe once more or twice) and then > the guest boots fine. > > Does libvirt have some specific QEMU dependency? Is there some compatibility > matrix I might have missed? I understand this may not be a supported > configuration given that I'm not using vanilla libvirt/QEMU, however I'd > appreciate some pointers so I can further debug this. I've trying debugging > this in case there's some obvious error but didn't find anything interesting. You want libvirt to be the same age as the QEMU you're using, or newer. New libvirt is expected to work with old QEMU. Old libvirt may not work with new QEMU. QEMU's deprecation process leads to code/behaviour being removed/changed over time and this may break old libvirt. I don't know the cause of the problem in your specific case, but personally i wouldn't spend time trying to debug it as it isn't a scenario we attempt to support. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
