1 |
On Apr 9, 2012 12:49 AM, "Vinícius Ferrão" <viniciusferrao@××××××××××.br> |
2 |
wrote: |
3 |
> |
4 |
> Hello fellas, |
5 |
> |
6 |
> I'm considering to implement some Gentoo Servers on top of VMWare vSphere |
7 |
ESXi. But perhaps this is not the best option. |
8 |
> |
9 |
> I was googling about performance issues in this scenario and started to |
10 |
consider some OS-Level VT, like OpenVZ or Linux-vserver, or whatever else. |
11 |
> |
12 |
> So I'm here to ask some opinions about virtualization. |
13 |
> |
14 |
> My restricted set of rules (LOL): |
15 |
> 1. I will not run anything else than Linux. |
16 |
> 2. I don't care about GPL, BSD, Icecream, Bacon, or whatever license, |
17 |
since it's free, it's fine. |
18 |
> 3. Don't need to be an Opensource solution. |
19 |
> |
20 |
> Thanks for any help, |
21 |
> |
22 |
|
23 |
I've deployed more than 20 Gentoo servers over VMware and XenServer, no |
24 |
performance issues. |
25 |
|
26 |
From the top of my head, Some pointers when doing menuconfig: |
27 |
|
28 |
* Go "tickless" |
29 |
* Activate the relevant paravirtualization code; choose the |
30 |
hypervisor-friendly suspend instead of spinlock |
31 |
* Use the paravirtualized storage driver (Vmware PV-SCSI or Xen Block |
32 |
FrontEnd) |
33 |
* If using hardened, first configure for "virtualization", exit (and save), |
34 |
menuconfig again, and check the options under GrSec and PaX; there are |
35 |
options that will cause performance penalty when run on top of a hypervisor |
36 |
(see the help text) |
37 |
* Do not compile *any* unnecessary drivers (e.g., wireless support, exotic |
38 |
devices) |
39 |
* Use I/O without delay |
40 |
|
41 |
And, deployment-wise : |
42 |
|
43 |
* When possible, do not create more than one partition per virtual drive; |
44 |
instead, create 1 virtual drive per filesystem mountpoint. E.g. : |
45 |
|
46 |
Instead of having /dev/sda{1,2,3,4} for /boot, /, /usr, and /home, |
47 |
respectively, create 4 virtual drives instead. The above mointpoints will |
48 |
then respectively map to /dev/sd{a,b,c,d}1 |
49 |
|
50 |
(The reason for the latter is because partitions get handled by the VM |
51 |
(slower), while accesses to virtual hard disks are handled by the |
52 |
hypervisor (faster)). |
53 |
|
54 |
I don't have access to my Gentoo systems ATM, so I can't provide a more |
55 |
detailed guide. |
56 |
|
57 |
Rgds, |