Re: [Xen-devel] Unable to create guest PV domain on OMAP5432

[Andrii Anisov <andrii_anisov@xxxxxxxx>]

Dear Jayadev,


Find my comments inlined:


On 15.11.17 08:08, Jayadev Kumaran wrote:
> Hello Andrii,
>
> >> BTW, what is your dom0 system? Does it have bash?
> > _dom0 uses a modified kernel(3.15) with Xen support and  default 
> omap fs_
> I made certain changes to my configuration file. Instead of trying to 
> use a disk, I want to the guest domain up from ramdisk image.
Its quite wise idea to sort out problems.

> My new configuration file looks like
>
> "
> name = "android"
>
> kernel = "/home/root/android/kernel"
> ramdisk = "/home/root/android/ramdisk.img"
> #bootloader = "/usr/lib/xen-4.4/bin/pygrub"
>
> memory = 512
> vcpus = 1
>
> device_model_version = 'qemu-xen-traditional'
>
> extra = "console=hvc0 rw init=/bin/sh earlyprintk=xenboot"
>
> "
>
> I'm able to create a guest domain as well.
>
> /root@omap5-evm:~# xl -vvv create android.cfg
> Parsing config from android.cfg
> libxl: debug: libxl_create.c:1646:do_domain_create: Domain 0:ao 
> 0x46e30: create: how=(nil) callback=(nil) poller=0x46e90
> libxl: debug: libxl_arm.c:87:libxl__arch_domain_prepare_config: 
> Configure the domain
> libxl: debug: libxl_arm.c:90:libxl__arch_domain_prepare_config:  - 
> Allocate 0 SPIs
> libxl: debug: libxl_create.c:987:initiate_domain_create: Domain 
> 1:running bootloader
> libxl: debug: libxl_bootloader.c:335:libxl__bootloader_run: Domain 
> 1:no bootloader configured, using user supplied kernel
> libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch 
> w=0x47780: deregister unregistered
> (XEN) grant_table.c:1688:d0v0 Expanding d1 grant table from 0 to 1 frames
> domainbuilder: detail: xc_dom_allocate: cmdline="console=hvc0 rw 
> init=/bin/sh earlyprintk=xenboot", features=""
> libxl: debug: libxl_dom.c:779:libxl__build_pv: pv kernel mapped 0 path 
> /home/root/android/kernel
> domainbuilder: detail: xc_dom_kernel_file: 
> filename="/home/root/android/kernel"
> domainbuilder: detail: xc_dom_malloc_filemap    : 4782 kB
> domainbuilder: detail: xc_dom_ramdisk_file: 
> filename="/home/root/android/ramdisk.img"
> domainbuilder: detail: xc_dom_malloc_filemap    : 179 kB
> domainbuilder: detail: xc_dom_boot_xen_init: ver 4.10, caps 
> 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: 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: 
> 0x40008000 -> 0x404b3b28
> libxl: debug: libxl_arm.c:866:libxl__prepare_dtb: constructing DTB for 
> Xen version 4.10 guest
> libxl: debug: libxl_arm.c:867:libxl__prepare_dtb:  - vGIC version: V2
> libxl: debug: libxl_arm.c:321:make_chosen_node: /chosen/bootargs = 
> console=hvc0 rw init=/bin/sh earlyprintk=xenboot
> libxl: debug: libxl_arm.c:328:make_chosen_node: /chosen adding 
> placeholder linux,initrd properties
> libxl: debug: libxl_arm.c:441:make_memory_nodes: Creating placeholder 
> node /memory@40000000
> libxl: debug: libxl_arm.c:441:make_memory_nodes: Creating placeholder 
> node /memory@200000000
> libxl: debug: libxl_arm.c:964:libxl__prepare_dtb: fdt total size 1394
> domainbuilder: detail: xc_dom_devicetree_mem: called
> libxl: debug: libxl_arm.c:1005:libxl__arch_domain_init_hw_description: 
> Generating ACPI tables is disabled by user.
> 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
> domainbuilder: detail: populate_guest_memory: populating RAM @ 
> 0000000040000000-0000000060000000 (512MB)
> domainbuilder: detail: populate_one_size: populated 0x100/0x100 
> entries with shift 9
> domainbuilder: detail: meminit: placing boot modules at 0x48000000
> domainbuilder: detail: meminit: ramdisk: 0x48000000 -> 0x4802d000
> domainbuilder: detail: meminit: devicetree: 0x4802d000 -> 0x4802e000
> libxl: debug: 
> libxl_arm.c:1073:libxl__arch_domain_finalise_hw_description: /chosen 
> updating initrd properties to cover 48000000-4802d000
> libxl: debug: libxl_arm.c:1039:finalise_one_node: Populating 
> placeholder node /memory@40000000
> libxl: debug: libxl_arm.c:1033:finalise_one_node: Nopping out 
> placeholder node /memory@200000000
> domainbuilder: detail: xc_dom_build_image: called
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x40008+0x4ac at 0xb6098000
> domainbuilder: detail: xc_dom_alloc_segment:   kernel : 0x40008000 -> 
> 0x404b4000  (pfn 0x40008 + 0x4ac pages)
> domainbuilder: detail: xc_dom_load_zimage_kernel: called
> domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 
> 0x40008000-0x404b4000
> domainbuilder: detail: xc_dom_load_zimage_kernel: copy 4897576 bytes 
> from blob 0xb6672000 to dst 0xb6098000
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x48000+0x2d at 0xb606b000
> domainbuilder: detail: xc_dom_alloc_segment:   ramdisk : 0x48000000 -> 
> 0x4802d000  (pfn 0x48000 + 0x2d pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
> 0x4802d+0x1 at 0xb6f63000
> domainbuilder: detail: xc_dom_alloc_segment:   devicetree : 0x4802d000 
> -> 0x4802e000  (pfn 0x4802d + 0x1 pages)
> domainbuilder: detail: alloc_magic_pages: called
> domainbuilder: detail: alloc_pgtables_arm: called
> domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x4802e000
> domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x0
> domainbuilder: detail: xc_dom_boot_image: called
> domainbuilder: detail: bootearly: doing nothing
> domainbuilder: detail: xc_dom_compat_check: supported guest type: 
> xen-3.0-armv7l <= matches
> domainbuilder: detail: setup_pgtables_arm: called
> domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000
> domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001
> domainbuilder: detail: clear_page: pfn 0x39003, mfn 0x39003
> domainbuilder: detail: start_info_arm: called
> domainbuilder: detail: domain builder memory footprint
> domainbuilder: detail:    allocated
> domainbuilder: detail:       malloc             : 1055 kB
> domainbuilder: detail:       anon mmap          : 0 bytes
> domainbuilder: detail:    mapped
> domainbuilder: detail:       file mmap          : 4962 kB
> domainbuilder: detail:       domU mmap          : 4968 kB
> domainbuilder: detail: vcpu_arm32: called
> domainbuilder: detail: Initial state CPSR 0x1d3 PC 0x40008000
> domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000
> domainbuilder: detail: xc_dom_release: called
> libxl: debug: libxl_event.c:2184:libxl__ao_progress_report: ao 
> 0x46e30: progress report: ignored
> libxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x46e30: 
> complete, rc=0
> libxl: debug: libxl_create.c:1683:do_domain_create: Domain 0:ao 
> 0x46e30: inprogress: poller=0x46e90, flags=ic
> libxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x46e30: destroy
> xl: fatal error: xl_utils.c:273: No such file or directory: logfile = 
> open(fullname, O_WRONLY|O_CREAT|O_APPEND, 0644)(XEN) traps.c:2081:d1v0 HS
> R=0x90000045 pc=0x40008298 gva=0x80004000 gpa=0x00000080004000
>
> xencall:buffer: debug: total allocations:0 total releases:0
> xencall:buffer: debug: current allocations:0 maximum allocations:0
> xencall:buffer: debug: cache current size:0
> xencall:buffer: debug: cache hits:0 misses:0 toobig:0
> xencall:buffer: debug: total allocations:0 total releases:0
> xencall:buffer: debug: current allocations:0 maximum allocations:0
> xencall:buffer: debug: cache current size:0
> xencall:buffer: debug: cache hits:0 misses:0 toobig:0
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: domain 
> monitoring daemonizing child [1427] exited with error status 1
> xencall:buffer: debug: total allocations:109 total releases:109
> xencall:buffer: debug: current allocations:0 maximum allocations:3
> xencall:buffer: debug: cache current size:3
> xencall:buffer: debug: cache hits:94 misses:3 toobig:12
> xencall:buffer: debug: total allocations:0 total releases:0
> xencall:buffer: debug: current allocations:0 maximum allocations:0
> xencall:buffer: debug: cache current size:0
> xencall:buffer: debug: cache hits:0 misses:0 toobig:0
>
> root@omap5-evm:~# xl list
> Name                                        ID   Mem VCPUs      
> State   Time(s)
> Domain-0                                     0   512 2     r-----      
> 12.7
> android                                      1   512 1     
> r-----       6.8/
> However I'm not able to access the guest console. '/xl console 
> android/' shows nothing, but using 'Ctrl + 5' or 'Ctrl + ]' closes the 
> console. Am I missing something here?
What kernel do you use for DomU? Please make sure you have in that 
kernel configuration XEN support enabled (together with hypervisor 
console support).

--

*Andrii Anisov*



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