From: Chris Cox <onebeer@bluebottle.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Vmware modules doesn't build for gentoo-2.6.9-gentoo-r3 kernel
Date: Tue, 7 Dec 2004 03:16:12 -0600 [thread overview]
Message-ID: <200412070316.12228.onebeer@bluebottle.com> (raw)
In-Reply-To: <20041206234736.5B9ED9AF2F@web.private.deploylinux.net>
On Monday 06 December 2004 05:47 pm, Matthew Marlowe wrote:
> >> \x01
> >>
> >> >>What is the location of the directory of C header files that match
> >> >> your running
> >> >>kernel? [/lib/modules/2.6.9-gentoo-r3/build/include]
>
> The above is the correct syntax. We are using similiar g.d.s. kernels for
> vmware GSX here. However, you probably want to switch to the ck kernel tree
> as it has patches to fix oom-killer and other vmware sensitive bugs.
> Otherwise, your you may find virtual machines being killed off for no
> reason during high util.
>
> I don't know why the modules weren't building for you.
>
I posted that question on 9 Nov, since then I've updated my kernel at least
twice. And the problem has been corrected. I don't know people are just now
sending replies to this thread.
Chris
--
ICQ: 5255916 IRC: freenode.net #gentoo
Linux 2.6.9-gentoo-r6 i686 AMD Athlon(tm) XP
3:12am up 8 days, 9:18, load average: 3.35, 2.75, 2.32
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2004-12-07 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 23:47 Re: [gentoo-user] Vmware modules doesn't build for gentoo-2.6.9-gentoo-r3 kernel Matthew Marlowe
2004-12-07 9:16 ` Chris Cox [this message]
2004-12-07 20:15 ` Martin Larsson
2004-12-07 20:33 ` Martin Larsson
2004-12-07 22:01 ` Chris Cox
[not found] <200411091158.14936.onebeer32@hotmail.com>
2004-12-06 21:25 ` Martin Larsson
2004-12-06 23:02 ` Bastian Balthazar Bux
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=200412070316.12228.onebeer@bluebottle.com \
--to=onebeer@bluebottle.com \
--cc=gentoo-user@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