Dominique Ramaekers
2015-Sep-16 06:06 UTC
Re: [libvirt-users] libvirt 1.19: could not open drive file (permission denied)
@requillart Don't get me wrong. It's no problem to use other partitions. Only, you have to add the location to the storage pool of libvirt... Sorry, no experience with gnome-boxes. @crequill Add a new storage pool with the destination /home/crequill/VM You can't fool apparmour with a link... Also with adding the storage pool, it's easier to get a clear picture of the usage of your storage resources in virt-manager -----Oorspronkelijk bericht----- Van: requillart@gmail.com [mailto:requillart@gmail.com] Namens crequill Verzonden: dinsdag 15 september 2015 19:24 Aan: Dominique Ramaekers CC: libvirt-users@redhat.com Onderwerp: Re: [libvirt-users] libvirt 1.19: could not open drive file (permission denied) If we cannot use anymore another partitions, for me it's a bug. Not for you? For information, I get this error with gnome boxes. With it, images are in /home/crequill/.local/share/gnome-boxes/images/. How run it? 2015-09-15 17:53 GMT+02:00 crequill <crequill@worldonline.fr>:> Indeed, I have a link between /var/lib/libvirt/images and my home > directory on an another partition. > > # ls -al /var/lib/libvirt/images > lrwxrwxrwx 1 root root 17 3 sept. 09:29 /var/lib/libvirt/images -> > /home/crequill/VM > > 2015-09-15 17:45 GMT+02:00 Dominique Ramaekers <dominique.ramaekers@cometal.be>: >> A while ago, I had the same problem. It was a apparmor issue. Maybe your image is on a location outside your storage pools? >> >> -----Oorspronkelijk bericht----- >> Van: libvirt-users-bounces@redhat.com >> [mailto:libvirt-users-bounces@redhat.com] Namens crequill >> Verzonden: dinsdag 15 september 2015 17:29 >> Aan: libvirt-users@redhat.com >> Onderwerp: [libvirt-users] libvirt 1.19: could not open drive file >> (permission denied) >> >> Hi, >> >> With libvrit 1.18 all is working fine: I can open my win7 VM on Archlinux without problem. >> But I cannot use it with libvirt 1.19: it could not open drive file (permission denied). >> >> In /etc/libvirt/qemu.conf, I have: >> - user: root >> - group: root >> >> And the drive file has root:root as owner. >> >> Why this configuration is running with libvirt 1.18 and not with libvirt 1.19 ? >> >> Many thanks for your reply. >> Christophe >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users@redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users
crequill
2015-Sep-16 07:19 UTC
Re: [libvirt-users] libvirt 1.19: could not open drive file (permission denied)
For gnome boxes, a pool already exists: $ virsh pool-list Name State Autostart -------------------------------------------------- default active yes gnome-boxes active no $ virsh vol-list gnome-boxes Name Path ------------------------------------------------------------------------------ win7 /home/crequill/.local/share/gnome-boxes/images/win7 $ ls -alh /home/crequill/.local/share/gnome-boxes/images/win7 -rwxrwxrwx 1 root root 60G 15 sept. 17:11 /home/crequill/.local/share/gnome-boxes/images/win7 With this and libvirt 1.19, I get: 2015-09-15T17:17:19.563181Z qemu-system-x86_64: -drive file=/home/crequill/.local/share/gnome-boxes/images/win7,if=none,id=drive-virtio-disk0,format=raw: Could not open '/home/crequill/.local/share/gnome-boxes/images/win7': Permission denied So, why this configuration is running with libvirt 1.18 and not with libvirt 1.19 ? 2015-09-16 8:06 GMT+02:00 Dominique Ramaekers <dominique.ramaekers@cometal.be>:> @requillart > Don't get me wrong. It's no problem to use other partitions. Only, you have to add the location to the storage pool of libvirt... > Sorry, no experience with gnome-boxes. > > @crequill > Add a new storage pool with the destination /home/crequill/VM > You can't fool apparmour with a link... > Also with adding the storage pool, it's easier to get a clear picture of the usage of your storage resources in virt-manager > > > > > -----Oorspronkelijk bericht----- > Van: requillart@gmail.com [mailto:requillart@gmail.com] Namens crequill > Verzonden: dinsdag 15 september 2015 19:24 > Aan: Dominique Ramaekers > CC: libvirt-users@redhat.com > Onderwerp: Re: [libvirt-users] libvirt 1.19: could not open drive file (permission denied) > > If we cannot use anymore another partitions, for me it's a bug. Not for you? > For information, I get this error with gnome boxes. With it, images are in /home/crequill/.local/share/gnome-boxes/images/. How run it? > > 2015-09-15 17:53 GMT+02:00 crequill <crequill@worldonline.fr>: >> Indeed, I have a link between /var/lib/libvirt/images and my home >> directory on an another partition. >> >> # ls -al /var/lib/libvirt/images >> lrwxrwxrwx 1 root root 17 3 sept. 09:29 /var/lib/libvirt/images -> >> /home/crequill/VM >> >> 2015-09-15 17:45 GMT+02:00 Dominique Ramaekers <dominique.ramaekers@cometal.be>: >>> A while ago, I had the same problem. It was a apparmor issue. Maybe your image is on a location outside your storage pools? >>> >>> -----Oorspronkelijk bericht----- >>> Van: libvirt-users-bounces@redhat.com >>> [mailto:libvirt-users-bounces@redhat.com] Namens crequill >>> Verzonden: dinsdag 15 september 2015 17:29 >>> Aan: libvirt-users@redhat.com >>> Onderwerp: [libvirt-users] libvirt 1.19: could not open drive file >>> (permission denied) >>> >>> Hi, >>> >>> With libvrit 1.18 all is working fine: I can open my win7 VM on Archlinux without problem. >>> But I cannot use it with libvirt 1.19: it could not open drive file (permission denied). >>> >>> In /etc/libvirt/qemu.conf, I have: >>> - user: root >>> - group: root >>> >>> And the drive file has root:root as owner. >>> >>> Why this configuration is running with libvirt 1.18 and not with libvirt 1.19 ? >>> >>> Many thanks for your reply. >>> Christophe >>> >>> _______________________________________________ >>> libvirt-users mailing list >>> libvirt-users@redhat.com >>> https://www.redhat.com/mailman/listinfo/libvirt-users
crequill
2015-Oct-06 14:52 UTC
Re: [libvirt-users] libvirt 1.19: could not open drive file (permission denied)
Hi, Problem resolved with libvirt-1.20 and by configuring qemu to run from my user (in /etc/libvirt/qemu.conf, modify user and group and restart libvirtd). Best regards. Christophe 2015-09-16 9:19 GMT+02:00 crequill <crequill@worldonline.fr>:> For gnome boxes, a pool already exists: > > $ virsh pool-list > Name State Autostart > -------------------------------------------------- > default active yes > gnome-boxes active no > > $ virsh vol-list gnome-boxes > Name Path > > ------------------------------------------------------------------------------ > win7 /home/crequill/.local/share/gnome-boxes/images/win7 > > $ ls -alh /home/crequill/.local/share/gnome-boxes/images/win7 > -rwxrwxrwx 1 root root 60G 15 sept. 17:11 > /home/crequill/.local/share/gnome-boxes/images/win7 > > With this and libvirt 1.19, I get: > > 2015-09-15T17:17:19.563181Z qemu-system-x86_64: -drive > > file=/home/crequill/.local/share/gnome-boxes/images/win7,if=none,id=drive-virtio-disk0,format=raw: > Could not open '/home/crequill/.local/share/gnome-boxes/images/win7': > Permission denied > > So, why this configuration is running with libvirt 1.18 and not with > libvirt 1.19 ? > > 2015-09-16 8:06 GMT+02:00 Dominique Ramaekers < > dominique.ramaekers@cometal.be>: > > @requillart > > Don't get me wrong. It's no problem to use other partitions. Only, you > have to add the location to the storage pool of libvirt... > > Sorry, no experience with gnome-boxes. > > > > @crequill > > Add a new storage pool with the destination /home/crequill/VM > > You can't fool apparmour with a link... > > Also with adding the storage pool, it's easier to get a clear picture of > the usage of your storage resources in virt-manager > > > > > > > > > > -----Oorspronkelijk bericht----- > > Van: requillart@gmail.com [mailto:requillart@gmail.com] Namens crequill > > Verzonden: dinsdag 15 september 2015 19:24 > > Aan: Dominique Ramaekers > > CC: libvirt-users@redhat.com > > Onderwerp: Re: [libvirt-users] libvirt 1.19: could not open drive file > (permission denied) > > > > If we cannot use anymore another partitions, for me it's a bug. Not for > you? > > For information, I get this error with gnome boxes. With it, images are > in /home/crequill/.local/share/gnome-boxes/images/. How run it? > > > > 2015-09-15 17:53 GMT+02:00 crequill <crequill@worldonline.fr>: > >> Indeed, I have a link between /var/lib/libvirt/images and my home > >> directory on an another partition. > >> > >> # ls -al /var/lib/libvirt/images > >> lrwxrwxrwx 1 root root 17 3 sept. 09:29 /var/lib/libvirt/images -> > >> /home/crequill/VM > >> > >> 2015-09-15 17:45 GMT+02:00 Dominique Ramaekers < > dominique.ramaekers@cometal.be>: > >>> A while ago, I had the same problem. It was a apparmor issue. Maybe > your image is on a location outside your storage pools? > >>> > >>> -----Oorspronkelijk bericht----- > >>> Van: libvirt-users-bounces@redhat.com > >>> [mailto:libvirt-users-bounces@redhat.com] Namens crequill > >>> Verzonden: dinsdag 15 september 2015 17:29 > >>> Aan: libvirt-users@redhat.com > >>> Onderwerp: [libvirt-users] libvirt 1.19: could not open drive file > >>> (permission denied) > >>> > >>> Hi, > >>> > >>> With libvrit 1.18 all is working fine: I can open my win7 VM on > Archlinux without problem. > >>> But I cannot use it with libvirt 1.19: it could not open drive file > (permission denied). > >>> > >>> In /etc/libvirt/qemu.conf, I have: > >>> - user: root > >>> - group: root > >>> > >>> And the drive file has root:root as owner. > >>> > >>> Why this configuration is running with libvirt 1.18 and not with > libvirt 1.19 ? > >>> > >>> Many thanks for your reply. > >>> Christophe > >>> > >>> _______________________________________________ > >>> libvirt-users mailing list > >>> libvirt-users@redhat.com > >>> https://www.redhat.com/mailman/listinfo/libvirt-users >
Apparently Analagous Threads
- Re: libvirt 1.19: could not open drive file (permission denied)
- Re: libvirt 1.19: could not open drive file (permission denied)
- Re: libvirt 1.19: could not open drive file (permission denied)
- Re: Windows Server 2008 - KVM
- 答复: How could I do the guest mount operation from the host?