libvirt disk option "cache=none" prevents VM from booting on GlusterFS/FUSE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Daniel Berrange |
Bug Description
I just upgraded all my Ubuntu and Essex packages to the latest for Ubuntu 12.04:
root@spcnode1:
ii libvirt-bin 0.9.8-2ubuntu13 programs for the libvirt library
root@spcnode1:
ii nova-compute 2012.1~
Now VMs are refusing to start, with this error:
2012-03-19 12:14:03 ERROR nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
Looking through libvirt logs in /var/log/libvirt and /var/log/
I found the addition merged in a few days ago here: https:/
If I edit my libvirt.
tags: | added: essex-rc-potential |
summary: |
- libvirt disk option "cache=none" prevents VM from booting + libvirt disk option "cache=none" prevents VM from booting on + GlusterFS/FUSE |
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
milestone: | none → essex-rc2 |
tags: | removed: essex-rc-potential |
Changed in nova: | |
milestone: | essex-rc2 → 2012.1 |
After a bit more testing, this only happens when I am using GlusterFS as my VM store. In the above report, /mnt/vmstore is a GlusterFS mount (running Gluster 3.3beta). If I edit my nova.conf to remove "--instances_path", so that the default instance directofy of /var/lib/ nova/instances is used instead, cache="None" seems to be accepted fine.
That begs the question of whether specifying "cache=none" across the board is really ideal.
I'm not sure what the correct setting should be for user with GlusterFS. Perhaps documenting this potential tripping point is sufficient.