Re: [Qemu-devel] sparc-softmmu with sun prom image?

[Blue Swirl]

On 5/7/09, Robert Reif <address@hidden> wrote:
> Brian Wheeler wrote:
>
> > I grabbed a prom image from my SS10 and it mostly works, but the idprom
> > stuff seems to be broken.  Has anyone tried this?  When I run 'printenv'
> > at the ok prompt it gives me a data access error and when I turned on
> > the debuging of unmapped memory, it would try to read at an offset just
> > above the allocated ram.
> >
> > Brian
> >
> >
> >
> >
>  Here is a patch I did about a month ago when more OpenBios
>  parameters were added to nvram.  The format used by
>  OpenBios is different from OpenBoot so the added parameters
>  made running an OpenBoot PROM image worse than before.
>
>  This patch lets you load nvram from a file rather than letting
>  qemu fill it with OpenBios parameters.  Use a file with all zeros
>  except for the idprom area.  I have a small program to generate
>  an nvram image with idprom for an SS-10. Start OpenBoot and run
>  set-defaults just like you would with a new NVRAM chip.  You
>  will then be able to run printenv without a crash.  You could also
>  get the nvram image from a real machine.
>
>  I never submitted this patch because there in no simple way
>  to save the nvram contents at program exit.  There are no
>  destructor functions for either QEMUMachine or a QEMU
>  hardware device.  Is anyone else interested in adding
>  destructor functions to devices or machines?  Is this even
>  feasible?

I think this is similar issue but somewhat separate to VM
snapshotting. The user can load an initial VM snapshot, snapshot load
and save can be commanded from monitor and by default, at least the
disk image is updated, unless in snapshot mode.

IMHO NVRAM (and PC CMOS, pflash etc.) should act the same way. Maybe
qcow etc could be reused?

>  I also have a small patch for eccmemctl and a large patch
>  for better SuperSPARC CPU support that I'm sitting on.  They
>  help a little with getting an SS-10 OpenBoot PROM working
>  better but there is still a long way to go.  The biggest piece
>  missing from QEMU is probably sbus emulation.  This will
>  be needed before OpenBoot could be used to load an OS.

What's missing from Sbus emulation? I know probing and slot
enable/disable does not work, are there other known issues?