Re: [Minios-devel] [Unikraft] Unable to run hello-world app on Xen on x86_64

[Simon Kuenzer <simon.kuenzer@xxxxxxxxx>]

Hey Ajay,

can you show me your helloworld.cfg (or is it the one from the wiki)? 
How did you install Xen? Which distro do you use for your Dom0? Did all 
required services for Xen get initialized and run in your Dom0?
Thanks,

Simon

On 04.04.2018 06:20, Ajay Garg wrote:
> Following is the log, when starting the domain with verbose-logging 
> enabled :
>
> ########################################################
> root@Latitude-3480:/home/ajay/unikraft/apps/helloworld# *xl -vv create 
> -c helloworld.cfg*
> Parsing config from helloworld.cfg
> domainbuilder: detail: xc_dom_allocate: cmdline="(null)", features="(null)"
> domainbuilder: detail: xc_dom_kernel_file: 
> filename="./build/helloworld_xen-x86_64"
> domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps 
> xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p 
> hvm-3.0-x86_64
> 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 bzImage loader ...
> domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> domainbuilder: detail: loader probe failed
> domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ...
> domainbuilder: detail: loader probe OK
> xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x5a088
> xc: detail: elf_parse_binary: memory: 0x0 -> 0x5a088
> xc: detail: elf_xen_parse_note: GUEST_OS = "Unikraft"
> xc: detail: elf_xen_parse_note: LOADER = "generic"
> xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0x3000
> xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
> xc: detail: elf_xen_parse: using notes from SHT_NOTE section
> xc: detail: elf_xen_addr_calc_check: VIRT_BASE unset, using 0x0
> xc: detail: elf_xen_addr_calc_check: ELF_PADDR_OFFSET unset, using 0x0
> xc: detail: elf_xen_addr_calc_check: addresses:
> xc: detail:     virt_base        = 0x0
> xc: detail:     elf_paddr_offset = 0x0
> xc: detail:     virt_offset      = 0x0
> xc: detail:     virt_kstart      = 0x0
> xc: detail:     virt_kend        = 0x5a088
> xc: detail:     virt_entry       = 0x1000
> xc: detail:     p2m_base         = 0xffffffffffffffff
> domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 
> 0x5a088
> domainbuilder: detail: xc_dom_mem_init: mem 4 MB, pages 0x400 pages, 4k each
> domainbuilder: detail: xc_dom_mem_init: 0x400 pages
> domainbuilder: detail: xc_dom_boot_mem_init: called
> domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
> domainbuilder: detail: xc_dom_build_image: called
> domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x0 -> 
> 0x5b000  (pfn 0x0 + 0x5b pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x0+0x5b at 0x7fe015720000
> xc: detail: elf_load_binary: phdr 0 at 0x7fe015720000 -> 0x7fe01572f15c
> domainbuilder: detail: xc_dom_alloc_segment:   phys2mach    : 0x5b000 -> 
> 0x5d000  (pfn 0x5b + 0x2 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x5b+0x2 at 0x7fe01578e000
> domainbuilder: detail: xc_dom_alloc_page   :   start info   : 0x5d000 
> (pfn 0x5d)
> domainbuilder: detail: xc_dom_alloc_page   :   xenstore     : 0x5e000 
> (pfn 0x5e)
> domainbuilder: detail: xc_dom_alloc_page   :   console      : 0x5f000 
> (pfn 0x5f)
> domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 
> 0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 
> 0x0000000000000000 -> 0x0000007fffffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 
> 0x0000000000000000 -> 0x000000003fffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 
> 0x0000000000000000 -> 0x00000000003fffff, 2 table(s)
> domainbuilder: detail: xc_dom_alloc_segment:   page tables  : 0x60000 -> 
> 0x65000  (pfn 0x60 + 0x5 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x60+0x5 at 0x7fe015789000
> domainbuilder: detail: xc_dom_alloc_page   :   boot stack   : 0x65000 
> (pfn 0x65)
> domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x66000
> domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x400000
> 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-x86_64 <= matches
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> xen-3.0-x86_32p
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> hvm-3.0-x86_32
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> hvm-3.0-x86_32p
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> hvm-3.0-x86_64
> domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x400
> domainbuilder: detail: clear_page: pfn 0x5f, mfn 0x130c5f
> domainbuilder: detail: clear_page: pfn 0x5e, mfn 0x130c5e
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x5d+0x1 at 0x7fe015786000
> domainbuilder: detail: start_info_x86_64: called
> domainbuilder: detail: setup_hypercall_page: vaddr=0x3000 pfn=0x3
> domainbuilder: detail: domain builder memory footprint
> domainbuilder: detail:    allocated
> domainbuilder: detail:       malloc             : 13384 bytes
> domainbuilder: detail:       anon mmap          : 0 bytes
> domainbuilder: detail:    mapped
> domainbuilder: detail:       file mmap          : 65 kB
> domainbuilder: detail:       domU mmap          : 396 kB
> domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 
> 0xb6c8e
> domainbuilder: detail: shared_info_x86_64: called
> domainbuilder: detail: vcpu_x86_64: called
> domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x60 mfn 0x130c60
> domainbuilder: detail: launch_vm: called, ctxt=0x7fe015787004
> domainbuilder: detail: xc_dom_release: called
> libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get domain 
> type for domid=2
> xl: unable to exec console client: No such file or directory
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console 
> child [3855] exited with error status 1
> ########################################################
>
> On Wed, Apr 4, 2018 at 9:01 AM, Ajay Garg <ajaygargnsit@xxxxxxxxx 
> <mailto:ajaygargnsit@xxxxxxxxx>> wrote:
>     Earnest request for help please.
>
>     I have even confirmed that hardware-virtualization is enabled in CPU
>     and BIOS.
>     Also, when booted into Xen, following is seen fine :
>
>     ########################################################
>     ajay@Latitude-3480:~$ cat /sys/hypervisor/properties/capabilities
>     xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
>     hvm-3.0-x86_64
>     ########################################################
>
>
>     However, running the hello-world app gives the same error :
>
>     ########################################################
>     root@Latitude-3480:/home/ajay/unikraft/apps/helloworld# xl create -c
>     helloworld.cfg
>     Parsing config from helloworld.cfg
>     libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get
>     domain type for domid=1
>     xl: unable to exec console client: No such file or directory
>     libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
>     console child [3004] exited with error status 1
>     ########################################################
>
>     On Tue, Apr 3, 2018 at 2:06 PM, Ajay Garg <ajaygargnsit@xxxxxxxxx
>     <mailto:ajaygargnsit@xxxxxxxxx>> wrote:
>
>         Help please ... unikraft seems to be the only option now to run
>         unikernels on ARM.
>         But before I reach there, I need to feel confident first on x86
>         (with unikraft).
>
>
>         Thanks and Regards,
>         Ajay
>
>
>
>
>     -- 
>     Regards,
>     Ajay
>
>
>
>
> --
> Regards,
> Ajay
>
>
> _______________________________________________
> Minios-devel mailing list
> Minios-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/minios-devel
_______________________________________________
Minios-devel mailing list
Minios-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/minios-devel