Managing disk in a VM
Posted
by
dst
on Super User
See other posts from Super User
or by dst
Published on 2013-09-03T12:24:40Z
Indexed on
2013/10/26
22:01 UTC
Read the original article
Hit count: 323
I'm replacing my two old rack servers with a new one that has plenty of power to take over the functionality my current servers. The server is a 4U rack mount with 16 3.5" SAS drive bays, two 2.5" bays, a Xeon E3-1230v2 CPU and 32GB of ECC RAM.
My issue is the following. I would like to have a FreeBSD file server with ZFS managing disks. However, I need other VMs for e.g. a shell/git server, mail server etc. I'm wondering how to deal with the following issues:
I want ZFS to fully manage the disks, so I'm not using any hardware RAID. Should I pass the SAS controller directly to the FreeBSD system as passthrough PCI?
I want to maximize the reliability of the setup. On what disks should I install the hypervsor and keep server system disks?
For (2) I have the option of having a RAID setup on the SAS controller and using that as system disk to store the hypervisor as well as VM images. However, this makes PCI passthrough to the file server impossible. Another option is using the two 2.5" bays. In terms of reliability how are SSDs compared to e.g. WD RE4 disks? Would it make sense to have two SSDs in software RAID as boot disks for the hypervisor or should I just go with e.g. WD RE4 disks in a software RAID setup.
I also need to think about where to store the mails for the mail server, but this could be done over NFS between the VMs.
BTW, this is for home use, so the load is not really that big. What I'm looking for is best practices for splitting up a server.
© Super User or respective owner