• firewall behavior
• exporting file system syntax and use of pseudo file systems
• difference in mount command syntax

I am running systems that use SELinux and firewalls*. I have one Centos 5.3 NFS server and three client machines running as virtual machines** on the server. My goal was to establish remote file systems for the virtual machine clients. I’ll skip some of the introductory steps to set up the nfs server process that are listed in the doc.

I’ll list the commands that I used to export the file system from the server and the mount command I first used on the client. The file system that I was attempting to export was /junk/client1. On the server (server.stevens.net), I added the following to /etc/exports:

and I used the following mount command on client1.stevens.net (and received the error shown):

A bit surprised that it didn’t work, I poked around the Internet and I found some good info that ultimately helped me get on the right track at Miles Brennan’s Linux Home Server HOWTO page. He does an excellent job explaining the pseudo file system configuration required for version 4 of NFS.

I built out the following psuedo file system on the server:

I then created bindings in /etc/fstab between /NFS4exports and /junk directories as follows (Bindings are like symbolic links, but the files are available in both filesystems, rather than being linked to the source location.):

Then I list the pseudo file systems in the /etc/exports file, and it is critical to note that the fsid=0 option be defined on the /NFS4exports file system (even though /NFS4exports itself will not be mounted by a remote client). Then all exported file systems are sub-directories of this system. If I had additional file systems elsewhere on the server that I wanted to share (say, /home), I would need to create an entry in the pseudo file system and bind it to /home in fstab.

Then I mounted the file systems from the client1 system. A major difference between the NFSv3 and NFSv4 command is that the root pseudo filesystem is not included in the identity of the remote file system (i.e., the NFS4exports directory is omitted from the command.

And on client2, showing an example that it can mount the client1 directory, but can’t see anything or write to it:

And that completed my setup (except to modify /etc/fstab so that the new /remotesys file system will automount at boot). The main point was to learn about NFS, but I also ended up with a way to provide storage for my virtual machines outside of the .vmdk virtual file system.


Footnotes:
* NFSv4 plays better with firewall because, unlike NFSv3, it does not make use of portmapper and rpc.mountd, rpc.statd, and rpc.lockd. I just had to open port 2049 on the firewall for NFS. However, during some troubleshooting, I needed to execute “showmount -e sserver.stevens.net’ from a client machine. The firewall blocked it, because it uses rpc.mountd and portmapper picks a random port by default. I used /etc/sysconfig/nfs to define a static port for rpc.mountd and then opened this port on the firewall too.
** As a side note with respect to the virtualization setup, I created one vm and installed a small, simple Centos image. Then I copied the files twice to new folders in /var/lib/vmware/VirtualMachines. Then I imported these virtual machines into VMware Server to quickly make some clones. Just a quick edit of the /etc/sysconfig/network file to update each machine to a unique hostname, and I had 3 distinct client machines.

I downloaded VMware Server (The 64 bit Linux RPM package) from http://www.vmware.com/freedownload/login.php?product=server20 as well as the User Guide from http://www.vmware.com/support/pubs/server_pubs.html. You will have to register with an email address on the VMWare site to access the downloads.

Chapter 2 of the User Guide walks you through the install. For me it looked like this:
After downloading the rpm package, I moved it to /tmp and checked the checksum vs. the value on the VMware download page. (It matched, trust me)

Then installed it with the instructions in the User Guide, and ran the vmware-config.pl script

In this script, I had to:

• Accept the EULA
• Configure networking (make all three types: bridged, NAT and host-only. When you build virtual machines, you may then select which type of network connection you want for each virtual machine. More info about the network types in chapter 11 of the User’s Guide)
• Set an administrator name (user on the computer)
• Set some port numbers (used defaults)
• Set some directories to store files. I did not like that the virtual machine files would, by default, be stored in /var/lib/vmware/Virtual Machines (space in directory name – yuck) so I changed it to /var/lib/vmware/VirtualMachines.
• Enter your license key, provided on the VMware download page.

Once it was installed, I fired up Firefox, aimed at http://localhost:8222 which started the VI Web Access (VMware Servers UI). This is when I realized that /var was too small. I decided to grow /var, since it was a logical volume and i had available space in the Volume Group. (This is worthy of it’s own post).

I configured my first virtual machine using Chapter 4 of the User Guide and the wizard. Then I placed my Windows 7 RC installation DVD into the drive and powered on the Virtual Machine, and completed the install of the guest OS. Poof! Virtualization experienced.

Still loads and loads (and loads?) to learn, but it’s been good to see the allocation of host resources for the guest machines, as well as the representation of virtual hardware to the guest OS.