Tracy R Reed wrote:
Andrew Lentvorski wrote:
I've seen claims both ways but very little hard data. VMWare can do
some very clever stuff that avoids kernel trips/page faults altogether.
Answering my own quote. It looks like th EULA for VMWare forbids
benchmarking. Sigh. When will they learn ...
That *alone* makes me want to dump VMWare. Sigh. I just wish qemu was
a better fit ...
They can't possibly avoid these things for disk/network IO, right?
Disk is a problem for VMWare. No doubt.
However, doesn't Xen do an emulated network card? If so, VMWare and Xen
are probably about the same.
In addition, I was under the impression that VMware was starting to do
JIT compilation of code paths in order to do full state checkpointing of
arbitrary OS's with lower overhead. Once you start doing JIT, they can
start replacing register spills, eliding memory traps, cache misses,
etc. It gets you a pretty solid boost to performance because you can
take advantage of a modern CPU even though all of your code is compiled
for a much older processor.
Now, if you have the full source code for the application and OS, you're
almost always better off recompiling. However, one of the things
virtualization is really good for is running legacy applications.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
