[Xen-devel] Xen on Arm Arndale Exynos5250

[ed sandberg <ed.sandberg@xxxxxxxxxxxxxxxxx>]

I am trying to get xen running on an arndale Exynos5250.  I think I am
close to success because I can boot the hypervisor and interact with the
debug console and I don't see any errors.  I can switch the debug
console from xen mode to Dom0 mode by pressing CTRL-a three times,
however I am not prompted to login to Dom0 and I am not able to type any
commands.  I am unsure if the expected behavior is to receive a login
prompt when I switch to Dom0 mode or if I should be getting output on
the HDMI and that is where I would login to Dom0.

I have attached the putty log showing how I boot with all of the
environment variables I am using and after booting I pressed '*' to
print all diagnostics.

Here are my steps so far. I have done all of the compiling on the
arndale board running the linaro prebuilt image from:

https://releases.linaro.org/14.03/ubuntu/arndale/arndale-saucy_server_20140323-616.img.gz

I have followed the instructions here:

http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale

I initially got the following error compiling Linux:

    LD      sound/built-in.o
    MK_FW   firmware/edid-1920x1080.fw.gen.S
make[1]: *** No rule to make target `firmware/edid-1920x1080.fw',
needed by `firmware/edid-1920x1080.fw.gen.o'.  Stop.
make: *** [firmware] Error 2

so I changed the value set in /linux/linaro/configs/lt-arndale.conf from
CONFIG_EXTRA_FIRMWARE="edid-1920x1080.fw" to CONFIG_EXTRA_FIRMWARE=""

That is the only thing I did that deviated from the instructions.

My initial thought was that I needed to add a getty process on COM3, so
that when I switched to Dom0 mode I could login.  This page seems to
agree with me:

http://wiki.xenproject.org/wiki/Xen_Serial_Console

I tried to do so by creating a ttyS2.conf file under /etc/init/ that
read as follows:

start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]

respawn
exec /sbin/getty -8 115200 ttyS2

with that in place I was still not prompted to login but it had an
effect because the serial connection would become unresponsive after a
few minutes.

Attachment: arndale.log
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel