From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59263) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezLgA-000198-Uh for qemu-devel@nongnu.org; Fri, 23 Mar 2018 08:20:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ezLg9-0006QE-IL for qemu-devel@nongnu.org; Fri, 23 Mar 2018 08:20:18 -0400 Date: Fri, 23 Mar 2018 12:19:43 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Message-ID: <20180323121943.GO16270@redhat.com> Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <6b4fbb94-2c28-27c2-17e4-b3ce593eb04d@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Regression on KVM qemu-system-aarch64 since "monitor: enable IO thread for (qmp & !mux) typed" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Auger Eric , qemu-arm , qemu list , Peter Xu On Fri, Mar 23, 2018 at 12:11:17PM +0000, Peter Maydell wrote: > On 23 March 2018 at 12:01, Auger Eric wrote: > > Hi, > > > > On 23/03/18 11:26, Peter Maydell wrote: > >> On 23 March 2018 at 10:24, Auger Eric wrote: > >>> Hi, > >>> > >>> I observe a regression on KVM accelerated qemu-system-aarch64: > >>> > >>> Unexpected error in kvm_device_access() at > >>> /home/augere/UPSTREAM/qemu/accel/kvm/kvm-all.c:2164: > >>> 2018-03-23T09:59:59.629439Z qemu-system-aarch64: KVM_GET_DEVICE_ATTR > >>> failed: Group 6 attr 0x000000000000c664: Device or resource busy > >>> 2018-03-23 10:00:00.085+0000: shutting down, reason=crashed > >> > >> Can you get a backtrace for this? (I guess you'd need to fiddle > >> with the kvm_device_access() code to make it assert rather > >> than passing back the error). > > > > OK. I will try to do so. As I could have expected, I cannot reproduce on > > a standalone qemu command line. The problem observed above is seen with > > libvirt launch which may be doing some other QMP stuff concurrently? > > Hmm, that could be a bit painful to debug. I dunno if libvirt > has a "launch QEMU under gdb" option. If not, you could try Nothing official, but the following trick should still work: https://www.berrange.com/posts/2011/10/12/debugging-early-startup-of-kvm-with-gdb-when-launched-by-libvirtd/ 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 :|