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. 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.cfglibxl: debug: libxl_create.c:1646:do_domain_create: Domain 0:ao 0x46e30: create: how=(nil) callback=(nil) poller=0x46e90libxl: debug: libxl_arm.c:87:libxl__arch_domain_prepare_config: Configure the domainlibxl: debug: libxl_arm.c:90:libxl__arch_domain_prepare_config: - Allocate 0 SPIslibxl: debug: libxl_create.c:987:initiate_domain_create: Domain 1:running bootloaderlibxl: debug: libxl_bootloader.c:335:libxl__bootloader_run: Domain 1:no bootloader configured, using user supplied kernellibxl: 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 framesdomainbuilder: 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/kerneldomainbuilder: detail: xc_dom_kernel_file: filename="/home/root/android/kernel"domainbuilder: detail: xc_dom_malloc_filemap : 4782 kBdomainbuilder: detail: xc_dom_ramdisk_file: filename="/home/root/android/ramdisk.img"domainbuilder: detail: xc_dom_malloc_filemap : 179 kBdomainbuilder: detail: xc_dom_boot_xen_init: ver 4.10, caps xen-3.0-armv7l domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000domainbuilder: detail: xc_dom_parse_image: calleddomainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe faileddomainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM64) loader ... domainbuilder: detail: xc_dom_probe_zimage64_kernel: kernel is not an arm64 Imagedomainbuilder: detail: loader probe faileddomainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM32) loader ... domainbuilder: detail: loader probe OKdomainbuilder: detail: xc_dom_parse_zimage32_kernel: calleddomainbuilder: detail: xc_dom_parse_zimage32_kernel: xen-3.0-armv7l: 0x40008000 -> 0x404b3b28libxl: debug: libxl_arm.c:866:libxl__prepare_dtb: constructing DTB for Xen version 4.10 guestlibxl: debug: libxl_arm.c:867:libxl__prepare_dtb: - vGIC version: V2libxl: debug: libxl_arm.c:321:make_chosen_node: /chosen/bootargs = console=hvc0 rw init=/bin/sh earlyprintk=xenbootlibxl: debug: libxl_arm.c:328:make_chosen_node: /chosen adding placeholder linux,initrd propertieslibxl: debug: libxl_arm.c:441:make_memory_nodes: Creating placeholder node /memory@40000000libxl: debug: libxl_arm.c:441:make_memory_nodes: Creating placeholder node /memory@200000000libxl: debug: libxl_arm.c:964:libxl__prepare_dtb: fdt total size 1394domainbuilder: detail: xc_dom_devicetree_mem: calledlibxl: 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 eachdomainbuilder: detail: xc_dom_mem_init: 0x20000 pagesdomainbuilder: detail: xc_dom_boot_mem_init: calleddomainbuilder: detail: set_mode: guest xen-3.0-armv7l, address size 32domainbuilder: detail: xc_dom_malloc : 1024 kBdomainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040000000-0000000060000000 (512MB)domainbuilder: detail: populate_one_size: populated 0x100/0x100 entries with shift 9domainbuilder: detail: meminit: placing boot modules at 0x48000000domainbuilder: detail: meminit: ramdisk: 0x48000000 -> 0x4802d000domainbuilder: detail: meminit: devicetree: 0x4802d000 -> 0x4802e000libxl: debug: libxl_arm.c:1073:libxl__arch_domain_finalise_hw_description: /chosen updating initrd properties to cover 48000000-4802d000libxl: debug: libxl_arm.c:1039:finalise_one_node: Populating placeholder node /memory@40000000libxl: debug: libxl_arm.c:1033:finalise_one_node: Nopping out placeholder node /memory@200000000domainbuilder: detail: xc_dom_build_image: calleddomainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40008+0x4ac at 0xb6098000domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x40008000 -> 0x404b4000 (pfn 0x40008 + 0x4ac pages)domainbuilder: detail: xc_dom_load_zimage_kernel: calleddomainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40008000-0x404b4000domainbuilder: detail: xc_dom_load_zimage_kernel: copy 4897576 bytes from blob 0xb6672000 to dst 0xb6098000domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x48000+0x2d at 0xb606b000domainbuilder: 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 0xb6f63000domainbuilder: detail: xc_dom_alloc_segment: devicetree : 0x4802d000 -> 0x4802e000 (pfn 0x4802d + 0x1 pages)domainbuilder: detail: alloc_magic_pages: calleddomainbuilder: detail: alloc_pgtables_arm: calleddomainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x4802e000domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0domainbuilder: detail: xc_dom_boot_image: calleddomainbuilder: detail: bootearly: doing nothingdomainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-armv7l <= matchesdomainbuilder: detail: setup_pgtables_arm: calleddomainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001domainbuilder: detail: clear_page: pfn 0x39003, mfn 0x39003domainbuilder: detail: start_info_arm: calleddomainbuilder: detail: domain builder memory footprintdomainbuilder: detail: allocateddomainbuilder: detail: malloc : 1055 kBdomainbuilder: detail: anon mmap : 0 bytesdomainbuilder: detail: mappeddomainbuilder: detail: file mmap : 4962 kBdomainbuilder: detail: domU mmap : 4968 kBdomainbuilder: detail: vcpu_arm32: calleddomainbuilder: detail: Initial state CPSR 0x1d3 PC 0x40008000domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000domainbuilder: detail: xc_dom_release: calledlibxl: debug: libxl_event.c:2184:libxl__ao_progress_report: ao 0x46e30: progress report: ignoredlibxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x46e30: complete, rc=0libxl: debug: libxl_create.c:1683:do_domain_create: Domain 0:ao 0x46e30: inprogress: poller=0x46e90, flags=iclibxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x46e30: destroyxl: 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 HSR=0x90000045 pc=0x40008298 gva=0x80004000 gpa=0x00000080004000xencall:buffer: debug: total allocations:0 total releases:0xencall:buffer: debug: current allocations:0 maximum allocations:0xencall:buffer: debug: cache current size:0xencall:buffer: debug: cache hits:0 misses:0 toobig:0xencall:buffer: debug: total allocations:0 total releases:0xencall:buffer: debug: current allocations:0 maximum allocations:0xencall:buffer: debug: cache current size:0xencall:buffer: debug: cache hits:0 misses:0 toobig:0libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: domain monitoring daemonizing child [1427] exited with error status 1xencall:buffer: debug: total allocations:109 total releases:109xencall:buffer: debug: current allocations:0 maximum allocations:3xencall:buffer: debug: cache current size:3xencall:buffer: debug: cache hits:94 misses:3 toobig:12xencall:buffer: debug: total allocations:0 total releases:0xencall:buffer: debug: current allocations:0 maximum allocations:0xencall:buffer: debug: cache current size:0xencall:buffer: debug: cache hits:0 misses:0 toobig:0root@omap5-evm:~# xl listName ID Mem VCPUs State Time(s)Domain-0 0 512 2 r----- 12.7android 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? On Thu, Nov 9, 2017 at 8:22 PM, Andrii Anisov <andrii_ani...@epam.com> wrote: > Hello Jayadev, > > Please see my comments inlined: > > > On 08.11.17 07:17, Jayadev Kumaran wrote: > >> Hello all, >> >> I'm trying to implement Xen hypervisor support on OMAP5432.I have >> followed the steps as in https://wiki.xenproject.org/wi >> ki/Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM for the initial >> setup. I'm able to see the domain 0 successfully up. >> >> /root@omap5-evm:~# /etc/init.d/xencommons start >> Starting /usr/local/sbin/xenstored... >> Setting domain 0 name, domid and JSON config... >> Done setting up Dom0 >> Starting xenconsoled... >> Starting QEMU as disk backend for dom0 >> / >> > Never used QEMU as disk backend on ARM. We are using raw partition for a > disk. > >> >> /root@omap5-evm:~# xl list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 512 2 r----- >> 11.5 >> / >> I have used the below configuration file for creating a guest domain. >> " >> name = "ubuntu" >> >> kernel = "/home/root/ubuntu/vmlinuz" >> ramdisk = "/home/root/ubuntu/initrd.gz" >> #bootloader = "/usr/lib/xen-4.4/bin/pygrub" >> >> memory = 1024 >> vcpus = 1 >> >> device_model_version = 'qemu-xen-traditional' >> > I would suggest to run the stuff without this line. > >> >> disk = [ >> '/dev/vg0/domu0,raw,xvda,rw' >> > Do you really have "/dev/vg0/domu0" in your dom0? > >> ] >> >> " >> >> But when I try to create the guest domain using xl create command,I get >> the below error. >> >> /root@omap5-evm:/# xl create -d -c /etc/xen/config.d/ubuntu.cfg/ >> > Please try adding ` xl -vvvv create -d -c /etc/xen/config.d/ubuntu.cfg` > for getting more output./ > / > >> / >> >> Parsing config from /etc/xen/config.d/ubuntu.cfg >> { >> "c_info": { >> "type": "pv", >> "name": "ubuntu", >> "uuid": "d7dd7835-61e3-46ce-b76f-140c0f9673fe", >> "run_hotplug_scripts": "True" >> }, >> "b_info": { >> "max_vcpus": 1, >> "avail_vcpus": [ >> 0 >> ], >> "max_memkb": 1048576, >> "target_memkb": 1048576, >> "shadow_memkb": 9216, >> "device_model_version": "qemu_xen_traditional", >> "sched_params": { >> >> }, >> "claim_mode": "True", >> "kernel": "/home/root/ubuntu/vmlinuz", >> "ramdisk": "/home/root/ubuntu/initrd.gz", >> "type.pv": { >> >> }, >> "arch_arm": { >> >> } >> }, >> "disks": [ >> { >> "pdev_path": "/dev/vg0/domu0", >> "vdev": "xvda", >> "format": "raw", >> "readwrite": 1 >> } >> ], >> "on_reboot": "restart", >> "on_soft_reset": "soft_reset" >> } >> (XEN) grant_table.c:1688:d0v0 Expanding d4 grant table from 0 to 1 frames >> (XEN) memory.c:238:d0v0 Could not allocate order=18 extent: id=4 >> memflags=0xc0 (0 of 1) >> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: >> /etc/xen/scripts/block add [1612] exited with error status 1 >> libxl: error: libxl_create.c:1278:domcreate_launch_dm: Domain 4:unable >> to add disk devices >> libxl: error: libxl_domain.c:1000:libxl__destroy_domid: Domain >> 4:Non-existant domain >> libxl: error: libxl_domain.c:959:domain_destroy_callback: Domain >> 4:Unable to destroy guest >> libxl: error: libxl_domain.c:886:domain_destroy_cb: Domain 4:Destruction >> of domain failed >> / >> Any input would be highly appreciated >> > > BTW, what is your dom0 system? Does it have bash? > Long time ago, we had busybox in dom0, and used > https://marc.info/?l=xen-devel&m=146358920813936&w=4 to workaround block > device creation issues. > > -- > > *Andrii Anisov* > > >
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
