Help, can't boot my arm linux guest on cubieboard2(arm host)

Help, can't boot my arm linux guest on cubieboard2(arm host)

[Coney Wu]

[-- Attachment #1.1: Type: text/plain, Size: 4996 bytes --]

Hi there,

I am very new to xen, and this is the first time for me to use the xen. I setup the xen host according to this article on my cubieboard:http://openmirage.org/wiki/xen-on-cubieboard2
but when I want to start the the guest os, there is a problem:

root@linaro-developer:~/vm# xl -vvv create domu_test -c
Parsing config from domu_test
libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x374a0: create: how=(nil) callback=(nil) poller=0x33e40
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or directory
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:286:libxl__device_disk_set_backend: Disk vdev=xvda, using backend phy
libxl: debug: libxl_create.c:797:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no bootloader configured, using user supplied kernel
libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch w=0x377c0: deregister unregistered
libxl: notice: libxl_numa.c:491:libxl__get_numa_candidate: NUMA placement failed, performance might be affected
domainbuilder: detail: xc_dom_allocate: cmdline="console=hvc0 xencons=tty root=/dev/xvda", features="(null)"
libxl: debug: libxl_dom.c:357:libxl__build_pv: pv kernel mapped 0 path /boot/zImage
domainbuilder: detail: xc_dom_kernel_file: filename="/boot/zImage"
domainbuilder: detail: xc_dom_malloc_filemap    : 4730 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.4, caps xen-3.0-armv7l
domainbuilder: detail: xc_dom_rambase_init: RAM starts at 80000
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM64) loader ...
domainbuilder: detail: xc_dom_probe_zimage64_kernel: kernel is not an arm64 Image
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM32) loader ...
domainbuilder: detail: loader probe OK
domainbuilder: detail: xc_dom_parse_zimage32_kernel: called
domainbuilder: detail: xc_dom_parse_zimage32_kernel: xen-3.0-armv7l: 0x80008000 -> 0x804a6b68
libxl: debug: libxl_arm.c:433:libxl__arch_domain_configure: constructing DTB for Xen version 4.4 guest
libxl: debug: libxl_arm.c:497:libxl__arch_domain_configure: fdt total size 1274
domainbuilder: detail: xc_dom_devicetree_mem: called
domainbuilder: detail: xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x20000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: set_mode: guest xen-3.0-armv7l, address size 32
domainbuilder: detail: xc_dom_malloc            : 1024 kB
xc: detail: Failed allocation for dom 4: 131072 extents of order 0
domainbuilder: detail: arch_setup_meminit: devicetree: 0x88000000 -> 0x880004fa
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x80008000 -> 0x804a7000  (pfn 0x80008 + 0x49f pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x80008+0x49f at 0xb6342000
domainbuilder: detail: xc_dom_load_zimage_kernel: called
domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x80008000-0x804a7000
domainbuilder: detail: xc_dom_load_zimage_kernel: copy 4844392 bytes from blob 0xb68e2000 to dst 0xb6342000
domainbuilder: detail: xc_dom_alloc_segment:   devicetree   : 0x88000000 -> 0x88001000  (pfn 0x88000 + 0x1 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x88000+0x1 at 0xb6f9c000
domainbuilder: detail: alloc_magic_pages: called
xc: detail: Failed allocation for dom 4: 2 extents of order 0
libxl: error: libxl_dom.c:423:libxl__build_pv: xc_dom_build_image failed: Device or resource busy
domainbuilder: detail: xc_dom_release: called
libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot (re-)build domain: -3
libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x374a0: complete, rc=-3
libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x374a0: inprogress: poller=0x33e40, flags=ic
libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x374a0: destroy
xc: debug: hypercall buffer: total allocations:154 total releases:154
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:146 misses:4 toobig:4


the first time when I boot the guest os, it is stuck at the starting ssh server, and I destroy the guest, and try to recreate it, I got this issue. I tried to rebuild the guest system, and reboot the cubieboard, but the problem is still here.

Is there something wrong with my zImage ? Any documents for this error?

Thank you!


[-- Attachment #1.2: Type: text/html, Size: 6099 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Help, can't boot my arm linux guest on cubieboard2(arm host)

[Ian Campbell]

On Tue, 2014-05-13 at 12:04 +0800, Coney Wu wrote:

User support questions such as this really belong on the xen-user@ list.
[...]
> xc: detail: Failed allocation for dom 4: 131072 extents of order 0
[...]
> domainbuilder: detail: alloc_magic_pages: called
> xc: detail: Failed allocation for dom 4: 2 extents of order 0

It seems like there isn't sufficient free RAM to build the guest.

What does "xl info" tell you? Are there other domains already running
(output of "xl list")? How much RAM have you given dom0? IIRC
cubieboard2's have 1G on them.

Ian.

Re: Help, can't boot my arm linux guest on cubieboard2(arm host)

[Coney Wu]

Yes, It was the memory issue, I reduce the dom0 memory to 256M, and it works now, 
Thanks very much.

On May 13, 2014, at 19:22, Ian Campbell <Ian.Campbell@citrix.com> wrote:

> On Tue, 2014-05-13 at 12:04 +0800, Coney Wu wrote:
> 
> User support questions such as this really belong on the xen-user@ list.
> [...]
>> xc: detail: Failed allocation for dom 4: 131072 extents of order 0
> [...]
>> domainbuilder: detail: alloc_magic_pages: called
>> xc: detail: Failed allocation for dom 4: 2 extents of order 0
> 
> It seems like there isn't sufficient free RAM to build the guest.
> 
> What does "xl info" tell you? Are there other domains already running
> (output of "xl list")? How much RAM have you given dom0? IIRC
> cubieboard2's have 1G on them.
> 
> Ian.
> 
>