On 21.02.2014, at 12:21, Avik Sil <avik...@linux.vnet.ibm.com> wrote:
> On 02/21/2014 04:25 PM, Aneesh Kumar K.V wrote: >> Alexander Graf <ag...@suse.de> 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. Yes, he did. But to apply the update we first need the SLOF copy on git.qemu.org updated. Alex
