Hm, ok. Looks like the patch mentioned above was in v0.9.0 already, so
at least that would be in 1.1.1 already in the Saucy version.

Unfortunately trying to reproduce locally is not working. The effect is
just as I would expect it. In the libxl specific log I get:

xc: error: Could not obtain handle on privileged command interface (2 = No such 
file or directory): Internal error
libxl: error: libxl.c:87:libxl_ctx_alloc: cannot open libxc handle: No such 
file or directory

which sounds reasonable as a normal guest won't have the control file
under /proc/xen. This looks to be enough to make libvirt not to try any
capabilities and my libvirt.log looks just as:

2014-03-04 17:44:15.814+0000: 1126: info : libvirt version: 1.1.1
2014-03-04 17:44:15.814+0000: 1126: error : virExec:418 : Cannot find 
'usr/lib/xen-common/bin/xen-toolstack' in path: No such file or directory
2014-03-04 17:44:15.952+0000: 1126: error : virExec:418 : Cannot find 
'pm-is-supported' in path: No such file or directory
2014-03-04 17:44:15.952+0000: 1126: warning : virQEMUCapsInit:896 : Failed to 
get host power management capabilities
2014-03-04 17:44:18.612+0000: 1126: error : virExec:418 : Cannot find 
'pm-is-supported' in path: No such file or directory
2014-03-04 17:44:18.612+0000: 1126: warning : virLXCDriverCapsInit:82 : Failed 
to get host power management capabilities
2014-03-04 17:44:18.613+0000: 1126: error : virExec:418 : Cannot find 
'pm-is-supported' in path: No such file or directory
2014-03-04 17:44:18.613+0000: 1126: warning : umlCapsInit:72 : Failed to get 
host power management capabilities

The virQEMUCapsInit fails too, but it does not prevent the daemon from
running. I am wondering what is different in your guest.

-- 
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

Reply via email to