Mailing List Archive

Thanks Julien, it works now!
Now, I can start /bin/bash as Linux init process :)


Sincerely,
Thomas


On Wed, Mar 27, 2013 at 4:29 AM, Julien Grall <julien.grall@citrix.com>wrote:

> On 03/26/2013 04:04 PM, Anthony PERARD wrote:
>
> > CC'ing xen-devel, where the ARMv7+ port of Xen is happening.
> >
> > On 25/03/13 09:46, Sengul Thomas wrote:
> >> Hello Anthony,
> >> I'm hoping your are the right person to ask about xen-arm on Arndale.
> >>
> >> I've tried the following wiki to run xen-arm on Arndale and it crashes
> while booting dom0.
> >> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale
> >>
> >> Here goes some part of log (attached the full log):
> >>
> >> (XEN) Guest data abort: Translation fault at level 2
> >> (XEN) gva=23c1901c
> >> (XEN) gpa=0000000023c1901c
> >> (XEN) size=2 sign=0 write=1 reg=0
> >> (XEN) eat=0 cm=0 s1ptw=0 dfsc=6
> >> (XEN) dom0 IPA 0x0000000023c1901c
> >> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe
> >> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff
> >> (XEN) 2ND[0x11e] = 0x0000000000000000
> >> (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]----
> >> (XEN) CPU: 0
> >> (XEN) PC: 4000893c
> >>
> >> Looks like dom0 tried to access at 23c1901c and page fault happens.
> >> I've got no idea how to figure out what is going on.
> >> Could you tell me any helpful tips to move on further?
>
> It's seems the kernel is unable to start when the zImage is loaded at
> 0x40007000. If you change this address, both in U-Boot and the DTS, by
> 0x60000000 the kernel is able to start.
>
> I updated wiki page with the new instructions and the new device tree.
>
> Cheers,
>
> Julien
>
>

I'm using the root file system from "
http://snapshots.linaro.org/quantal/images/server/" and it lacks a lot of
stuffs for running domU.

Are you also using RFS above or another one?

Also, if you have a working RFS that can launch domU, could you post it on
wiki?

Thanks always,
Thomas





On Wed, Mar 27, 2013 at 4:29 AM, Julien Grall <julien.grall@citrix.com>wrote:

> On 03/26/2013 04:04 PM, Anthony PERARD wrote:
>
> > CC'ing xen-devel, where the ARMv7+ port of Xen is happening.
> >
> > On 25/03/13 09:46, Sengul Thomas wrote:
> >> Hello Anthony,
> >> I'm hoping your are the right person to ask about xen-arm on Arndale.
> >>
> >> I've tried the following wiki to run xen-arm on Arndale and it crashes
> while booting dom0.
> >> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale
> >>
> >> Here goes some part of log (attached the full log):
> >>
> >> (XEN) Guest data abort: Translation fault at level 2
> >> (XEN) gva=23c1901c
> >> (XEN) gpa=0000000023c1901c
> >> (XEN) size=2 sign=0 write=1 reg=0
> >> (XEN) eat=0 cm=0 s1ptw=0 dfsc=6
> >> (XEN) dom0 IPA 0x0000000023c1901c
> >> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe
> >> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff
> >> (XEN) 2ND[0x11e] = 0x0000000000000000
> >> (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]----
> >> (XEN) CPU: 0
> >> (XEN) PC: 4000893c
> >>
> >> Looks like dom0 tried to access at 23c1901c and page fault happens.
> >> I've got no idea how to figure out what is going on.
> >> Could you tell me any helpful tips to move on further?
>
> It's seems the kernel is unable to start when the zImage is loaded at
> 0x40007000. If you change this address, both in U-Boot and the DTS, by
> 0x60000000 the kernel is able to start.
>
> I updated wiki page with the new instructions and the new device tree.
>
> Cheers,
>
> Julien
>
>

Great! Thanks Julien for updating the wiki.

On Wed, 27 Mar 2013, Sengul Thomas wrote:
> Thanks Julien, it works now!
> Now, I can start /bin/bash as Linux init process :)
>
>
> Sincerely,
> Thomas
>
>
> On Wed, Mar 27, 2013 at 4:29 AM, Julien Grall <julien.grall@citrix.com> wrote:
> On 03/26/2013 04:04 PM, Anthony PERARD wrote:
>
> > CC'ing xen-devel, where the ARMv7+ port of Xen is happening.
> >
> > On 25/03/13 09:46, Sengul Thomas wrote:
> >> Hello Anthony,
> >> I'm hoping your are the right person to ask about xen-arm on Arndale.
> >>
> >> I've tried the following wiki to run xen-arm on Arndale and it crashes while booting dom0.
> >> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale
> >>
> >> Here goes some part of log (attached the full log):
> >>
> >> (XEN) Guest data abort: Translation fault at level 2
> >> (XEN)     gva=23c1901c
> >> (XEN)     gpa=0000000023c1901c
> >> (XEN)     size=2 sign=0 write=1 reg=0
> >> (XEN)     eat=0 cm=0 s1ptw=0 dfsc=6
> >> (XEN) dom0 IPA 0x0000000023c1901c
> >> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe
> >> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff
> >> (XEN) 2ND[0x11e] = 0x0000000000000000
> >> (XEN) ----[ Xen-4.3-unstable  arm32  debug=y  Tainted:    C ]----
> >> (XEN) CPU:    0
> >> (XEN) PC:     4000893c
> >>
> >> Looks like dom0 tried to access at 23c1901c and page fault happens.
> >> I've got no idea how to figure out what is going on.
> >> Could you tell me any helpful tips to move on further?
>
> It's seems the kernel is unable to start when the zImage is loaded at
> 0x40007000. If you change this address, both in U-Boot and the DTS, by
> 0x60000000 the kernel is able to start.
>
> I updated wiki page with the new instructions and the new device tree.
>
> Cheers,
>
> Julien
>
>
>
>

Hi Julien,

I am trying to use Xen on Arndale board with instrunction on page
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale

I am also facing a problem similar to the one that you debugged
before. Translation fault is happening at level3. The fault happens
when 0x12c20008 is accessed. This location happens to be a register of
UART2 port on Arndale. A part of the log is below. Any idea what
caused access to UART to fail?

(XEN) Device-tree contains "xen,xen" node. Ignoring.
(XEN) Populate P2M 0x50000000->0x60000000 (1:1 mapping for dom0)
(XEN) Loading kernel from boot module 1
(XEN) Loading zImage from 0000000060000000 to 0000000050008000-00000000503b6858
(XEN) Loading dom0 DTB to 0x000000005fe00000-0x000000005fe04442
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen)
(XEN) Freed 220kB init memory.
(XEN) Guest data abort: Translation fault at level 3
(XEN) gva=f7020008
(XEN) gpa=0000000012c20008
(XEN) size=2 sign=0 write=0 reg=2
(XEN) eat=0 cm=0 s1ptw=0 dfsc=7
(XEN) dom0 IPA 0x0000000012c20008
(XEN) P2M @ 02ffbf80 mfn:0xbfdfc
(XEN) 1ST[0x0] = 0x00000000bfdfe6ff
(XEN) 2ND[0x96] = 0x00000000bfd776ff
(XEN) 3RD[0x20] = 0x0000000000000000

Thanks,
Giridhar

On 27 March 2013 00:59, Julien Grall <julien.grall@citrix.com> wrote:
> On 03/26/2013 04:04 PM, Anthony PERARD wrote:
>
>> CC'ing xen-devel, where the ARMv7+ port of Xen is happening.
>>
>> On 25/03/13 09:46, Sengul Thomas wrote:
>>> Hello Anthony,
>>> I'm hoping your are the right person to ask about xen-arm on Arndale.
>>>
>>> I've tried the following wiki to run xen-arm on Arndale and it crashes while booting dom0.
>>> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale
>>>
>>> Here goes some part of log (attached the full log):
>>>
>>> (XEN) Guest data abort: Translation fault at level 2
>>> (XEN) gva=23c1901c
>>> (XEN) gpa=0000000023c1901c
>>> (XEN) size=2 sign=0 write=1 reg=0
>>> (XEN) eat=0 cm=0 s1ptw=0 dfsc=6
>>> (XEN) dom0 IPA 0x0000000023c1901c
>>> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe
>>> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff
>>> (XEN) 2ND[0x11e] = 0x0000000000000000
>>> (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]----
>>> (XEN) CPU: 0
>>> (XEN) PC: 4000893c
>>>
>>> Looks like dom0 tried to access at 23c1901c and page fault happens.
>>> I've got no idea how to figure out what is going on.
>>> Could you tell me any helpful tips to move on further?
>
> It's seems the kernel is unable to start when the zImage is loaded at
> 0x40007000. If you change this address, both in U-Boot and the DTS, by
> 0x60000000 the kernel is able to start.
>
> I updated wiki page with the new instructions and the new device tree.
>
> Cheers,
>
> Julien
>
>
> _______________________________________________
> Xen-arm mailing list
> Xen-arm@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm

_______________________________________________
Xen-arm mailing list
Xen-arm@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm