Re: [Xen-users] DOMu failed to launch

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

Please keep the discussion on list and avoid HTML mails.

I didn't see anything confidentially looking in the logs so I've copied the
list for you this time.

On Wed, 2016-01-06 at 23:44 -0800, Atul Raut wrote:
> Hi Ian,
> 
> This is regarding my queries - http://comments.gmane.org/gmane.comp.emula
> tors.xen.user/86055Â; 
> Sorry I didnt got mail, where you answer.
> 
> Please find Attachment of my DomU config file & failure logs.

> libxl: verbose: libxl_create.c:101:libxl__domain_build_info_setdefault: 
> qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or 
> directory

I'm unsure why the tools think you need a qemu, AFAICT your configuration
doesn't. I'd suggest removing the serial=pty since that may be confusing
things and is meaningless for an ARM domain (it is specific to x86/HVM
guests)

> libxl: debug: libxl_create.c:945:initiate_domain_create: running bootloader
> libxl: debug: libxl_bootloader.c:330:libxl__bootloader_run: no bootloader 
> configured, using user supplied kernel
> libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch 
> w=0x435cf0: deregister unregistered
> domainbuilder: detail: xc_dom_allocate: cmdline="earlycon=xenboot 
> hostname=VM1 console=hvc1 root=/dev/ram nosoftlockup 
> rcu_cpu_stall_suppress=1", features="(null)"
> libxl: debug: libxl_dom.c:631:libxl__build_pv: pv kernel mapped 0 path 
> /boot/Image
> domainbuilder: detail: xc_dom_kernel_file: filename="/boot/Image"
> domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file 
> `/boot/Image')
> domainbuilder: detail: xc_dom_malloc_filemapÂÂÂÂ: 20233 kB
> domainbuilder: detail: xc_dom_ramdisk_file: filename="/boot/rootfs.cpio.gz"
> domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file 
> `/boot/rootfs.cpio.gz')

These two "ATUL - ... failed" messages: If it has failed why is it
continuing? Have you patched the source in some ways?

> domainbuilder: detail: xc_dom_malloc_filemapÂÂÂÂ: 2080 kB
> domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch64 
> xen-3.0-armv7l
> domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000
> 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: loader probe OK
> domainbuilder: detail: xc_dom_parse_zimage64_kernel: called
> domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 
> 0x40080000 -> 0x41442620
> libxl: debug: libxl_arm.c:776:libxl__arch_domain_init_hw_description: 
> constructing DTB for Xen version 4.6 guest
> libxl: debug: libxl_arm.c:777:libxl__arch_domain_init_hw_description:ÂÂ- vGIC 
> version: V3
> libxl: debug: libxl_arm.c:273:make_chosen_node: /chosen/bootargs = 
> earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram nosoftlockup 
> rcu_cpu_stall_suppress=1
> libxl: debug: libxl_arm.c:280:make_chosen_node: /chosen adding placeholder 
> linux,initrd properties
> libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder node 
> /memory@40000000
> libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder node 
> /memory@200000000
> libxl: debug: libxl_arm.c:871:libxl__arch_domain_init_hw_description: fdt 
> total size 1442
> domainbuilder: detail: xc_dom_devicetree_mem: called
> 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: set_mode: guest xen-3.0-aarch64, address size 64
> domainbuilder: detail: xc_dom_mallocÂÂÂÂÂÂÂÂÂÂÂÂ: 256 kB
> domainbuilder: detail: populate_guest_memory: populating RAM @ 
> 0000000040000000-0000000048000000 (128MB)
> domainbuilder: detail: populate_one_size: populated 0x40/0x40 entries with 
> shift 9
> domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x47df6000
> domainbuilder: detail: arch_setup_meminit: ramdisk: 0x47df6000 -> 0x47fff000
> domainbuilder: detail: arch_setup_meminit: devicetree: 0x47fff000 -> 
> 0x48000000
> libxl: debug: libxl_arm.c:936:libxl__arch_domain_finalise_hw_description: 
> /chosen updating initrd properties to cover 47df6000-47fff000
> libxl: debug: libxl_arm.c:902:finalise_one_memory_node: Populating 
> placeholder node /memory@40000000
> libxl: debug: libxl_arm.c:896:finalise_one_memory_node: Nopping out 
> placeholder node /memory@200000000
> domainbuilder: detail: xc_dom_build_image: called
> domainbuilder: detail: xc_dom_alloc_segment:ÂÂÂkernelÂÂÂÂÂÂÂ: 0x40080000 -> 
> 0x41443000ÂÂ(pfn 0x40080 + 0x13c3 pages)
> domainbuilder: detail: xc_dom_mallocÂÂÂÂÂÂÂÂÂÂÂÂ: 118 kB
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x40080+0x13c3 at 0x7f8d6e0000
> domainbuilder: detail: xc_dom_load_zimage_kernel: called
> domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 
> 0x40080000-0x41443000
> domainbuilder: detail: xc_dom_load_zimage_kernel: copy 20719136 bytes from 
> blob 0x7f8eced000 to dst 0x7f8d6e0000
> domainbuilder: detail: xc_dom_alloc_segment:ÂÂÂramdiskÂÂÂÂÂÂ: 0x47df6000 -> 
> 0x47fff000ÂÂ(pfn 0x47df6 + 0x209 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x47df6+0x209 at 0x7f8d4d7000
> domainbuilder: detail: xc_dom_alloc_segment:ÂÂÂdevicetreeÂÂÂ: 0x47fff000 -> 
> 0x48000000ÂÂ(pfn 0x47fff + 0x1 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x47fff+0x1 at 0x7f903dc000
> domainbuilder: detail: alloc_magic_pages: called
> domainbuilder: detail: count_pgtables_arm: called
> domainbuilder: detail: xc_dom_build_imageÂÂ: virt_alloc_end : 0x48000000
> domainbuilder: detail: xc_dom_build_imageÂÂ: virt_pgtab_end : 0x0
> domainbuilder: detail: xc_dom_boot_image: called
> domainbuilder: detail: arch_setup_bootearly: doing nothing
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> xen-3.0-aarch64 <= matches
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> xen-3.0-armv7l
> domainbuilder: detail: setup_pgtables_arm: called
> domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000
> domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001
> domainbuilder: detail: start_info_arm: called
> domainbuilder: detail: domain builder memory footprint
> domainbuilder: detail:ÂÂÂÂallocated
> domainbuilder: detail:ÂÂÂÂÂÂÂmallocÂÂÂÂÂÂÂÂÂÂÂÂÂ: 389 kB
> domainbuilder: detail:ÂÂÂÂÂÂÂanon mmapÂÂÂÂÂÂÂÂÂÂ: 0 bytes
> domainbuilder: detail:ÂÂÂÂmapped
> domainbuilder: detail:ÂÂÂÂÂÂÂfile mmapÂÂÂÂÂÂÂÂÂÂ: 22314 kB
> domainbuilder: detail:ÂÂÂÂÂÂÂdomU mmapÂÂÂÂÂÂÂÂÂÂ: 22324 kB
> domainbuilder: detail: vcpu_arm64: called
> domainbuilder: detail: DTB 47fff000
> domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000
> domainbuilder: detail: launch_vm: called, ctxt=0x7f903de004
> domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000
> domainbuilder: detail: xc_dom_release: called
> (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0)

Line 411 of this file in 4.6 isn't this log message (which appears to be
around line 523. What exact version of Xen are you running? Have you
patched it in any way?

> libxl: debug: libxl_event.c:2193:libxl__ao_progress_report: ao 0x435300: 
> progress report: callback queued aop=0x4398d0
> libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x435300: complete, 
> rc=0
> libxl: debug: libxl_event.c:1410:egc_run_callbacks: ao 0x435300: progress 
> report: callback aop=0x4398d0
> libxl: debug: libxl_create.c:1583:do_domain_create: ao 0x435300: inprogress: 
> poller=0x434ba0, flags=ic
> libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x435300: destroy
> xenconsole: Could not read tty from store: Success

Attachment: vm1.cfg
Description: Text document

Attachment: DomU_failure_logs.txt
Description: Text document

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