Hi All,
I am running XEN-ARM for vexpress on Fast Model and I am
able to boot a domo kernel. But when I try to create a domU and boot it using
xl it shows an error, in mapping page frame number(pfn) to machine frame number(mfn).
My domU kernel image contains the xenvm dtb appended to it, and is also getting
recognized. I am attaching the config file that I am using to create the domU.
The command that I am using for xl is “ xl –vvv create
/path/to/config/file”. The kernel versions for both dom0 and domU are
linux 3.8.0.rc3.I have reproduced the error below:
…
Parsing config from /root/myxm
libxl: verbose:
libxl_create.c:130:libxl__domain_build_info_setdefault: qemu-xen is
unavailable, use qemu-xen-traditional instead: No such file or directory
libxl: debug: libxl_create.c:1236:do_domain_create: ao
0x36268: create: how=(nil) callback=(nil) poller=0x346a8
libxl: debug:
libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda
spec.backend=unknown
libxl: debug:
libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda, using
backend phy
libxl: debug: libxl_create.c:682: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:608:libxl__ev_xswatch_deregister:
watch w=0x3655c: deregister unregistered
libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate:
New best NUMA placement candidate found: nr_nodes=1, nr_cpus=1, nr_vcpus=2,
free_memkb=1890
libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA
placement candidate with 1 nodes, 1 cpus and 1890 KB free selected
domainbuilder: detail: xc_dom_allocate:
cmdline="", features="(null)"
libxl: debug: libxl_dom.c:334:libxl__build_pv: pv kernel
mapped 0 path /root/image
domainbuilder: detail: xc_dom_kernel_file:
filename="/root/image"
domainbuilder: detail:
xc_dom_malloc_filemap : 2461 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.3,
caps xen-3.0-armv7l
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 (ARM) loader ...
domainbuilder: detail: xc_dom_probe_zimage_kernel: found
an appended DTB
domainbuilder: detail: loader probe OK
domainbuilder: detail: xc_dom_parse_zimage_kernel: called
domainbuilder: detail: xc_dom_parse_zimage_kernel:
xen-3.0-armv7l: RAM starts at 80000
domainbuilder: detail: xc_dom_parse_zimage_kernel:
xen-3.0-armv7l: 0x80008000 -> 0x8026f522
domainbuilder: detail: xc_dom_mem_init: mem 128 MB, pages
0x8000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x8000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail:
xc_dom_malloc
: 256 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:
kernel : 0x80008000 -> 0x80270000
(pfn 0x80008 + 0x268 pages)
Failed to map pfn to mfn rc:-14 pfn:864ae mfn:80008 Failed
to map pfn to mfn rc:-14 pfn:864ad mfn:80009
.
.
.
Failed to map pfn to mfn rc:-14 pfn:86a48 mfn:8026e
Failed to map pfn to mfn rc:-14 pfn:873d7 mfn:8026f
xc: error: panic: xc_dom_boot.c:197:
xc_dom_boot_domU_map: failed to mmap domU pages 0x80008+0x268 [mmap, errno=14
(Bad address)]: Internal error
libxl: error: libxl_dom.c:388:libxl__build_pv:
xc_dom_build_image failed: Bad address
domainbuilder: detail: xc_dom_release: called
libxl: error: libxl_create.c:907:domcreate_rebuild_done:
cannot (re-)build domain: -3
libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao
0x36268: complete, rc=-3
libxl: debug: libxl_create.c:1249:do_domain_create: ao
0x36268: inprogress: poller=0x346a8, flags=ic
libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao
0x36268: destroy
xc: debug: hypercall buffer: total allocations:120 total
releases:120
xc: debug: hypercall buffer: current allocations:0
maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:112 misses:4
toobig:4
…
Regards
Shubham Khandelwal
