General TC > Tiny Core on Virtual Machines

open-vm-tools for VMware

(1/6) > >>

danielibarnes:
I submitted my open-vm-tools extensions, and they are now posted. Since there are at least a half-dozen separate threads on the topic, I am starting a new one to centralize information on the extensions, helpful tips on their usage, and receive feedback on any issues. I tested these extensions with VMware Player 3.1.4 and VMware ESXi 4.1.0 Update 1.

There are seven extensions:

* open-vm-tools, -dev, -modules: tools built with only a glib2 dependency
* open-vm-tools-x, -dev, -modules: tools built with X support and a total of 37 dependencies.
* vm-scsi-2.6.33.3-tinycore: kernel modules for SCSI devices used by VMware guests
Since it doesn't depend on X, the open-vm-tools extension is ideal for Micro Core. It provides kernel modules such as the vmxnet driver for the "Flexible" adapter used by VMware Player. The vmmemctl driver, although no longer a part of open-vm-tools, is built from the last release of open-vm-tools that provided it. The vmtoolsd daemon is started with a script in /usr/local/etc/init.d. It will synchronize time with the host and work with Shared Folders. You can even create a VMware remix of Micro Core.

The open-vm-tools-x extension depends on Xorg, and is a larger package. The extensions plus dependencies total about 40MB. In addition to the features provided by the basic extension, features such as mouse integration, the shared clipboard, Unity, and automatic screen resizing are provided and work as expected. The vmware-user daemon is started automatically when X starts in order to provide this functionality. Instructions for creating a VMware remix of Tiny Core are also available.

Tips:

* Do not run the startup script in /opt/bootlocal.sh with Tiny Core because X may start before the script has had a chance to set up the necessary files.
* The xclip extension is useful with the shared clipboard feature.
* In order to configure the vmxnet interfaces with a static address, be sure to specify the nodhcp bootcode and configure the interface after running the start script.

gutmensch:
Great job, Daniel! I'm using VMWare Workstation a lot with TC, so thank you very much for this extension :)

curaga:
vmxnet is included in the base?

danielibarnes:

--- Quote from: curaga on April 15, 2011, 02:41:41 AM ---vmxnet is included in the base?

--- End quote ---

vmxnet3 is included; vmxnet is not part of the linux kernel. Perhaps because the PCI ID is the same as the pcnet32 module.

athouston:
Also thank you Daniel. I am a long time user of the other operating system and have been using TC to teach myself about the rest of the It world. I've decide to jump from v2 to v3 but I'm still learning Linux. Hence a couple of stupid questions if I may.

I have load open-vm-tools-x and vm-scsi... in a virtual TC session under VMWare Fusion 3 on an iMac 10.6 O/S. Both of these files are listed in the OnBoot Items in AppsAudit.

Apparently the vmtools is running OK because I now don't get an message to load it when I start the session. But the mouse still stays stuck in the session screen unless I manually release it (control-command). I see your reference to the xorg.conf being modified with the mouse "driver=vmmouse" line. My system has an xorg.conf.vesa file. I assume this is what needs modifying (it says "driver=mouse"). Problem is it is R/O. I ran sudo su before starting vi but it is persistently R/O. Is this the correct file and how can I get around the R/O please.

Secondly, in system stats I see the vmxnet loaded but no reference to flexible drive. I assume I don't need to worry about the "blacklist=..." option on startup.

Can you clarify that the nodhcp option is for open-vm-tools-x and that I should modify this to include nodhcp on my dhcp server (because it is static).



Navigation

[0] Message Index

[#] Next page

Go to full version