Re: [Qemu-devel] [PATCH 00/28] target-ppc: Altivec 2.07

[Richard W.M. Jones]

On Thu, Feb 20, 2014 at 03:44:33PM +0100, Thomas Huth wrote:
> On Thu, 20 Feb 2014 12:34:00 +0000
> "Richard W.M. Jones" <address@hidden> wrote:
> 
> [...]
> > 
> > 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.
> 
> Yes, that's the Open Firmware prompt of the SLOF firmware here. If you
> know how to program in Forth, you can use it to debug the system.
> 
> > Populating /vdevice methods
> > Populating /vdevice/address@hidden
> > Populating /vdevice/address@hidden
> > C0580\b\b\b\b\bC05A0\b\b\b\b\bPopulating /address@hidden
> > ^M Adapters on 0800000020000000
> >                      00 0000 (D) : 106b 003f    serial bus [ usb-ohci ]
> >                      00 0800 (D) : 1af4 1004    virtio [ scsi ]
> > Populating /address@hidden/address@hidden
> >        SCSI: Looking for devices
> >           100000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           101000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           102000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           103000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           104000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           105000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           106000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           107000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> >           108000000000000 DISK     : "QEMU     QEMU HARDDISK    1.7."
> > C0600\b\b\b\b\bC0640\b\b\b\b\bC0690\b\b\b\b\bC06A0\b\b\b\b\bC06A8\b\b\b\b\bC06B0\b\b\b\b\bC06B8\b\b\b\b\bC06C0\b\b\b\b\b
> >  
> 
> So the last successful checkpoint seems to be C06C0 ? Looking at
> https://github.com/aik/SLOF/blob/master/board-qemu/slof/tree.fs
> there is not much critical stuff going on between that checkpoint and
> the next one, so I guess the firmware just ran out of internal memory.
> 
> When you run into this crash again, could you try to enter the
> following commands? They might help to confirm my suspicion:
> 
>  .free
>  .available
>  here .

I don't have a way to send commands here, since the appliance runs
completely captive.

However attached are:

 - the libvirt XML
 - the qemu command line

which may help to reproduce the bug.  I'm using upstream qemu + 91
patches provided by Tom, as detailed earlier in this thread.

> Please also say how much memory you were using for the guest.

I tried it with: 768 MB, 2048 MB and 20480 MB.  All failed in the same
way.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

libvirt.log
Description: Text document

guestfs-4xhp0yowac5zxg2u.log
Description: Text document