From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTcOY-0004yW-84 for qemu-devel@nongnu.org; Wed, 10 Feb 2016 16:33:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTcOX-0000YT-Bn for qemu-devel@nongnu.org; Wed, 10 Feb 2016 16:33:54 -0500 Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]:35324) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTcOW-0000YF-T8 for qemu-devel@nongnu.org; Wed, 10 Feb 2016 16:33:53 -0500 Received: by mail-wm0-x234.google.com with SMTP id c200so48163011wme.0 for ; Wed, 10 Feb 2016 13:33:52 -0800 (PST) Sender: Paolo Bonzini References: <20160210192648.GI16357@HEDWIG.INI.CMU.EDU> From: Paolo Bonzini Message-ID: <56BBACBD.4090300@redhat.com> Date: Wed, 10 Feb 2016 22:33:49 +0100 MIME-Version: 1.0 In-Reply-To: <20160210192648.GI16357@HEDWIG.INI.CMU.EDU> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] commit 5b82b70 boot problems List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Gabriel L. Somlo" , qemu-devel@nongnu.org Cc: stefanha@redhat.com On 10/02/2016 20:26, Gabriel L. Somlo wrote: > Hi Stefan, > > After pulling from upstream this morning, my guest VMs were no longer > able to boot. For instance, running something like > > bin/qemu-system-x86_64 -machine q35,accel=kvm -m 2048 -monitor stdio \ > -device ide-drive,bus=ide.2,drive=CD \ > -drive id=CD,if=none,snapshot=on,file=Fedora-Live-Workstation-x86_64-22-3.iso > > Would just hang with a black screen, or sometimes partially display > the GRUB boot menu, and never make it any further than that. > > After a bisect, I narrowed it down to 5b82b70 ("memory: RCU > ram_list.dirty_memory[] for safe RAM hotplug"); reverting that > commit got me back to where my VMs were working fine, but the > actual content of the changes isn't immediately obvious. > > Apologies for the noise in case you're already aware of the problem. No apologies needed, but indeed a fix is pending on the list (search for "memory" in today's subjects). Paolo > Otherwise, I'd be happy to test and send you debug output. > > Please advise. > > Thanks much, > --Gabriel > >