WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] NFS problem under domU

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] NFS problem under domU
From: "Gino LV. Ledesma" <gledesma@xxxxxxxxx>
Date: Fri, 11 Nov 2005 12:02:01 -0800
Delivery-date: Fri, 11 Nov 2005 20:02:12 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IfOPucNCmXTs9rqZ0lW6Ffmz/NA9Np65vwM2QJfoEKZTg501Xmj2887U9SQJXo8azgQpuUYudBdysgHArCQXoGAR0ECxIwlIkKP6O3Lt8ocWYGsWOz81eQ4E4zCdwbL7PA3no9KdXSOfTmMoTnqXI0BqE2ktgd4LKLD3DTPZbxw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1131738996.2462.30.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1131720596.2462.7.camel@xxxxxxxxxxxxxxxxxxxxx> <e27bf7770511110946sdb46663s535e95c3c485dc71@xxxxxxxxxxxxxx> <1131738996.2462.30.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Oh, so I take it you don't _need_ NFS4? :-)

I was assuming this since your error logs and the messages you were
pointing to mentioned NFS4. If NFS support is all you need, then just
compile in the regular NFSv2/NFSv3 support into your kernel.

Now as mentioned in the links you placed, Fedora Core 4 comes with
NFSv4 support, and the init scripts assume you have the NFSv4 module.
You have two options to make Fedora Core 4 happy:

1. Compile NFSv4 support as a module -- OR --
2. Modify the init scripts so that it doesn't load the NFSv4 stuff
(there's a number of them)

- gino

On 11/11/05, Jorge I. Davila L. <davila@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> support for NFS4 is experimental for the 2.6.11.12 kernel :-O (at least
> is that I can see in my kernel configuration )
>
> El vie, 11-11-2005 a las 09:46 -0800, Gino LV. Ledesma escribió:
> > Have had problems with this as well in the past. What I did was to
> > compile the kernel with NFS4 and party as modules instead since the
> > stock Fedora scripts insist on loading the module as part of startup.
> >
> > -gino
> >
> > On 11/11/05, Jorge I. Davila L. <davila@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > > Hello list!:
> > >
> > > I'm having a problem with NFS under a domU with fedora core 3 / xenU
> > > kernel 2.6.11.12-xenU
> > >
> > > When the nfs daemon is started (or restarted):
> > >
> > > # service nfs restart
> > > Shutting down NFS mountd:                                  [  OK  ]
> > > Shutting down NFS daemon:                                  [  OK  ]
> > > Shutting down NFS quotas:                                  [  OK  ]
> > > Shutting down NFS services:                                [  OK  ]
> > > Starting NFS services:                                     [  OK  ]
> > > Starting NFS quotas:                                       [  OK  ]
> > > Starting NFS daemon:                                       [  OK  ]
> > > Starting NFS mountd:                                       [  OK  ]
> > > Starting RPC idmapd: FATAL: Module sunrpc not found.
> > > FATAL: Error running install command for sunrpc
> > >
> > >
> > > Trying to mount the shared resources:
> > >
> > > # mount -t nfs4  w.x.y.z:/download /root/nfs
> > > Warning: rpc.idmapd appears not to be running.
> > >          All uids will be mapped to the nobody uid.
> > > mount to NFS server 'w.x.y.z' failed.
> > >
> > > I tried the proposed solutions here:
> > >
> > > http://forums.fedoraforum.org/showthread.php?t=63224
> > >
> > > and here:
> > >
> > > http://linux-nfs.org/pipermail/nfsv4/2005-July/002246.html
> > >
> > > In the domU /var/log/messages I can see:
> > >
> > > Nov 11 08:24:06 ltskbunk rpc.idmapd: nfsdreopen: Opening
> > > '/proc/net/rpc/nfs4.idtoname/channel' failed: errno 2 (No such file or
> > > directory)
> > > Nov 11 08:24:06 ltskbunk rpc.idmapd: nfsdreopen: Opening
> > > '/proc/net/rpc/nfs4.nametoid/channel' failed: errno 2 (No such file or
> > > directory)
> > >
> > > I'm guessing that there is not a xen issue. But I wonder if someone here
> > > can give some light.
> > >
> > > Thanks,
> > >
> > >
> > > --
> > > -----------------------------------------------------------------
> > > Jorge Isaac Davila Lopez
> > > -
> > > sitio web: http://www.nicaraguaopensource.com/
> > > correo-e: davila@xxxxxxxxxxxxxxxxxxxxxxx
> > > -
> > > clave pgp: http://www.nicaraguaopensource.com/claves/nos.asc
> > > huella digital: F8F4 8563 28D2 29E1 E2EA 9EAB CA0F A96F A3EE 6F56
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> > >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> --
> -----------------------------------------------------------------
> Jorge Isaac Davila Lopez
> -
> sitio web: http://www.nicaraguaopensource.com/
> correo-e: davila@xxxxxxxxxxxxxxxxxxxxxxx
> -
> clave pgp: http://www.nicaraguaopensource.com/claves/nos.asc
> huella digital: F8F4 8563 28D2 29E1 E2EA 9EAB CA0F A96F A3EE 6F56
>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>