[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] XEN 4.5, odroid-xu, domU


   Thanks for the previous help wrt my attempts at getting XEN running
with dom0 on an exynos5410 based Odroid-XU.
   Currently, Things are OK with having a single CPU enabled.

   Previously, there was an issue with having to pass the Arch timer
frequency having to be passed through the DTS. I did successfully
update the Arch timer frequency in u-boot with the help of a modified
trustzone. It is still experimental, but the end result is that CNTFRQ
is read as 24000000 as required and not 0.

   Pursuing further, I am having issues starting a domU kernel. In all
the documentation I always find the dtb appended to the kernel. I am
refraining from doing so.

My domU config file:
root@odroid-desktop:~# cat vmTest.cfg
kernel = "/root/zImage.dom0"
memory = 512
name = "domuTest"
vcpus = 1
disk = [ 'phy:/dev/loop0,xvda,w' ]
extra = "console=hvc0 root=/dev/xvda debug rw"

I am using the same kernel which is running as dom0.

I create domU with: xl create vmTest.cfg
It creates is fine but then the domU kernel immediately crashes.

root@odroid-desktop:~# xl create vmTest.cfg -d
Parsing config from vmTest.cfg
    "domid": null,
    "config": {
        "c_info": {
            "type": "pv",
            "name": "domuTest",
            "uuid": "3cccea5b-330d-42a6-9d61-af3e3d6c588c",
            "run_hotplug_scripts": "True"
        "b_info": {
            "max_vcpus": 1,
            "avail_vcpus": [
            "max_memkb": 524288,
            "target_memkb": 524288,
            "shadow_memkb": 5120,
            "sched_params": {

            "claim_mode": "True",
            "type.pv": {
                "kernel": "/root/zImage.dom0",
                "cmdline": "console=hvc0 root=/dev/xvda debug rw"
        "disks": [
                "pdev_path": "/dev/loop0",
                "vdev": "xvda",
                "format": "raw",
                "readwrite": 1
        "on_reboot": "restart"

xl list
root@odroid-desktop:~# xl list
Name                                        ID   Mem VCPUs    State    Time(s)
Domain-0                                     0  1024     1     r-----     167.3
domuTest                                     3   512     1     ------      25.7

root@odroid-desktop:~# /usr/local/lib/xen/bin/xenctx 3
PC:       0000000c
CPSR:     600001d7
USR:               SP:00000000 LR:00000000
SVC: SPSR:000001d3 SP:40c579c0 LR:40c569c4
FIQ: SPSR:00000000 SP:00000000 LR:00000000
IRQ: SPSR:00000000 SP:00000000 LR:00000000
ABT: SPSR:600001d7 SP:00000000 LR:00000010
UND: SPSR:00000000 SP:00000000 LR:00000000

 r0_usr: 10000000     r1_usr: 0000001c     r2_usr: 40c569c4
 r3_usr: 00000030     r4_usr: 40c56980     r5_usr: 40008000
 r6_usr: ffffffff     r7_usr: 40c579e0     r8_usr: 40c679e0
 r9_usr: 407cda20    r10_usr: 407cd178    r11_usr: 40c569b4
r12_usr: 40c569b4

 r8_fiq: 00000000
 r9_fiq: 00000000    r10_fiq: 00000000    r11_fiq: 00000000
r12_fiq: 00000000

SCTLR: 00c5107d
TTBCR: 0000000000000000
TTBR0: 0000000040004000
TTBR1: 0000000000000000

Note that the PC is at 0x0000000c

My question, is how do I go about debugging this, as I do not get any
output nor a stack trace or anything in the XEN console.

The link: 
points at one such case where I could hit the issue. I do not have
CONFIG_DEBUG_LL set, but looks awefully similar to what is being
described. So, most probably this is the issue, as I do not see any
output as well.

Any and all help is deeply appreciated.

- Suriyan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.