Re: [Xen-devel] Testing xen-arm on Arndale

[Sengul Thomas <thomas.sengul@xxxxxxxxx>]

On Wed, Mar 27, 2013 at 8:57 PM, Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> wrote:
> On Wed, 27 Mar 2013, Sengul Thomas wrote:

>
> In order to build /root/kernel, you just need to build a Linux tree v3.7
> or greater, build the dtbs, then:
>
> cat arch/arm/boot/zImage arch/arm/boot/dts/xenvm-4.2.dtb > kernel
>

Oh! It literally is appending :-)


>
>> Also, is there a helpful wiki link that describes manually building domU 
>> image?
>
> Not really, I could create one I guess.
> Right now I am using a simple script to create a domU filesystem from
> busybox and other libraries in dom0 on the fly:
>

Thanks for the script. But, at the moment, I'm just hoping to see some
booting messages poping out from console.
When I try 'xl create <some conf> -c', rather than booting messages,
following messages (attached the full log) pop out and domU dies.

(XEN) Guest data abort: Translation fault at level 1
(XEN)     gva=40004000
(XEN)     gpa=0000000040004000
(XEN)     instruction syndrome invalid
(XEN)     eat=0 cm=0 s1ptw=0 dfsc=5
(XEN) dom14 IPA 0x0000000040004000
(XEN) P2M @ 02ff9d40 mfn:0xbfcea
(XEN) 1ST[0x1] = 0x0000000000000000
(XEN) ----[ Xen-4.3-unstable  arm32  debug=y  Tainted:    C ]----
(XEN) CPU:    0
(XEN) PC:     80008338
(XEN) CPSR:   800001d3 MODE:SVC
(XEN)      R0: 40004000 R1: 00000c12 R2: 40008000 R3: 40004000
(XEN)      R4: 40008000 R5: 00000000 R6: 0000000e R7: ffffffff
(XEN)      R8: ffffffff R9: 40000000 R10:50000000 R11:10201105 R12:800080a8

After digging into domU Linux kernel, it turns out that someone tries
to access 0x40004000 while uncompressing zImage.
This is quite weird because, when I checked the page table setup for
domU, it starts mapping from 0x80000000 and 0x40004000 address is not
supposed to be accessed.
Do you guys have any hint about this?

Additionally, it turns out that if we try to use Linux kernel 3.8.4
(from https://www.kernel.org/), we do not see the above page-fault
messages and we can see domU is running using xl as follows:

    root@localhost:~# xl list
    Name                                        ID   Mem VCPUs
State    Time(s)
    Domain-0                                     0   256     1
r-----    2009.2
    win                                          1   128     1
------    1898.6

Unfortunately, I'm not still seeing any booting messages:

    root@localhost:~# xl create xl.conf -c
    Parsing config from xl.conf
    Daemon running with PID 1802
    <hangs here>

I'm running xenconsoled with the following command:

    root@localhost:~# xenconsoled --log=all

Then, I can see xenconsoled running in ps:

    root@localhost:~# ps ax | grep xenconsoled
     1767 ?        SLl    0:00 xenconsoled --log=all
     1839 pts/0    S+     0:00 grep --color=auto xenconsoled

I can see pid file is properly generated:

    root@localhost:~# cat /var/run/xenconsoled.pid
    1767

Log file is created (but sadly, no log messages):

   root@localhost:~# ls /var/log/xen/console/* -l
   -rw-r--r-- 1 root root 0 Mar 28 09:00 /var/log/xen/console/guest-win.log
   -rw-r--r-- 1 root root 0 Mar 28 09:00 /var/log/xen/console/hypervisor.log

I guess we are almost right there launching domU, only a little bit
more puzzle (I'm hoping) should be solved.
Do you guys have any hints or tips for solving this puzzle?


Fun hacking xen arm arndale,
Thomas

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