This is my first technical post.
Back in February 2010 I decided I needed some hands-on outside of work to catch up to all the changes in the Virtualization world.
I am a regular reader on http://www.xenappblog.com so I used this post as a basis for building my home training lab.
Couple of notes:
- ASUS M4A78-EM is now out of stock. I picked up 3 of these (One on Amazon as Used)
- AMD X4 9650 CPU is out of Stock so I picked up the AMD X4 9750 (Note you need to also by a 92mm CPU FAN as well)
- Corsair 8GB (4×2GB) has jumped in price and is now $99.00 USD per 4GB
- I also added a larger Maxtor Internal Drive and DVD.
I also wanted to test XENMOTION and use Provisioning Server so I figured I would need a cheap NAS solution. I reviewed several methods for standing up a old PC as a NAS, but determined I wanted something smaller with low power requirements.
I already had a small Buffalo CIFS NAS so I set that up as a CIFS .ISO storage repository in XENCENTER (Note: I had to use the option to specify using different credentials and specify “Guest”)
My initial research of cheap NAS solutions on Newegg lead me to believe the cheapest enclosure that supported NFS was the Patriot Valkyrie 2 . It was advertised sporting a fast processor, NFS support, lifetime warranty, and didn’t have any negative reviews. It seemed better then any of the other NAS solutions at that price. Once I got the device I discovered that the current firmware doesn’t have NFS or AFP support , the software has a number of issues reported on Patriot forums, and after running the drives for 24 hours discovered case doesn’t provide enough cooling for the drives (The drives were so hot, I could barely touch them). You can read my review on Newegg for more information of the problems. The device has potential, but the promised firmware hasn’t been released yet and I got tired of waiting. I did some additional research and discovered the DLINK DNS-321 is a more mature cheap NAS solution, so I bought one and when I got it set it up and updated to the latest firmware so it would support my 2x2TB drives.
My initial attempts to setup a NFS Storage Repository didn’t work through XENCENTER though.
What I discovered after a lot of trial and research was that when setting up the NFS Share on the NAS, I needed to specify the host as 192.168.1.0/24 . This will setup the etc/exports file to allow all nodes on my subnet access to the NAS. Also you need to enable read and write access (of course).
The other trick I learned about the DNS-321 is that the default Volume_1 is not the actual path. I was specifying <NAS IP>:/Volume_1 as the path and scanning and it didn’t work. While researching on CITRIX’s forums, I discovered some post related to the Error 32 in the XENCENTER Application log that recommended running Telnet or SSH against the device and then doing the ether of the following commands.
- CAT /etc/exports
- MORE /etc/exports
When one of these commands are ran, it will list the NFS shares. This is what has to be entered on the Storage Repository path. The problem is the DNS-321 doesn’t have TELNET or SSH enabled by default. A little more research revealed that the device can be hacked pretty easily using Fun_Plug modifications. Just download and copy over the Volume_1 the Fun_Plug file and Fun_Plug.tgz files and reboot SAN device. After a few minutes you can TELNET into the host using Putty and run the commands at the top to list the NFS Shares.
The NFS Share for the DNS-321 is /mnt/HD_a2 . So you really don’t need to Telnet or SSH though to figure that out since it is listed on the NFS Sharing page, it is just a little misleading. I assume you can also modify the /etc/exports file on the NAS to specify different paths if you wanted to as well. So messing around with Fun_Plug is not a bad thing.
Once I got NAS working, I created a 2008 Console Only VM, Installed the XENSERVER Tools manually, then did a XENMOTION. It worked, but it took some time for it to complete and the XENCENTER Console lost communication with the XENSERVER initially in the process.
Summary:
- DLINK DNS-321 with latest firmware works with XENSERVER 5.5
- Setting up NAS NFS Share specify Host as 192.168.1.0/24 and Make it R/W
- Setting up XENCENTER SR specify <SAN IP>:/mnt/HD_a2
- Troubleshooting XENCENTER [Error 32] TELNET or SSH into NAS and list the /etc/exports file to determine correct NFS share paths.