1 |
On Wed, Dec 31, 2014 at 8:26 AM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Wednesday 31 Dec 2014 12:47:55 Sid S wrote: |
3 |
> |
4 |
> Vbox seems to be coming last by quite some margin in the intel tests! I also |
5 |
> read this article and it looks that vbox is thankfully doing better on AMD; |
6 |
> but there are differences in the versions and kernels used between the two |
7 |
> articles: |
8 |
> |
9 |
|
10 |
I think you need to think about your use case. The requirements were |
11 |
for a workstation testing environment. I think performance (as long |
12 |
as somewhat reasonable) isn't going to be a big concern there vs ease |
13 |
of setup, ability to snapshot, convenience features like being able to |
14 |
group guests, being able to get the right environment easily, etc. |
15 |
You probably also want reasonable graphics performance if you're |
16 |
testing clients inside VMs. If performance makes the difference |
17 |
between being able to run the cluster you need to test on your |
18 |
workstation or not, then that becomes a factor. Otherwise it is a |
19 |
nice-to-have. |
20 |
|
21 |
If you're talking about running servers then performance becomes much |
22 |
more important. However, if you're running linux guests you should |
23 |
seriously consider containers, and if containers aren't the right |
24 |
solution you should also be looking at stuff like VMWare (I don't know |
25 |
how well the FOSS solutions do as far as enterprise-y features go). |
26 |
|
27 |
In any case, while not quite as simple as Virtualbox I've found that |
28 |
virt-manager is very easy to use once you've gotten networking set up |
29 |
(which isn't too hard to do under either openrc or networkd). I tend |
30 |
to use the GUI for setting things up and for graphical guests, and I |
31 |
used to create init.d scripts / units for the stuff that I |
32 |
subsequently moved to containers. You can go back-and-forth between |
33 |
the two (and to be fair you can do the same with virtualbox). One of |
34 |
the advantages of KVM is that it doesn't require tainting your kernel, |
35 |
and you don't have to remember to rebuild the module anytime you |
36 |
update your kernel. I've finally gotten to the point where I don't |
37 |
have any external modules on one of my boxes and I'm very happy with |
38 |
that (alas, my mythtv frontend needs nvidia-drivers - I don't think |
39 |
the hardware acceleration is as good with the kernel drivers though to |
40 |
be fair it has been a year or two since I last tried). |
41 |
|
42 |
-- |
43 |
Rich |