Hi Andrew. Thanks for the reply.
On Sat, Apr 28, 2018 at 10:57 PM, Andrew Cooper <andrew.coop...@citrix.com> 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. Thanks and Regards, Ajay
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
