monkeyfoahead wrote:I own a Mac Pro modified to accept 8 sata harddrives that I have in a single zpool. If Zevo bites the dust, will I be able to run some kind of VM solution from within OSX to access this zpool? Please pardon my ignorance.
Yes. If you want to continue using OS X on the Mac Pro, you can use VMware Fusion ($50) or Oracle's VirtualBox (free but less user friendly).
http://www.vmware.com/products/fusion/overview.html
You have two choices on how to gain access to the drives from within the VM.
1. Option 1.
Buy a PCIe USB 3.0 express card (about $70) for the Mac Pro, as described here like this:
http://www.sonnettech.com/product/allegrousb3pcie.html
Buy (about $60-$100) one or two USB 3.0 hubs so that you have at least 8 ports total:
viewtopic.php?f=4&t=1649#p4611
Buy eight USB 3.0 enclosures (3.5" or 2.5") depending on the size of the drives. (about $50 each) For example:
http://lifehacker.com/5955402/five-best ... enclosures
Use VMware's USB 3.0 "adapter" to directly connect the drives to a VM.
You will most likely want to use Linux for the operating system together with ZFS on Linux http://zfsonlinux.org
Other OS choices are Oracle Solaris 11, Free BSD, or some flavor of Illumos (formerly Open Solaris) such as Open Indiana or SmartOS.
I'm recommending Linux because I don't think VMware has proper USB 3.0 "adapters"/drivers for the other OSs.
2. Option 2.
Use "raw disk" vmdk files to map the drives to the VM. This will work as long as each of the drives is less than 2 terabytes. (It may have been upped to 3 terabytes recently, but I'm not sure). You create the raw disk vmdk files using the command line tool vmware-rawdiskCreator, which is included with VMware Fusion. Once VMware Fusion is installed, the command line tool is located at this path:
/Applications/VMware Fusion.app/Contents/Library/vmware-rawdiskCreator
(VirtualBox has an equivalent command line tool called VBoxManage which is located at /usr/bin/VBoxManage. Incidentally, the raw disk vmdk files created by VBoxManage can be used with VMware too.)
One tiny hurdle is that VMware Fusion does not let you create raw disk vmdks through the GUI. You have to add them either by directly editing the vmx configuration file or by using a simple trick. You create a virtual hard disk vmdk via VMware Fusion's GUI. And then simply replace the virtual hard disk vmdk file the GUI created with the raw disk vmdk file you created using vware-rawdiskCreator. If the raw disk vmdk file has the same file name as the virtual disk vmdk created through the GUI, VMware will happily use the raw disk vmdk file. This trick just lets you avoid having to deal with editing the vmx file by hand.
You will create one raw disk vmdk file for each of your physical drives and the virtual machine should be able to access them fine.
Usually the purpose of the raw disk vmdk feature is to make it possible for VMware Fusion to boot a physical Boot Camp partition as a virtual machine. That's why they make it difficult to manipulate raw disk vmdks via the GUI. The GUI has features which are inapporpriate for raw disks (such as resizing). Nonetheless, the non-Boot-Camp raw disk vmdks work just fine if you use the command line tool vware-rawdiskCreator.
Option 2 should work with any of the guest OSs I mentioned above because there is no need for the guest OS to have any particular driver nor for VMware to have any particular VM adpater compatible with the guest OS.
Of the two options, option 1 USB 3.0 or option 2 raw disk vmdks, option 1 USB 3.0 will likely give you better performance because VMware is actually able to pass the drive through to the virtual machine directly and use a proper VM adapter. Option 2 is cheaper but will probably have worse performance because the drive is not actually passed through but merely mapped via the raw disk vmdk file. Also, option 2 is a bit more advanced because you have to use the command line tool to create the raw disk vmdks.
____
Now, if the Mac Pro is not your primary computer, you could repurpose it as a VMware ESXi 5.1 server http://kb.vmware.com/selfservice/micros ... Id=2032756
Mac Pros are officially supported hardware for ESXi server http://www.vmware.com/resources/compati ... search.php
Given that you have SATA drives directly attached, ESXi server would be a very powerful approach. (It's also free.) You would connect the Mac Pro to your primary computer via Gigabit Ethernet (10 GbE if you can afford it) and access the ESXi server's virtual machines from your primary computer. The ESXi server could run Oracle Solaris 11, Linux, etc. You are even allowed to run OS X on the ESXi server because a Mac Pro is Apple hardware. The reason the Mac Pro would not be your primary machine is that the ESXi server cannot itself be a console for accessing the virtual machines that it is hosting. You have to access them from a console on a client computer, which would be your primary computer. Because ESXi runs on bare metal, the performance should be fantastic compared to VMware Fusion, which runs as software on top of OS X. Because your SATA drives are directly attached, you should be able to pass them through (paravirtualized) to the guest OSs if you want to keep your existing pool.
Your last option would be to install Linux directly on the Mac Pro, which should work great. Whether you could live with that as a primary machine is your judgment. At worst it could be a server. I doubt you will be able to install Oracle Solaris 11 or Open Indiana directly on the Mac Pro, but you never know. Also, FreeBSD may work on Mac Pros, but I'm not sure. Using ESXi server gets around these OS compatibility issues because the Mac Pro hardware is officially supported for ESXi, and then you put whatever ZFS capable OS on top of ESXi that you please.