From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which 'tools' package for VMware DomU?
Date: Wed, 30 Mar 2011 18:58:15 -0400 [thread overview]
Message-ID: <4D93B587.6070701@kutulu.org> (raw)
In-Reply-To: <4D937D0F.5090004@kutulu.org>
On 3/30/2011 2:57 PM, Mike Edenfield wrote:
> On 3/30/2011 12:55 PM, Pandu Poluan wrote:
>> Hello, list!
>>
>> I want to deploy some Gentoo-based VMs on VMware. From portage-search,
>> I see some 'tools' related to VMware, namely:
>>
>> * vmware-tools
>>
>> * open-vm-tools
>>
>> * open-vm-tools-kmod
>>
>> What are the differences? And which one should I use if I want to use
>> VMware's PVSCSI and VMXNET?
>
> As I understand things, open-vm-tools is just an open-source version of
> vmware-tools, but uses the same code base and is managed by VMWare. Both
> of them should have the modules you want. Unless you have a compelling
> reason to use the pre-built stuff from the vmware-tools tarball I'd go
> with the open-vm-tools one.
Teach me to read more carefully...
The specific modules you mentioned are included in your kernel already,
assuming you are using at least a 2.6.34 kernel. You'll still want to
install open-vm-tools, which installs the other modules via
open-vm-tools-kmod, like vsock and vmci, plus the user-space daemon.
Device Drivers -->
[*] Misc devices --->
<M> VMware Balloon Driver
SCSI device support --->
[*] SCSI low-level drivers --->
<*> VMware PVSCSI driver support
[*] Network device support
<M> VMware VMXNET3 ethernet driver
(That first one is the vmmemctl driver, which helps improve the memory
management between host & guest).
--Mike
next prev parent reply other threads:[~2011-03-30 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 16:55 [gentoo-user] Which 'tools' package for VMware DomU? Pandu Poluan
2011-03-30 18:57 ` Mike Edenfield
2011-03-30 22:58 ` Mike Edenfield [this message]
2011-03-31 8:31 ` Pandu Poluan
2011-03-31 12:10 ` Mike Edenfield
2011-03-31 12:57 ` Pandu Poluan
2011-04-01 6:09 ` Pandu Poluan
2011-04-01 15:54 ` Mike Edenfield
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=4D93B587.6070701@kutulu.org \
--to=kutulu@kutulu.org \
--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