On 03/20/2014 05:38 PM, Nux! wrote:
On 19.03.2014 22:48, Edison Su wrote:
-----Original Message-----
From: Nux! [mailto:n...@li.nux.ro]
Sent: Wednesday, March 19, 2014 3:34 PM
To: dev@cloudstack.apache.org
Subject: RE: [RFC]Bypass Libvirt storage pool for NFS
On 19.03.2014 22:28, Edison Su wrote:
Edison, if - with the workarounds in place now - the current version
of KVM works OK, then why wouldn't a newer version work just as fine?
Just trying to understand this.
That's a long story, there is a bug in Libvirt, which is introduced in
a newer version(>0.9.10), which can make the storage pool disappear.
Edison, that I understand, but what is the technical reason that
prevents
using newer KVM?
It looks like current KVM works fine on CentOS 6.5 for example which has
libvirt 0.10.2.
Yes, at first glance, the newer version libvirt(> 0.9.10) just works
fine. But under stress test, it will complain NFS storage pool
missing, and can't add the storage pool back, unless you shut down all
the VMs which using the storage pool. That's the
bug(https://bugzilla.redhat.com/show_bug.cgi?id=977706) all about.
In ACS 4.2/4.3 release, we only recommend to use libvirt <=0.9.10, if
primary storage is NFS.
Ok, I'm trying to make some noise in that bz entry, hopefully someone
gets annoyed enough to do something about it.
And it just went upstream! How great is that?
Quick question: there is no problem if instead of using NFS directly we
use the "shared mount point" option, is it?
Probably not, since we would then be mounting the filesystem manually
instead of having libvirt do it.
I'd say get this patch down into EL6 and I'll try to get it into Ubuntu
14.04.
Wido
Lucian
