thr3ads.net - Xen devel - DomU creation failure for Xen-ARM [Oct 2013]

If this information is useful, please help other people find it:
Share via:

Vaibhav Bedia

2013-Oct-27 21:15 UTC

DomU creation failure for Xen-ARM

Hi,

By putting some stupid workaround in dist-tools creation step as
reported earlier
i now have a Ubuntu ARM system running on OMAP5 Dom0.

Currently DomU creation doesn''t work and following is what i get on the
console:
Any hints on how to proceed or debug this?

root@arm:/home/ubuntu# xl create domU
Parsing config from domU
Daemon running with PID 1800
root@arm:/home/ubuntu# (d1) 6Booting Linux on physical CPU 0x0
(d1) 5Linux version 3.12.0-rc5-00671-geb765a3-dirty
(vaibhav@vaibhav-VirtualBox) (gcc version 4.7.3 (Ubuntu/Linaro
4.7.3-1ubuntu1)
(d1) ) #11 SMP Sun Oct 27 16:31:24 EDT 2013
(d1) CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d
(d1) CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
(d1) 6Machine: Generic DT based system, model: XENVM-4.2
(d1) 6cma: CMA: reserved 16 MiB at 81000000
(d1) Memory policy: ECC disabled, Data cache writealloc
(d1) 7On node 0 totalpages: 8192
(d1) 7free_area_init_node: node 0, pgdat c089b940, node_mem_map c0e13000
(d1) 7  Normal zone: 64 pages used for memmap
(d1) 7  Normal zone: 0 pages reserved
(d1) 7  Normal zone: 8192 pages, LIFO batch:0
(d1) 6psci: probing function IDs from device-tree
(d1) 6PERCPU: Embedded 9 pages/cpu @c0e56000 s15232 r8192 d13440 u36864
(d1) 7pcpu-alloc: s15232 r8192 d13440 u36864 alloc=9*4096
(d1) 7pcpu-alloc:
(d1) Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 8128
(d1) 5Kernel command line: console=hvc0 root=/dev/xvda psci=enable
(d1) 6PID hash table entries: 128 (order: -3, 512 bytes)
(d1) 6Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
(d1) 6Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
(d1) Memory: 1600K/32768K available (5639K kernel code, 610K rwdata,
2144K rodata, 398K init, 5572K bss, 31168K reserved, 0K highmem
(d1) )
(d1) 5Virtual kernel memory layout:
(d1)     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
(d1)     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
(d1)     vmalloc : 0xc2800000 - 0xff000000   ( 968 MB)
(d1)     lowmem  : 0xc0000000 - 0xc2000000   (  32 MB)
(d1)     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
(d1)     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
(d1)       .text : 0xc0008000 - 0xc07a2084   (7785 kB)
(d1)       .init : 0xc07a3000 - 0xc0806b80   ( 399 kB)
(d1)       .data : 0xc0808000 - 0xc08a0a48   ( 611 kB)
(d1)        .bss : 0xc08a0a48 - 0xc0e11e40   (5573 kB)
(d1) 6Hierarchical RCU implementation.
(d1) 6  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
(d1) 6NR_IRQS:16 nr_irqs:16 16
(d1) arch_timer_init : 619 1
(d1) arch_timer_register 480
(d1) 6Architected cp15 timer(s) running at 6.14MHz (virt).
(d1) arch_counter_register 413
(d1) 6Switching to timer-based delay loop
(d1) 6sched_clock: ARM arch timer >56 bits at 6144kHz, resolution 162ns
(d1) 6sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps
every 4294967286ms
(d1) 6Console: colour dummy device 80x30
(d1) Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
(d1) ... MAX_LOCKDEP_SUBCLASSES:  8
(d1) ... MAX_LOCK_DEPTH:          48
(d1) ... MAX_LOCKDEP_KEYS:        8191
(d1) ... CLASSHASH_SIZE:          4096
(d1) ... MAX_LOCKDEP_ENTRIES:     16384
(d1) ... MAX_LOCKDEP_CHAINS:      32768
(d1) ... CHAINHASH_SIZE:          16384
(d1)  memory used by lock dependency info: 3695 kB
(d1)  per task-struct memory footprint: 1152 bytes
(d1) 6Calibrating delay loop (skipped), value calculated using timer
frequency.. 12.28 BogoMIPS (lpj=61440)
(d1) 6pid_max: default: 32768 minimum: 301
(d1) 6Security Framework initialized
(d1) 6Mount-cache hash table entries: 512
(d1) 6CPU: Testing write buffer coherency: ok
(d1) 3/cpus/cpu@0 missing clock-frequency property
(d1) 6CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
(d1) 6Setting up static identity map for 0xc0557a88 - 0xc0557ae0
(d1) 6Brought up 1 CPUs
(d1) 6SMP: Total of 1 processors activated.
(d1) 6CPU: All CPU(s) started in SVC mode.
(d1) 6devtmpfs: initialized
(d1) 6VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
(d1) 6Xen 4.2 support found, events_irq=31 gnttab_frame_pfn=b0000
(d1) 6xen:grant_table: Grant tables using version 1 layout
(d1) Grant table initialized
(d1) 6pinctrl core: initialized pinctrl subsystem
(d1) 6regulator-dummy: no parameters
(d1) 6NET: Registered protocol family 16
(d1) 6Xen: initializing cpu0
(d1) 4alloc_contig_range test_pages_isolated(81000, 81040) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81080) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 810c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81100) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81140) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81180) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 811c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81200) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81240) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81280) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 812c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81300) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81340) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81380) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 813c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81400) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81440) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81480) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 814c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81500) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81540) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81580) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 815c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81600) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81640) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81680) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 816c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81700) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81740) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81780) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 817c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81000, 81800) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81840) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81880) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 818c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81900) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81940) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81980) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 819c0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81a00) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81a40) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81a80) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81ac0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81b00) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81b40) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81b80) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81bc0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81c00) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81c40) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81c80) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81cc0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81d00) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81d40) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81d80) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81dc0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81e00) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81e40) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81e80) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81ec0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81f00) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81f40) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81f80) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 81fc0) failed
(d1) 4alloc_contig_range test_pages_isolated(81800, 82000) failed
(d1) 3DMA: failed to allocate 256 KiB pool for atomic coherent allocation
(d1) 4kworker/u2:0 invoked oom-killer: gfp_mask=0x3000d0, order=1,
oom_score_adj=0
(d1) dCPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted
3.12.0-rc5-00671-geb765a3-dirty #11
(d1) dWorkqueue: khelper __call_usermodehelper
(d1) [<c001b82c>] (unwind_backtrace+0x0/0xf8) from [<c0017cd0>]
(show_stack+0x10/0x14)
(d1) [<c0017cd0>] (show_stack+0x10/0x14) from [<c054ce50>]
(dump_stack+0x70/0x8c)
(d1) [<c054ce50>] (dump_stack+0x70/0x8c) from [<c054b8c4>]
(dump_header.isra.14+0x64/0x1ec)
(d1) [<c054b8c4>] (dump_header.isra.14+0x64/0x1ec) from [<c00d3e98>]
(out_of_memory+0x2c8/0x300)
(d1) [<c00d3e98>] (out_of_memory+0x2c8/0x300) from [<c00d7f9c>]
(__alloc_pages_nodemask+0x8b4/0x8e0)
(d1) [<c00d7f9c>] (__alloc_pages_nodemask+0x8b4/0x8e0) from
[<c003fe98>] (copy_process.part.55+0xec/0xf6c)
(d1) [<c003fe98>] (copy_process.part.55+0xec/0xf6c) from
[<c0040e64>]
(do_fork+0xb0/0x300)
(d1) [<c0040e64>] (do_fork+0xb0/0x300) from [<c00410dc>]
(kernel_thread+0x28/0x30)
(d1) [<c00410dc>] (kernel_thread+0x28/0x30) from [<c005615c>]
(__call_usermodehelper+0x28/0x90)
(d1) [<c005615c>] (__call_usermodehelper+0x28/0x90) from
[<c00598a0>]
(process_one_work+0x1b4/0x4a0)
(d1) [<c00598a0>] (process_one_work+0x1b4/0x4a0) from [<c0059f88>]
(worker_thread+0x138/0x37c)
(d1) [<c0059f88>] (worker_thread+0x138/0x37c) from [<c00607e8>]
(kthread+0xa4/0xb0)
(d1) [<c00607e8>] (kthread+0xa4/0xb0) from [<c0013e68>]
(ret_from_fork+0x14/0x2c)
(d1) Mem-info:
(d1) Normal per-cpu:
(d1) CPU    0: hi:    0, btch:   1 usd:   0
(d1) active_anon:0 inactive_anon:0 isolated_anon:0
(d1)  active_file:0 inactive_file:0 isolated_file:0
(d1)  unevictable:0 dirty:0 writeback:0 unstable:0
(d1)  free:0 slab_reclaimable:8 slab_unreclaimable:110
(d1)  mapped:0 shmem:0 pagetables:0 bounce:0
(d1)  free_cma:0
(d1) Normal free:0kB min:0kB low:0kB high:0kB active_anon:0kB
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB is
(d1) olated(anon):0kB isolated(file):0kB present:32768kB
managed:17984kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB
shmem:0kB sl
(d1) ab_reclaimable:32kB slab_unreclaimable:440kB kernel_stack:96kB
pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tm
(d1) p:0kB pages_scanned:0 all_unreclaimable? yes
(d1) lowmem_reserve[]: 0 0 0
(d1) Normal: 0*4kB 7*8kB (U) 2*16kB (UM) 0*32kB 0*64kB 1*128kB (U)
1*256kB (U) 1*512kB
(d1) (U) 0*1024kB 0*2048kB 0*4096kB 2*8192kB (I) = 17368kB
(d1) 0 total pagecache pages
(d1) 0 pages in swap cache
(d1) Swap cache stats: add 0, delete 0, find 0/0
(d1) Free swap  = 0kB
(d1) Total swap = 0kB
(d1) 8192 pages of RAM
(d1) 4357 free pages
(d1) 3696 reserved pages
(d1) 118 slab pages
(d1) 0 pages shared
(d1) 0 pages swap cached
(d1) 6[ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
(d1) 0Kernel panic - not syncing: Out of memory and no killable processes...
(d1)

Vaibhav Bedia

2013-Oct-29 01:07 UTC

head link

Re: DomU creation failure for Xen-ARM

On Sun, Oct 27, 2013 at 5:15 PM, Vaibhav Bedia <vaibhav.bedia@gmail.com>
wrote:> Hi,
>
> By putting some stupid workaround in dist-tools creation step as
> reported earlier
> i now have a Ubuntu ARM system running on OMAP5 Dom0.
>
I finally got a couple of DomUs using a ramdisk running on OMAP5 :)

The problem was due to the dtb for DomU allocating only 32MB of memory.
Once i increased that the error reported earlier went away.

The comment in xenvm-4.2.dts in the kernel seems to suggest the memory
node gets updated

memory@80000000 {
        device_type = "memory";
        /* this field is going to be adjusted by the hypervisor */
        reg = <0 0x80000000 0 0x08000000>;
};

Is there some config option to get this working as expected?

Thanks,
Vaibhav

Julien Grall

2013-Oct-29 23:06 UTC

head link

Re: DomU creation failure for Xen-ARM

On 10/28/2013 06:07 PM, Vaibhav Bedia wrote:> On Sun, Oct 27, 2013 at 5:15 PM, Vaibhav Bedia
<vaibhav.bedia@gmail.com> wrote:
>> Hi,
>>
>> By putting some stupid workaround in dist-tools creation step as
>> reported earlier
>> i now have a Ubuntu ARM system running on OMAP5 Dom0.
>>
>
> I finally got a couple of DomUs using a ramdisk running on OMAP5 :)
>
> The problem was due to the dtb for DomU allocating only 32MB of memory.
> Once i increased that the error reported earlier went away.
>
> The comment in xenvm-4.2.dts in the kernel seems to suggest the memory
> node gets updated
>
> memory@80000000 {
>          device_type = "memory";
>          /* this field is going to be adjusted by the hypervisor */
>          reg = <0 0x80000000 0 0x08000000>;
> };
>
> Is there some config option to get this working as expected?
Not yet. Ian Campbell is working on the auto-generation of domU device tree.
For now, if you want to change the amount of memory, you need to modify 
the device tree yourself and xl configuration file.

Cheers,

Julien

-- 
Julien Grall

Vaibhav Bedia

2013-Oct-29 23:55 UTC

head link

Re: DomU creation failure for Xen-ARM

Hi Julien,

On Tue, Oct 29, 2013 at 7:06 PM, Julien Grall <julien.grall@linaro.org>
wrote:>
>
> On 10/28/2013 06:07 PM, Vaibhav Bedia wrote:
>>
>> On Sun, Oct 27, 2013 at 5:15 PM, Vaibhav Bedia
<vaibhav.bedia@gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> By putting some stupid workaround in dist-tools creation step as
>>> reported earlier
>>> i now have a Ubuntu ARM system running on OMAP5 Dom0.
>>>
>>
>> I finally got a couple of DomUs using a ramdisk running on OMAP5 :)
>>
>> The problem was due to the dtb for DomU allocating only 32MB of memory.
>> Once i increased that the error reported earlier went away.
>>
>> The comment in xenvm-4.2.dts in the kernel seems to suggest the memory
>> node gets updated
>>
>> memory@80000000 {
>>          device_type = "memory";
>>          /* this field is going to be adjusted by the hypervisor */
>>          reg = <0 0x80000000 0 0x08000000>;
>> };
>>
>> Is there some config option to get this working as expected?
>
>
> Not yet. Ian Campbell is working on the auto-generation of domU device
tree.
> For now, if you want to change the amount of memory, you need to modify the
> device tree yourself and xl configuration file.
>
Ok. It took me some time to figure out why a change in the xl configuration file
was not taking effect. What do you think about increasing the default
value in the
device tree for now?

Regards,
Vaibhav

Xen devel - Oct 2013 - DomU creation failure for Xen-ARM

DomU creation failure for Xen-ARM

Re: DomU creation failure for Xen-ARM

Re: DomU creation failure for Xen-ARM

Re: DomU creation failure for Xen-ARM