[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] libxl get_physinfo failure: Permission denied



Hi,

I installed Xen 4.5 source on top of Ubuntu, using "make world" and "make install" targets. I then installed virt-manager. After bringing up virt-manager I attempt to connect to Xen hypervisor and got:

ÂÂÂÂ unable to connect to libvirt
ÂÂÂÂ Failed to connect socket to /var/run/libvirt/libvirt-sock' No such file or directory

I then noticed libvirt-bin isn't running, so I think that is my problem.Â

If I try to issue 'service libvirt-bin start' it gives me back a process number, but it must die quickly because the service is still down. Three log files are touched during my start attempt:

 -rw-r--r-- 1 root root 39757 Feb 27 06:00 /var/log/xenstored-access.log
 -rw-r--r-- 1 root root 44908 Feb 27 06:00 /var/log/libvirt/libxl/libxl-driver.log
 -rw------- 1 root root 46396 Feb 27 06:00 /var/log/libvirt/libvirtd.log

* xenstored-access.log has 22 new entries, grouped into pairs that increment an "Axx" identifier and go from A63 to A73. Here is the A63 logs:

ÂÂÂÂ [20150227T11:00:29.478Z]Â A63ÂÂÂÂÂÂÂÂÂ newconn
ÂÂÂÂ [20150227T11:00:29.479Z]Â A63ÂÂÂÂÂÂÂÂÂ endconn

* libxl-driver.log also has 11 log groupings that are just the same set of logs repeated 11 times. Here is the first group:

ÂÂÂÂ xc: detail: sysctl operation failed -- need to rebuild the user-space tool set?
ÂÂÂÂ libxl: error: libxl.c:4320:libxl_get_physinfo: getting physinfo: Permission denied
ÂÂÂÂ xc: debug: hypercall buffer: total allocations:7 total releases:7
ÂÂÂÂ xc: debug: hypercall buffer: current allocations:0 maximum allocations:1
ÂÂÂÂ xc: debug: hypercall buffer: cache current size:1
ÂÂÂÂ xc: debug: hypercall buffer: cache hits:6 misses:1 toobig:0

* libvirtd.log also has 11 log groupings, that are just the same set of logs repeated 11 times. Here is that group:

ÂÂÂÂ 2015-02-27 11:00:29.479+0000: 4842: info : libvirt version: 1.2.2
ÂÂÂÂ 2015-02-27 11:00:29.479+0000: 4842: error : libxlDriverConfigNew:1131 : Unable to configure libxl's memory management parameters
ÂÂÂÂ 2015-02-27 11:00:29.479+0000: 4842: error : virStateInitialize:749 : Initialization of LIBXL state driver failed: Unknown problem
ÂÂÂÂ 2015-02-27 11:00:29.479+0000: 4842: error : daemonRunStateInit:920 : Driver state initialization failed

When I google for libxl_get_physinfo I see other reported errors during "xl info" and other "xl" commands. ÂÂ I tried "xl info" and that works for me and does not alter the log files:

root@<server>:~# xl info
hostÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : server
releaseÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : 3.13.0-46-generic
versionÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : #75-Ubuntu SMP Tue Feb 10 15:24:04 UTC 2015
machineÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : x86_64
nr_cpusÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : 8
max_cpu_idÂÂÂÂÂÂÂÂÂÂÂÂ : 7
nr_nodesÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : 2
cores_per_socketÂÂÂÂÂÂ : 4
threads_per_coreÂÂÂÂÂÂ : 1
cpu_mhzÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : 2400
hw_capsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : bfebfbff:2c100800:00000000:00003f00:17bee3ff:00000000:00000001:00000000
virt_capsÂÂÂÂÂÂÂÂÂÂÂÂÂ : hvm hvm_directio
total_memoryÂÂÂÂÂÂÂÂÂÂ : 98168
free_memoryÂÂÂÂÂÂÂÂÂÂÂ : 128
sharing_freed_memoryÂÂ : 0
sharing_used_memoryÂÂÂ : 0
outstanding_claimsÂÂÂÂ : 0
free_cpusÂÂÂÂÂÂÂÂÂÂÂÂÂ : 0
xen_majorÂÂÂÂÂÂÂÂÂÂÂÂÂ : 4
xen_minorÂÂÂÂÂÂÂÂÂÂÂÂÂ : 5
xen_extraÂÂÂÂÂÂÂÂÂÂÂÂÂ : .0
xen_versionÂÂÂÂÂÂÂÂÂÂÂ : 4.5.0
xen_capsÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_schedulerÂÂÂÂÂÂÂÂÂ : credit
xen_pagesizeÂÂÂÂÂÂÂÂÂÂ : 4096
platform_paramsÂÂÂÂÂÂÂ : virt_start=0xffff800000000000
xen_changesetÂÂÂÂÂÂÂÂÂ : Mon Jan 12 11:30:05 2015 -0500 git:a8ac229
xen_commandlineÂÂÂÂÂÂÂ : placeholder
cc_compilerÂÂÂÂÂÂÂÂÂÂÂ : gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
cc_compile_byÂÂÂÂÂÂÂÂÂ : root
cc_compile_domainÂÂÂÂÂ : cisco.com
cc_compile_dateÂÂÂÂÂÂÂ : Thu Feb 19 07:26:00 EST 2015
xend_config_formatÂÂÂÂ : 4
root@<server>:~#

Any idea what could be causing my issues?

Thanks,
Wayne

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.