Hello Konrad, >> What does 'xl info' say? B/c:
xl info gives the below output *root@omap5-evm:~# xl infohost : omap5-evmrelease : 3.15.0-dirtyversion : #18 SMP Fri Nov 3 14:33:50 IST 2017machine : armv7lnr_cpus : 2max_cpu_id : 1nr_nodes : 1cores_per_socket : 1threads_per_core : 1cpu_mhz : 6hw_caps : 00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000virt_caps :total_memory : 2032free_memory : 1439sharing_freed_memory : 0sharing_used_memory : 0outstanding_claims : 0free_cpus : 0xen_major : 4xen_minor : 10xen_extra : .0-rcxen_version : 4.10.0-rcxen_caps : xen-3.0-armv7l xen_scheduler : creditxen_pagesize : 4096platform_params : virt_start=0x200000xen_changeset : Mon Oct 16 15:14:16 2017 +0100 git:24fb44e-dirtyxen_commandline : sync_console console=dtuart dtuart=serial2cc_compiler : arm-linux-gnueabihf-gcc (crosstool-NG linaro-1.13.1-4.7-2013.03cc_compile_by : ritikacc_compile_domain : cc_compile_date : Fri Oct 27 11:39:32 IST 2017build_id : ed71e48dc494388691dac13664932a8f5ed3ee45xend_config_format : 4* >> not allocate order=18 extent: id=4 memflags=0xc0 (0 of 1)libxl: error: > looks like it could not allocate memory? On Wed, Nov 8, 2017 at 8:22 PM, Konrad Rzeszutek Wilk < konrad.w...@oracle.com> wrote: > On Wed, Nov 08, 2017 at 10:47:20AM +0530, 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/wiki/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 startStarting > > /usr/local/sbin/xenstored...Setting domain 0 name, domid and JSON > > config...Done setting up Dom0Starting xenconsoled...Starting QEMU as disk > > backend for dom0* > > > > > > > > *root@omap5-evm:~# xl listName ID > > Mem VCPUs State Time(s)Domain-0 > > 0 512 2 r----- 11.5* > > What does 'xl info' say? B/c: > .. > > 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: > > .. looks like it could not allocate memory? >
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
