public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: vmware in Linux 2.6
Date: Fri, 26 Sep 2003 12:56:10 -0700	[thread overview]
Message-ID: <m2oex79vdx.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: 14D30F86678@vcnet.vc.cvut.cz

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

>>>>> "Petr" == Petr Vandrovec <VANDROVE@vc.cvut.cz>:
 Petr> On 26 Sep 03 at 12:50, Mons Rullgord wrote:
 >> "Petr Vandrovec" <VANDROVE@vc.cvut.cz> writes:
 >>
 > Is it possible to use vmware with Linux 2.6?  The kernel modules
 > (obviously) fail to compile.

[...]

 Petr> And except that this patch makes thing compilable, it also makes
 Petr> driver a bit friendlier to the MM subsystem, it allows you to use
 Petr> VMware on 4G/4G host, and it properly handles bridged networking
 Petr> on adapters using hardware (or pseudohardware...) Tx checksumming
 Petr> (although only for IPv4 due to features of dev_queue_xmit_nit).

Does VMware roll these changes back in? This isn't cheap software, I
feel they should care for Linux users a bit more.

For those who run VMware on notebooks with ACPI, another patch is
necessary, otherwise ACPI C-states handling doesn't notice VMware and as
a result the guest system is unbearably slow.

--J.

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-09-26 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26 12:45 vmware in Linux 2.6 Petr Vandrovec
2003-09-26 19:56 ` Jan Rychter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-26 20:46 Petr Vandrovec
2003-09-26 10:25 Petr Vandrovec
2003-09-26 10:50 ` Måns Rullgård
2003-09-26  9:46 Måns Rullgård
2003-09-26 10:28 ` Martin Zwickel
2003-09-26 10:29 ` Sean Neakums
2003-09-26 10:30 ` Helmut Djurkin

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=m2oex79vdx.fsf@tnuctip.rychter.com \
    --to=jan@rychter.com \
    --cc=linux-kernel@vger.kernel.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