On Sun, Sep 15, 2013 at 2:42 PM, Dan Kenigsberg wrote:
On Sun, Sep 15, 2013 at 01:59:29PM +0200, Gianluca Cecchi wrote:
> On Sun, Sep 15, 2013 at 1:50 PM, Gianluca Cecchi wrote:
Gianluca, due to all the twists of this thread, I no longer recall
which
libvirt version you are using. Would you remind us?
All signs show that it starts up qemu without setting its auxiliary
group properly (Assuming that your
# groups qemu
qemu : qemu kvm
is just as mine)
I've added libvir-list so the fine folks there could check why qemu
cannot read/write files group-owned by kvm.
Dan.
I'm using what stock f18 repo gives today:
[root@tekkaman ~]# rpm -q libvirt
libvirt-0.10.2.7-1.fc18.x86_64
[root@tekkaman ~]# groups qemu
qemu : qemu kvm
[root@tekkaman ~]# grep libvirt-0 /var/log/yum.log
Jan 07 00:12:13 Installed: libvirt-0.10.2.2-3.fc18.x86_64
Feb 09 17:17:30 Updated: libvirt-0.10.2.3-1.fc18.x86_64
Apr 18 19:44:58 Updated: libvirt-0.10.2.4-1.fc18.x86_64
May 29 20:45:26 Updated: libvirt-0.10.2.5-1.fc18.x86_64
Jun 27 20:05:24 Updated: libvirt-0.10.2.6-1.fc18.x86_64
Aug 18 19:09:52 Updated: libvirt-0.10.2.7-1.fc18.x86_64
I'm not using consistently this all-in-one system for ovirt.
For sure in July it worked ok.
Only today when I wanted to run one of its vms, I saw the error and I
found this reference in the list.
Gianluca