On 02/04/12 11:29, Richard W.M. Jones wrote:
What's the actual, complete error message?
What's the output when you use:
export LIBGUESTFS_TRACE=1
How about if you use:
export LIBVIRT_DEBUG=1
guestfs-browser -x
libguestfs: trace: add_drive_opts
"/var/lib/libvirt/images/01-Old-32.img" "readonly:true" "format:raw"
libguestfs: trace: add_drive_opts = -1 (error)
libguestfs: trace: close
Both give above.
ls -l /var/lib/libvirt/images
total 335544764
-rw-------. 1 root root 42949672960 Apr 2 11:32 01-Old-32.img
-rw-------. 1 root root 42949672960 Apr 2 09:30 02-Old-64.img
-rw-------. 1 root root 42949672960 Apr 2 09:53 03-Current-32.img
-rw-------. 1 root root 42949672960 Apr 2 10:02 04-urrent-64.img
-rw-------. 1 root root 42949672960 Apr 2 10:12 05-Branched-32.img
-rw-------. 1 root root 42949672960 Apr 2 10:20 06-Branched-64.img
-rw-------. 1 root root 42949672960 Apr 2 08:31 07-Rawhide-32.img
-rw-------. 1 root root 42949672960 Apr 2 08:49 08-Rawhide-64.img
Virt-Manager doesn't have the "readonly" checked in the virtio disk
libguestfs itself doesn't use PolicyKit, so it's doubtful that
creating that .pkla file is having any effect whatsoever. libvirt
uses PolicyKit, and libguestfs uses libvirt to get a list of local
guests, so a *libvirt* .pkla file may be necessary, but without
knowing what the error is, it's hard to tell.
Rich.
There is a libvirt.pkla in place.
--
Regards,
Frank
"Jack of all, fubars"
_______________________________________________
virt mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/virt
