Dear Wido and all, FYI, I managed to resolve the problem by installing latest version of libvirt. Apparently, the libvirt version that I was using (1.0.2), which I got from here:
http://blog.widodh.nl/2013/06/a-quick-note-on-running-cloudstack-with-rbd-on-ubuntu-12-04/ was the culprit. I downloaded the latest libvirt version (version 1.1.0) from their FTP site: ftp://libvirt.org/libvirt/libvirt-1.1.0.tar.gz Install the latest librbd-dev package: apt-get install librbd-dev Then compile libvirt with storage RBD enabled: ./autogen.sh --prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --with-storage-rbd Restart the KVM host after it's done. virsh pool-info is now showing the correct "Allocation" amount: root@hv-kvm-02:~# virsh pool-info d433809b-01ea-3947-ba0f-48077244e4d6 Name: d433809b-01ea-3947-ba0f-48077244e4d6 UUID: d433809b-01ea-3947-ba0f-48077244e4d6 State: running Persistent: no Autostart: no Capacity: 5.47 TiB Allocation: 328.00 B Available: 5.47 TiB Tried to create a VM instance, and now the VM can utilise the RBD storage pool. No more "insufficient space on pool" error message on the log. The only issue is that, I noted that only the DATADISK volume is created on the RBD primary storage pool. The ROOT volume of that VM is still created on the NFS primary storage pool. Is there a way to ensure that the ROOT volume will also be created on the RBD primary storage pool instead of the NFS pool? Looking forward to your reply, thank you. Cheers. On Wed, Jul 17, 2013 at 12:42 PM, Indra Pramana <[email protected]> wrote: > Dear Wido and all, > > On Tue, Jul 16, 2013 at 10:49 AM, Indra Pramana <[email protected]> wrote: > >> Hi Prasanna, >> >> On Mon, Jul 15, 2013 at 12:38 PM, Prasanna Santhanam <[email protected]>wrote: >> >>> It might be a bug on ceph but the thread you referenced was resolved. >>> See here: http://markmail.org/message/mkm2fqyawmwpufsc >>> >>> If it still persists, can you please file a bug on JIRA? >>> >> >> As suggested, I have filed a bug on JIRA. >> >> https://issues.apache.org/jira/browse/CLOUDSTACK-3542 >> >> Appreciate any advise on how to resolve the problem. Wido, any comments >> from your end? :) >> > > Anyone has any clues on how to resolve this problem? It is a show-stopper > for me, I can't proceed further without able to get my RBD primary storage > to work. > > Any advice is greatly appreciated. > > Looking forward to your reply, thank you. > > Cheers. > >
