Running OpenBMC in qemu

[Maxim Sloyko]

On Tue, Apr 18, 2017 at 10:01 AM, Maxim Sloyko <maxims at google.com> wrote:
> On Mon, Apr 17, 2017 at 5:56 PM, Robi Buranyi <rburanyi at google.com> wrote:
>> why does it have to be qemuarm exactly? You can equally run qemux86(-64),
>> and shall see no difference in test results.
>
> Well, I guess it does not *have* to be qemuarm, but last time I tried
> it, it worked, that's why I was running qemuarm. I was also under the
> impression that we are trying to support it.
>
> If it's broken beyond repair though, it's fine by me.
>
>>
>> so what has been working for me all the time [and still works with a
>> relatively recent gbmc checkout]
>> - build for machine qeumux86-64
>> - and run a console-only mode: runqemu qemux86-64 ext4
>> qemuparams="-nographic"

OK, so it turns out the problem was not arm vs x86, the problem was
the lack of -nographic parameter.
qemuarm image booted OK with -nographic parameter.

>>
>>
>>
>> On Mon, Apr 17, 2017 at 5:25 PM, Maxim Sloyko <maxims at google.com> wrote:
>>>
>>> Hi all!
>>>
>>> I've ran into troubles when I was trying to run OpenBMC image in qemu.
>>> It has been a while since I've done this, so I'm wondering if I'm
>>> missing something.
>>>
>>> I build it with:
>>>
>>> export TEMPLATECONF=meta-phosphor/conf
>>> source openbmc-env
>>> MACHINE=qemuarm bitbase obmc-phosphor-image
>>>
>>> With v1.0-stable openbmc/openbmc branch I get this output:
>>> http://pastebin.ca/3798183
>>>
>>> With the most recent version (master), I get very similar output,
>>> except that the error is now:
>>>
>>> VNC server running on ::1:5900
>>> vpb_sic_write: Bad register offset 0x2c
>>>
>>>
>>> In both cases the terminal I run this from basically just hangs.
>>>
>>> Am I missing something here?
>>>
>>> Thanks!
>>>
>>> --
>>> Maxim Sloyko
>>
>>
>
>
>
> --
> Maxim Sloyko



-- 
Maxim Sloyko