From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53938) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGoAY-0007KC-89 for qemu-devel@nongnu.org; Fri, 21 Feb 2014 06:21:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGoAR-0007PV-Df for qemu-devel@nongnu.org; Fri, 21 Feb 2014 06:21:26 -0500 Received: from e28smtp09.in.ibm.com ([122.248.162.9]:51025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGoAQ-0007P6-83 for qemu-devel@nongnu.org; Fri, 21 Feb 2014 06:21:19 -0500 Received: from /spool/local by e28smtp09.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 21 Feb 2014 16:51:13 +0530 Message-ID: <530736A2.2070608@linux.vnet.ibm.com> Date: Fri, 21 Feb 2014 16:51:06 +0530 From: Avik Sil MIME-Version: 1.0 References: <1392240199-2454-1-git-send-email-tommusta@gmail.com> <20140218185254.GA18678@redhat.com> <5303EC62.7020101@gmail.com> <20140220102342.GW1346@redhat.com> <20140220123400.GA3590@redhat.com> <296027B6-98E3-4D89-B469-D8520A409B3F@suse.de> <871tyw4twy.fsf@linux.vnet.ibm.com> In-Reply-To: <871tyw4twy.fsf@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 00/28] target-ppc: Altivec 2.07 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Aneesh Kumar K.V" Cc: QEMU Developers , Tom Musta , "list@suse.de:PowerPC" , Alexander Graf , "Richard W.M. Jones" On 02/21/2014 04:25 PM, Aneesh Kumar K.V wrote: > Alexander Graf writes: > >> >>> The second bug is kind of interesting. If you add ~ 256 disks (using >>> virtio-scsi), then it looks as if the firmware crashes. The total >>> console output is below. It looks as if "c >" is some kind of prompt. >>> qemu spins using 100% of CPU after this. >> >> How much RAM do you pass into the guest? Could you please try to >> increase that size to see whether it makes a difference? If it >> doesn't, Aneesh is your man :) > > Avik tells me that this is fixed in latest slof. Yes, the slof in upstream qemu is too old (Oct 15, 2013). With the latest slof in https://github.com/aik/SLOF.git this issue is fixed. AFAIR, Alexey was planning to send the latest slof to upstream qemu. Regards, Avik