On Mon, Aug 29, 2016 at 6:03 PM, Mykola Golub <mgolub@xxxxxxxxxxxx> wrote: > May be qemu does not see you ceph.conf? Or some other environmental > issue (e.g. with qemu rbd driver). Try > > ldd /usr/bin/qemu-system-x86_64 |grep rbd > > Have you tried starting it from command line? > > You could check if config debug options work as expected setting them > on your working cluster. You can also try "touch /tmp/cbt/ceph/log/$name.log" and "chmod 777 /tmp/cbt/ceph/log/$name.log" to eliminate permissions issues. > > On Fri, Aug 26, 2016 at 09:08:30PM +0000, Deneau, Tom wrote: >> I have two small clusters configured with the same version of Ceph and the same OS version. >> (different processor hardware) >> >> On these clusters I have bootable RBD images that I expect a VM to boot from. >> On one cluster, the VM does not boot from the image. On the other cluster, it boots fine. >> On the failing cluster, a VM can boot fine from the base qcow2 image from which the rbd image was created. It's only rbd images that are causing problems for the VM. >> >> I would like to enable some debug logging that could tell where the two clusters are diverging. >> >> I tried adding >> debug rbd = 20 >> log file = /tmp/cbt/ceph/log/$name.log >> >> I do see some rbd debug messages to stderr during operations like rbd clone, etc. but I don't see any log files created in /tmp/cbt/ceph or /var/log/ceph or any messages when librbd is being used by say qemu-img convert, or by qemu-kvm. >> >> Is there a way to see detailed debug messages for librbd? >> >> Or is there a better way to see where things are diverging between these two clusters? >> (note: I tried lttng but could not get it to record anything) >> >> -- Tom >> -- >> 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 > > -- > 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 -- Cheers, Brad -- 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
