From: "Hong-Gunn Chew" <hgchewML@optusnet.com.au>
To: "'Petr Vandrovec'" <VANDROVE@vc.cvut.cz>
Cc: "'Linux kernel mailing list'" <linux-kernel@vger.kernel.org>,
<riel@conectiva.com.br>
Subject: RE: File corruption when running VMware.
Date: Sat, 27 Apr 2002 01:44:44 +0930 [thread overview]
Message-ID: <000b01c1ed3d$7b87a640$1405a8c0@hgclaptop> (raw)
In-Reply-To: <37A7BD60863@vcnet.vc.cvut.cz>
Hi Petr,
> Hi again,
> one of 2.4.x kernel images available in SuSE's 8.0 has
> patched&enabled
> support for page tables in high memory, and this quickly
> revealed incompatibility between VMware's vmmon page table
> handling and ptes above directly mapped range.
>
> So if you have >890MB of RAM and your kernel is compiled
> with support for pte in high memory, please stop using
> VMware, or reconfigure your
> kernel to not use pte in high memory (4GB config without
> pte-in-highmem is OK). Using pte-in-highmem with vmmon will
> cause kernel oopses and/or
> memory corruption :-(
I do have 1GB of memory. I will try to reconfigure my kernel
and see if there's still a problem.
Thanks for the info!
Cheers,
Hong-Gunn
next prev parent reply other threads:[~2002-04-26 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 15:30 File corruption when running VMware Petr Vandrovec
2002-04-26 16:14 ` Hong-Gunn Chew [this message]
2002-04-26 23:01 ` Andrea Arcangeli
2002-04-26 23:56 ` Andrea Arcangeli
2002-04-27 0:00 ` Andrea Arcangeli
2002-04-27 15:36 ` Andrea Arcangeli
2002-05-03 2:53 ` Memory corruption when running VMware. (was File curruption when running VMware) Hong-Gunn Chew
2002-05-03 8:08 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2002-04-24 10:08 File corruption when running VMware Petr Vandrovec
2002-04-24 3:24 Hong-Gunn Chew
2002-04-24 5:01 ` Rik van Riel
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='000b01c1ed3d$7b87a640$1405a8c0@hgclaptop' \
--to=hgchewml@optusnet.com.au \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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