On Mon, Aug 29, 2016 at 06:33:28PM +0000, Deneau, Tom wrote: > I notice on both clusters the qemu process running is > /usr/libexec/qemu-kvm (this is RHEL 7.2) and the > euser,fgroup,ruser,uname printed by ps are all user qemu. > (note: I am initiating the VM thru virsh define xyz.xml followed by > virsh start, and the user initiating both those virsh commands is > root). So I advise to look at ps output for exact qemu command line and compare this with the working environments. If they are the same, try to run this manually from command line (instead of virsh) to see if there is useful output (under qemu user and root). If you don't see the qemu process on the non-working environment (because it terminated with failure), try to run here the command from the working env. > On both clusters /etc/ceph/ceph.conf is 644 access. > > On both clusters, I get > ldd /usr/libexec/qemu-kvm | grep rbd > librbd.so.1 => /lib64/librbd.so.1 (0x00007fbdf1071000) > > > When I try > rbd --id admin export <image-spec> - | md5sum > I get the same md5sum values on both clusters. > > If I use --id qemu instead, I get > rbd: couldn't connect to the cluster > on both clusters. Why did you try 'qemu' id? I doubt qemu sets it this way. > > If I leave off the --id option entirely, it works on both clusters and I get the same md5sum. > > Have not tried setting debug options on the working cluster, will > try that. So it does not look like rbd issue. I don't think 'debug rbd' is useful here. You could try increasing 'debug ms' (ceph messages) though. -- Mykola Golub -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
