public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Toughts on Virtualization
Date: Mon, 9 Apr 2012 01:26:34 +0700	[thread overview]
Message-ID: <CAA2qdGW4sOPp2Q0Ujox3Ef-qTccv=9txvsEu808vTWksggXaFw@mail.gmail.com> (raw)
In-Reply-To: <86CEA8B2-BE0D-40DB-A047-604393956FEA@cc.if.ufrj.br>

[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]

On Apr 9, 2012 12:49 AM, "Vinícius Ferrão" <viniciusferrao@cc.if.ufrj.br>
wrote:
>
> Hello fellas,
>
> I'm considering to implement some Gentoo Servers on top of VMWare vSphere
ESXi. But perhaps this is not the best option.
>
> I was googling about performance issues in this scenario and started to
consider some OS-Level VT, like OpenVZ or Linux-vserver, or whatever else.
>
> So I'm here to ask some opinions about virtualization.
>
> My restricted set of rules (LOL):
> 1. I will not run anything else than Linux.
> 2. I don't care about GPL, BSD, Icecream, Bacon, or whatever license,
since it's free, it's fine.
> 3. Don't need to be an Opensource solution.
>
> Thanks for any help,
>

I've deployed more than 20 Gentoo servers over VMware and XenServer, no
performance issues.

From the top of my head, Some pointers when doing menuconfig:

* Go "tickless"
* Activate the relevant paravirtualization code; choose the
hypervisor-friendly suspend instead of spinlock
* Use the paravirtualized storage driver (Vmware PV-SCSI or Xen Block
FrontEnd)
* If using hardened, first configure for "virtualization", exit (and save),
menuconfig again, and check the options under GrSec and PaX; there are
options that will cause performance penalty when run on top of a hypervisor
(see the help text)
* Do not compile *any* unnecessary drivers (e.g., wireless support, exotic
devices)
* Use I/O without delay

And, deployment-wise :

* When possible, do not create more than one partition per virtual drive;
instead, create 1 virtual drive per filesystem mountpoint. E.g. :

Instead of having /dev/sda{1,2,3,4} for /boot, /, /usr, and /home,
respectively, create 4 virtual drives instead. The above mointpoints will
then respectively map to /dev/sd{a,b,c,d}1

(The reason for the latter is because partitions get handled by the VM
(slower), while accesses to virtual hard disks are handled by the
hypervisor (faster)).

I don't have access to my Gentoo systems ATM, so I can't provide a more
detailed guide.

Rgds,

[-- Attachment #2: Type: text/html, Size: 2382 bytes --]

  reply	other threads:[~2012-04-08 18:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-08 17:47 [gentoo-server] Toughts on Virtualization Vinícius Ferrão
2012-04-08 18:26 ` Pandu Poluan [this message]
2012-04-09  2:18   ` Eduardo Schoedler
2012-04-09 16:37     ` Paul Hartman
2012-04-09 16:32   ` Konstantin
2012-04-09 17:31     ` Pandu Poluan
2012-04-10  0:13     ` Hacking Network Solutions - Gentoo List Subscriptions
2012-04-10  0:28       ` Pandu Poluan
2012-04-11  0:42         ` Hacking Networked Solutions - Gentoo List Subscriptions
2012-04-11 14:38       ` Konstantin
2012-04-11 15:17         ` Konstantin
2012-04-11 15:29         ` Hacking Networked Solutions - Gentoo List Subscriptions
2012-04-08 20:21 ` vivo75
2012-04-09 23:46 ` Patrick Nagel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA2qdGW4sOPp2Q0Ujox3Ef-qTccv=9txvsEu808vTWksggXaFw@mail.gmail.com' \
    --to=pandu@poluan.info \
    --cc=gentoo-server@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox