From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41124) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezM6t-0005dS-TZ for qemu-devel@nongnu.org; Fri, 23 Mar 2018 08:47:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ezM6t-0002mx-5Y for qemu-devel@nongnu.org; Fri, 23 Mar 2018 08:47:55 -0400 References: <6b4fbb94-2c28-27c2-17e4-b3ce593eb04d@redhat.com> <20180323121957.GM32362@xz-mi> From: Auger Eric Message-ID: Date: Fri, 23 Mar 2018 13:47:45 +0100 MIME-Version: 1.0 In-Reply-To: <20180323121957.GM32362@xz-mi> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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 Xu Cc: Peter Maydell , qemu-arm , qemu list Hi Peter, On 23/03/18 13:19, Peter Xu wrote: > On Fri, Mar 23, 2018 at 01:01:43PM +0100, 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? > > Maybe not concurrently inside libvirt, but after the patches AFAIK the > QMP part can be concurrent with something else or break some timing. > > Anyway, sorry for that! I'll see what I can do to help. No worries Thanks Eric >