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 > <http://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. Beyond that, double check your Linux kernel configuration options when it comes to Xen support. ~Andrew
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
