I changed the /chosen node in the dts file to
#######################################
chosen {
stdout-path = "serial0:115200n8";
xen,xen-bootargs = "dom0_mem=752M console=dtuart dtuart=serial0
dom0_max_vcpus=4";
xen,dom0-bootargs = "console=ttyS0,115200 rw root=/dev/mmcblk0p2
ignore_loglevel cma=128M";
modules {
#address-cells = <2>;
#size-cells = <2>;
module@1 {
compatible = "xen,linux-zimage", "xen,multiboot-module";
reg = <0x0 0x7a000000 0x0 0x02000000>;
};
};
};
#######################################
Also, the xen-related features in the kernel are as follows (created by
default after selecting "Kernel features => Xen guest support on ARM" in
menuconfig) :
#######################################
CONFIG_XEN_DOM0=y
CONFIG_XEN=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
CONFIG_HVC_XEN_FRONTEND=y
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=m
CONFIG_XEN_GRANT_DEV_ALLOC=m
CONFIG_SWIOTLB_XEN=y
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_AUTO_XLATE=y
# CONFIG_XEN_BLKDEV_BACKEND is not set
# CONFIG_XEN_SCSI_FRONTEND is not set
# CONFIG_XEN_NETDEV_BACKEND is not set
# CONFIG_XEN_WDT is not set
# CONFIG_XEN_PVCALLS_FRONTEND is not set
# CONFIG_XEN_PVCALLS_BACKEND is not set
#######################################
However, I see absolutely no change in the observations; no xen-related log
on the serial-console, and "sudo xl list" gives the same error messages.
What am I lacking?
On Sat, Apr 28, 2018 at 11:06 PM, Andrew Cooper <[email protected]>
wrote:
> On 28/04/18 18:34, Ajay Garg wrote:
>
> Hi Andrew.
>
> Thanks for the reply.
>
> On Sat, Apr 28, 2018 at 10:57 PM, Andrew Cooper <[email protected]
> > wrote:
>
>> On 28/04/18 18:12, Ajay Garg wrote:
>>
>> Hi All.
>>
>> We have brought up the cubieboard2 from almost scratch, following are the
>> steps done :
>>
>> <snip>
>>
>> == getting xen ready ==
>>
>> i)
>> Compiled xen on cubieboard itself, via :
>>
>> * git clone git://xenbits.xen.org/xen.git
>> * cd xen
>> . * ./configure --libdir=/usr/lib
>> * make debball CONFIG_EARLY_PRINTK=sun7i -j4
>> * sudo dpkg -i dist/xen-upstream-4.11-unstable.deb
>> * sudo reboot
>>
>> ii)
>> Upon reboot, "sudo xl list" gives following :
>>
>> ##################################################################
>> debian@debian-armhf:~$ sudo xl list
>> [sudo] password for debian:
>> xencall: error: Could not obtain handle on privileged command interface:
>> No such file or directory
>> libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle: No
>> such file or directory
>> cannot init xl context
>> ##################################################################
>>
>>
>> This means that /dev/xen/privcmd (or the legacy /proc/xen/privcmd) device
>> isn't available.
>>
>> First check that you have actually booted Xen with Linux as dom0. You
>> don't show any logs in this final section, and simply installing the
>> debball and rebooting won't typically cause Xen to be the head of the boot
>> list.
>>
>
> Yes, I haven't been able to setup xen bootup.
>
> That's why, requested help regarding the changes that are required in
> https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/sun7i-a20-
> cubieboard2.dts, that would cause dom0 to boot up.
>
>
> Sorry for the confusion.
>
>
> Ah - sorry. I misunderstood. I'm afraid you're going to have to wait for
> some people more knowledge about ARM to answer.
>
> ~Andrew
>
--
Regards,
Ajay
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
