31 Eki 2006 Sal 16:06 tarihinde, Mark Lord şunları yazmıştı: > My experience with VMware on several recent processors (mostly P-M family) > is that it crawls unless I force this first: > echo 1 > /sys/module/processor/parameters/max_cstate > > So I use a wrapper script around VMware (workstation) to save max_cstate, > set it to 1, and restore it again on exit. Hmm, this seems related to that one[1], without setting max_cstate my processors has some issues :) [1] http://bugme.osdl.org/show_bug.cgi?id=7376 -- S.Çağlar Onur <[email protected]> http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
Attachment:
pgpWkDloyGXGi.pgp
Description: PGP signature
- References:
- 2.6.18 is problematic in VMware
- From: Jan Engelhardt <[email protected]>
- Re: 2.6.18 is problematic in VMware
- From: Jan Engelhardt <[email protected]>
- Re: 2.6.18 is problematic in VMware
- From: Mark Lord <[email protected]>
- 2.6.18 is problematic in VMware
- Prev by Date: Re: [take22 0/4] kevent: Generic event handling mechanism.
- Next by Date: Re: mmaping a kernel buffer to user space
- Previous by thread: Re: 2.6.18 is problematic in VMware
- Next by thread: Re: 2.6.18 is problematic in VMware
- Index(es):