Re: [Libvir] virsh - vcpuinfo cmd not working in 0.2.2
Hi Richard,
On 14.05.2007, at 18:00, Richard W.M. Jones wrote:
Jan Michael wrote:
32266 stat64("/var/run/xenstored/socket", {st_mode=S_IFSOCK|
0600,st_size=0, ...}) = 0
32266 socket(PF_FILE, SOCK_STREAM, 0) = 4
32266 fcntl64(4, F_GETFD) = 0
32266 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
32266 connect(4, {sa_family=AF_FILE, path="/var/run/xenstored/
socket"},110) = 0
32266 write(2, "libvir: error : no support for h"..., 42) = 42
It looks like the last thing it does is to connect to xenstored
(successfully) then fails.
Did you get any further on this? I would be tempted to try libvirt
from CVS.
No, not with virsh in libvirt 0.2.1. As you suggested I tried the
latest libvirt from CVS. I configured it with:
./autogen.sh --disable-bridge-params --with-test=no --with-qemu=no
Because otherwise it won't compile on my installation.
Virsh then can be successfully run from the libvirt/src directory. It
reports me the following:
<virsh version>
virsh # version
Compiled against library: libvir 0.2.2
Using library: libvir 0.2.2
Using API: Xen 3.0.1
Running hypervisor: Xen 3.0.0
</virsh version>
But it still has a broken vcpuinfo command:
<virsh vcpuinfo>
virsh # vcpuinfo 0
VCPU: 0
CPU: 0
State: blocked
CPU time: 0.0s
CPU Affinity: --
</virsh vcpuinfo>
I have no problem with that so far, since I can use libvirt 0.2.1 in
my own programs without restriction of any kind. I use virsh very
rarely for some testing purposes.
Cheers,
Jan