On 10/23/2009 07:22 AM, Jon Nordby wrote:
The problem is due to libvirt using mount.nfs instead of mount.nfs4
for
NFSv4 shares.
virt-manager tries the following command (see attached file):
[jon@jon-laptop ~]$ sudo /bin/mount 10.0.0.2:/libvirt_install
/var/lib/libvirt/images/server-install
mount.nfs: access denied by server while mounting 10.0.0.2:/libvirt_install
When it should be something like this instead:
[jon@jon-laptop ~]$ sudo /bin/mount -t nfs4 10.0.0.2:/libvirt_install
/var/lib/libvirt/images/server-install
Because mount apparently considers NFSv4 to be a different type than
previous NFS versions:
[jon@jon-laptop ~]$ mount.nfs
mount.nfs mount.nfs4
OS: Arch Linux Current on both server and client. nfs-utils 1.2.0-4 and
kernel 2.6.31
I don't believe there is a good way to programatically check which version a
share is, but one can catch the error and try again with "-t nfs4".
Or perhaps trying nfs4 first is better...
> libvirtError: internal error '/bin/mount
10.0.0.2:/libvirt_install
/var/lib/libvirt/images/server-install' exited with
non-zero status 32
and signal 0: mount.nfs: access denied by server while mounting
10.0.0.2:/libvirt_insta
FYI, libvirt issues should go to libvirt-list(a)redhat.com (cc'ing)
- Cole