On Fri, May 06, 2011 at 06:10:24PM -0400, T Johnson wrote:
On Thu, May 5, 2011 at 10:59 PM, Richard W.M. Jones
<rjones(a)redhat.com> wrote:
> The I/O errors above would be because the underlying disk is somehow
> read-only to qemu.
>
By this you mean the uid the process is running as and not the actual
'qemu' uid, right? Just making sure..
No, I mean that libguestfs is unable to open the disk in anything
other than read-only mode. The 'qemu' user/uid has nothing to do with
this.
> For NFS I guess this could be because of root_squash-ing.
>
Hmm, ok. I will keep plugging away and update the thread if I discover
something.
One thing that's curious is I've also played with just using
command-line `virt-X` and `guestfish` to upload new files to the same
images and haven't had the same write problems and/or process hangs.
Secondly, the changes *do* get written to the images so it's certainly
not a flat-out permission denied issue.
It's got something to do with what permissions or user your daemon /
remote process runs as, but from here it's hard to say exactly what.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://libguestfs.org