Comment 2 for bug 691590

Yes, this would work (as long as the process doing this move owns the directory -- otherwise it is still an error 13). The whole point, though, is that libvirt does not need to take ownership of a *read-only* file.

At least it could revert the ownership when the VM is closed, if you want to protect against an ISO update while the ISO is in use by libvirt. Or use flock, or something. But this (update-while-somebody-is-using) is a common issue on *IX, and still we do not see ownership being unilaterally changed.

Of course, we can also bypass by using 'sudo', but this would break the least privilege principle.