-muc.de:
Libvirt is trying to set security lables even for network shares. This
will not work. I think this is fixed in newer libvirt versions. For
older versions you can try this patch:
http://www.redhat.com/archives/libvir-list/2011-May/msg01446.html
Regards,
Christian
2012/2/4 Masuko
: 0.38-1maverick)
*apparmor is disable.
apparmor shouldn't matter if you have libvirt 0.9.9 or newer.
I use libvirt 0.8.3 (latest version for maverick), so I disabled apparmor.
2012/2/2 Josh Durgin josh.dur...@dreamhost.com:
On 02/02/2012 01:49 AM, Masuko Tomoya wrote:
Hi, all.
When I
12:51 AM, Masuko Tomoya wrote:
Hi Josh,
Thank you for reply !
This might mean the rbd image list object can't be read for some
reason, or the rbd tool is doing something weird that the rados tool
isn't. Can you share the output of 'ceph -s' and
'rbd ls --log-to-stderr --debug-ms 1 --debug
0 0 0 0 0 0 0 0
osdstat kbused kbavail kb hb in hb out
0 15681572603215727600[] []
sum15681572603215727600
2012/2/3 Josh Durgin josh.dur...@dreamhost.com:
On 02/03/2012 02:14 PM, Masuko Tomoya
...@dreamhost.com:
On 02/03/2012 02:54 PM, Masuko Tomoya wrote:
Hi,
The output of 'ceph pg dump' is below.
root@ceph01:~# ceph pg dump
2012-02-04 07:50:15.453151 mon- [pg,dump]
2012-02-04 07:50:15.453734 mon.0 - 'dumped all in format plain' (0)
version 63
last_osdmap_epoch 37
last_pg_scan 1
Hi, all.
I'm trying to attach rbd volume from instance on KVM.
But I have problem.
Could you help me ?
---
I tried to attach rbd volume on ceph01 to instance on compute1 with
virsh command.
root@compute1:~# virsh attach-device test-ub16 /root/testvolume.xml
error: Failed to attach device from
Hi, all.
I'm trying to attach rbd volume from instance on KVM.
But I have problem.
Could you help me ?
---
I tried to attach rbd volume on ceph01 to instance on compute1 with
virsh command.
root@compute1:~# virsh attach-device test-ub16 /root/testvolume.xml
error: Failed to attach device from
Hi, all.
When I execute rbd command, it is not success.
root@ceph01:~# rbd list
(no response)
/var/log/ceph/mon.0.log
-
2012-02-02 17:58:19.801762 7ff4bbfb1710 -- 10.68.119.191:6789/0 ==
client.? 10.68.119.191:0/1002580 1 auth(proto 0 30 bytes) v1
56+0+0 (625540289 0 0) 0x1619a00
