I know this is dirty, but...
removing /usr/lib/libvirt/connection-driver/libvirt_driver_libxl.so and
/usr/lib/libvirt/connection-driver/libvirt_driver_xen.so makes libvirt-
bin launch on the Rackspace public cloud.
A strace of the libvirt-bin process shows it opening /proc/xen/xenbus
and then trying to get the xen properties
892 open("/proc/xen/privcmd", O_RDWR) = 22
4892 fcntl(22, F_GETFD) = 0
4892 fcntl(22, F_SETFD, FD_CLOEXEC) = 0
4892 stat("/var/run/xenstored/socket", 0x7f509c32e6e0) = -1 ENOENT (No such
file or directory)
4892 stat("/proc/xen/xenbus", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
4892 open("/proc/xen/xenbus", O_RDWR) = 23
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 262145
4892 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_LOCKED, -1, 0) = 0x7f50ac5d4000
4892 madvise(0x7f50ac5d4000, 4096, 0xa /* MADV_??? */) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 4096
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e3c0) = 0
4892 ioctl(22, SNDCTL_DSP_RESET, 0x7f509c32e250) = -1 EPERM (Operation not
permitted)
4892 write(19, "libxl: error: libxl.c:3938:libxl_get_physinfo: getting
physinfo: Operation not permitted\n", 89) = 89
4892 gettid() = 4892
4892 clock_gettime(CLOCK_REALTIME, {1394225065, 392717879}) = 0
4892 write(4, "2014-03-07 20:44:25.392+0000: 4892: error :
libxlMakeCapabilities:786 : internal error: Failed to get node physical info
from libxenlight\n", 138) = 138
4892 gettid() = 4892
4892 clock_gettime(CLOCK_REALTIME, {1394225065, 392879907}) = 0
4892 write(4, "2014-03-07 20:44:25.392+0000: 4892: error :
libxlStateInitialize:1320 : cannot create capabilities for libxenlight\n", 115)
= 115
4892 gettid() = 4892
4892 clock_gettime(CLOCK_REALTIME, {1394225065, 393023723}) = 0
4892 gettid() = 4892
4892 clock_gettime(CLOCK_REALTIME, {1394225065, 393108049}) = 0
4892 write(19, "xc: debug: hypercall buffer: total allocations:7 total
releases:7\n", 66) = 66
4892 write(19, "xc: debug: hypercall buffer: current allocations:0 maximum
allocations:1\n", 73) = 73
4892 write(19, "xc: debug: hypercall buffer: cache current size:1\n", 50) = 50
4892 write(19, "xc: debug: hypercall buffer: cache hits:6 misses:1
toobig:0\n", 60) = 60
4892 madvise(0x7f50ac5d4000, 4096, 0xb /* MADV_??? */) = 0
4892 munmap(0x7f50ac5d4000, 4096) = 0
There is obviously a problem in the 1.1.1 version of libvirt-bin in
cloud-archive here - but I don't know where to look yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin fails to start inside Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1248025/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
