That seems like an unholy amount of time, even for a virtual machine. We
use VMWare here and on even our most modest and sluggish VMWare machine it
doesn't take more than an hour to compile a kernel. At home on my stinky
Pentium 4 system it takes maybe 45 minutes to do it.
I would suspect that the delay is not from VMWare itself but the system
it's running on. I've noticed that the virtual machines we have here that
run off servers with slower disk access tend to get sluggish by orders of
magnitude as the system, in general, gets loaded. Fast disk access with
VMWare is extremely important. Mucho memory is important to avoid swapping.
-Matt
On Tue, 11 Mar 2008 16:41:37 -0700, Paul G. Allen
<[EMAIL PROTECTED]> wrote:
I've never dealt with VMWare until recently so I'm not familiar with it.
I think there's a few on the list that are.
I asked the admin at our data center to compile a new CentoOS 5 kernel
for one of our systems so that it would support a module I need for AVG.
He got it done, but it took him 5 hours to do it. He said half the time
was waiting for it to do its thing, the other half was actual work. He
did not compile the module I need (that's for me to do).
I've compiled many kernels and on the slower machines it takes about 20
minutes. Why does it take so long with a VMWare hosted virtual machine?
TIA,
PGA
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
