Dear colleagues,
Can you say what the best way to implement VMWare tools into Owl Current? I’m trying to implement this software but have not achieved result.
Best regards
Oleg Malykh
IT Support Department
JSC "Martin Bauer Management"
Phone +7 495 7059376
Fax +7 495 7059373
gsm +7 916 1139938
o.malykh <at> krls.ru
On 12-Nov-2011 07:54:52 +0400, Malykh Oleg wrote: > Can you say what the best way to implement VMWare tools > into Owl Current? I'm trying to implement this software > but have not achieved result. Try installing the RHEL package. -- -- Alexey V. Vissarionov aka Gremlin from Kremlin <gremlin ПРИ gremlin ТЧК ru> GPG key ID: 0xBA52B364, keyserver: hkp://subkeys.pgp.net GPG key fingerprint: 920D 3BCE 930A CF01 A591 541C 6C6D 286E BA52 B364
In any case we need to rebuild kernel. Maybe there is another option to make vmware tools working without rebuilding kernel. 2011/11/12 <gremlin <at> gremlin.ru>: > On 12-Nov-2011 07:54:52 +0400, Malykh Oleg wrote: > > > Can you say what the best way to implement VMWare tools > > into Owl Current? I'm trying to implement this software > > but have not achieved result. > > Try installing the RHEL package. > > > -- > Alexey V. Vissarionov aka Gremlin from Kremlin > <gremlin ПРИ gremlin ТЧК ru> > GPG key ID: 0xBA52B364, keyserver: hkp://subkeys.pgp.net > GPG key fingerprint: 920D 3BCE 930A CF01 A591 541C 6C6D 286E BA52 B364 >
On 12-Nov-2011 20:48:15 +0400, misha shiposh wrote: > In any case we need to rebuild kernel. Maybe there is another > option to make vmware tools working without rebuilding kernel. Does that confuse you? Or are the VMware kernel patches proprietary? > 2011/11/12 <gremlin <at> gremlin.ru>: A: Because it messes up the order in which people normally read text. Q: Why top-posting is considered the most annoying thing in messages? -- -- Alexey V. Vissarionov aka Gremlin from Kremlin <gremlin ПРИ gremlin ТЧК ru> GPG key ID: 0xBA52B364, keyserver: hkp://subkeys.pgp.net GPG key fingerprint: 920D 3BCE 930A CF01 A591 541C 6C6D 286E BA52 B364
On Sat, Nov 12, 2011 at 08:48:15PM +0400, misha shiposh wrote: > In any case we need to rebuild kernel. Why do one need this? VMware modules can be compiled and loaded into the currently running kernel with no issues. Just follow the official VMware procedure in regard to adding their modules into the running kernel. Well, you may need to tweak their Makefile a bit to specify the proper location of the kernel sources. -- -- (GM)
On Mon, Nov 14, 2011 at 9:31 AM, (GalaxyMaster) <galaxy <at> openwall.com> wrote: > On Sat, Nov 12, 2011 at 08:48:15PM +0400, misha shiposh wrote: >> In any case we need to rebuild kernel. > > Why do one need this? VMware modules can be compiled and loaded into > the currently running kernel with no issues. Just follow the official > VMware procedure in regard to adding their modules into the running > kernel. Well, you may need to tweak their Makefile a bit to specify the > proper location of the kernel sources. Anywhere it's not so easy as i expected... We have about 5 or 8 owl in our product virtualization, and as a result i must do this steps on each machine. I just thought that there are anothe way without having to build kernel or modules for installing tools. Thanks for your answer.
Misha, Galaxy - On Mon, Nov 14, 2011 at 11:06:46AM +0400, misha shiposh wrote: > On Mon, Nov 14, 2011 at 9:31 AM, (GalaxyMaster) <galaxy <at> openwall.com> wrote: > > ... VMware modules can be compiled and loaded into > > the currently running kernel with no issues. Just follow the official > > VMware procedure in regard to adding their modules into the running > > kernel. Well, you may need to tweak their Makefile a bit to specify the > > proper location of the kernel sources. > > Anywhere it's not so easy as i expected... > We have about 5 or 8 owl in our product virtualization, and as a > result i must do this steps on each machine. I just thought that there > are anothe way without having to build kernel or modules for > installing tools. It sounds like the two of you could write some tutorials (such as on our wiki) based on your experience with this. Then maybe others in here would be able to propose how to simplify them. I am totally unfamiliar with VMware, so I can't help right now, but having seen the exact steps that you have to take on each machine now I might be able to suggest something or we might even make relevant changes to Owl itself (e.g., reducing the number of customization steps needed for VMware tools). Thanks, Alexander
VMWare tools temporarily show up on the cdrom, after you tell vmware to install vmware tools, so I was searching for the cdrom, but couldn't find it. The /etc/fstab file shows a /dev/cdrom device, but that doesn't exist. Please advise. -Robert Harris -----Original Message----- From: Solar Designer [mailto:solar <at> openwall.com] Sent: Monday, November 14, 2011 6:44 AM To: owl-users <at> lists.openwall.com Subject: Re: [owl-users] VMWare tools Misha, Galaxy - On Mon, Nov 14, 2011 at 11:06:46AM +0400, misha shiposh wrote: > On Mon, Nov 14, 2011 at 9:31 AM, (GalaxyMaster) <galaxy <at> openwall.com> wrote: > > ... VMware modules can be compiled and loaded into > > the currently running kernel with no issues. Just follow the official > > VMware procedure in regard to adding their modules into the running > > kernel. Well, you may need to tweak their Makefile a bit to specify the > > proper location of the kernel sources. > > Anywhere it's not so easy as i expected... > We have about 5 or 8 owl in our product virtualization, and as a > result i must do this steps on each machine. I just thought that there > are anothe way without having to build kernel or modules for > installing tools. It sounds like the two of you could write some tutorials (such as on our wiki) based on your experience with this. Then maybe others in here would be able to propose how to simplify them. I am totally unfamiliar with VMware, so I can't help right now, but having seen the exact steps that you have to take on each machine now I might be able to suggest something or we might even make relevant changes to Owl itself (e.g., reducing the number of customization steps needed for VMware tools). Thanks, Alexander
On Tue, Nov 15, 2011 at 05:44:48PM -0500, Robert Harris wrote: > VMWare tools temporarily show up on the cdrom, after you tell vmware to > install vmware tools, Do you mean that VMware provides a virtual CD-ROM that has the tools on it? (I am just trying to guess.) > The /etc/fstab file shows a /dev/cdrom device, but that doesn't exist. If you need this, you're supposed to make /dev/cdrom a symlink to your actual CD drive device - e.g., with: ln -s hdc /dev/cdrom or: ln -s scd0 /dev/cdrom (see dmesg to determine the device name to use here). Then simple "mount /mnt/cdrom" should work. Alexander
Alex/All, Thanks for the information that works. To answer your question: > VMWare tools temporarily show up on the cdrom, after you tell vmware to > install vmware tools, Do you mean that VMware provides a virtual CD-ROM that has the tools on it? (I am just trying to guess.) Yes, when one tells vmware to "Install VMware tools", the software shows up on the virtual cdrom device (hopefully already created). It is usually a .tar.gz file. You uncompress and unzip it. The zip file has the source code of the VMware tools, and you have to compile them. There is a perl script to compile and install VMware tools, called vmware-install.pl. I really didn't see much need to install VMware tools, since its major benefit is to provide better video and mouse drivers, and "shared" folders with the host machine. Since we don't have X-Windows in owl, the better video and mouse drivers aren't helpful. Since this email chain doesn't actually show the error codes, I tried installing the tools. The following is the error message that occurs: Searching for a valid kernel header path... The path "" is not a valid path to the 2.6.18-238.5.1.el5.028stab085.2.owl2 kernel headers. WARNING: This program cannot compile any modules for the following reason(s)... - This program could not find a valid path to the gcc binary. Please ensure that the gcc binary is installed on this sytem. - This program could not find a valid path to the kernel headers of the running kernel. Please ensure that the header files for the running kernel are installed on this sytem. I attempted to give it the path /usr/bin, but that doesn't work. Can you advise on the solution? -Robert Harris from VA -----Original Message----- From: Solar Designer [mailto:solar <at> openwall.com] Sent: Tuesday, November 15, 2011 6:09 PM To: owl-users <at> lists.openwall.com Subject: Re: [owl-users] VMWare tools On Tue, Nov 15, 2011 at 05:44:48PM -0500, Robert Harris wrote: > VMWare tools temporarily show up on the cdrom, after you tell vmware to > install vmware tools, Do you mean that VMware provides a virtual CD-ROM that has the tools on it? (I am just trying to guess.) > The /etc/fstab file shows a /dev/cdrom device, but that doesn't exist. If you need this, you're supposed to make /dev/cdrom a symlink to your actual CD drive device - e.g., with: ln -s hdc /dev/cdrom or: ln -s scd0 /dev/cdrom (see dmesg to determine the device name to use here). Then simple "mount /mnt/cdrom" should work. Alexander
On Thu, Nov 17, 2011 at 07:42:25PM -0500, Robert Harris wrote: > Searching for a valid kernel header path... > The path "" is not a valid path to the 2.6.18-238.5.1.el5.028stab085.2.owl2 > kernel headers. > > WARNING: This program cannot compile any modules for the following > reason(s)... > > - This program could not find a valid path to the gcc binary. Please ensure > that the gcc binary is installed on this sytem. > > - This program could not find a valid path to the kernel headers of the > running > kernel. Please ensure that the header files for the running kernel are > installed on this sytem. > > I attempted to give it the path /usr/bin, but that doesn't work. > > > Can you advise on the solution? Based on your message only, no. I think that one of us will need to reproduce and debug these issues. Galaxy - maybe you? (I think you were using Owl with VMware before.) Robert - one thing you could try is running those tools under "strace -fF". This should reveal what files they're trying to access. Thanks, Alexander
On Fri, Nov 18, 2011 at 08:22:59PM +0400, Solar Designer wrote: > Based on your message only, no. I think that one of us will need to > reproduce and debug these issues. Galaxy - maybe you? (I think you > were using Owl with VMware before.) I'd love to help, but I migrated the last of my VMware VMs to XenServer about 4 months ago :(, so I have no spare VMware machine to play right now :(. However, I do not recall any issues re: compiling VMware modules for our kernels, except it required to specify proper include paths for the kernel source in the VMware's Makefile. -- -- (GM)
On Fri, Nov 18, 2011 at 08:34:33PM +0400, (GalaxyMaster) wrote: > [...] I do not recall any issues re: compiling VMware > modules for our kernels, except it required to specify proper include > paths for the kernel source in the VMware's Makefile. Oh, kernel source. It sounds like Robert needs to extract and configure a kernel source tree before building VMware modules, then - which makes sense. Perhaps follow the kernel build instructions here: http://openwall.info/wiki/Owl/kernel-build#Non-RPM-ed-kernel-build up to and including the "make oldconfig" command (the actual kernel build doesn't need to be performed - we merely need a source tree configured just like one for our actual kernels). Robert? Alexander
Robert, On Thu, Nov 17, 2011 at 07:42:25PM -0500, Robert Harris wrote: > I really didn't see much need to install VMware tools, since its major > benefit is to provide better video and mouse drivers, and "shared" folders > with the host machine. Since we don't have X-Windows in owl, the better > video and mouse drivers aren't helpful. There is a yummy part in these tools: the vmnet and pvscsi modules which provide more efficient way to work with the virtualised hardware. Also, IIRC, there is a module to interoperate with VMware's client, so you can gracefully shut a VM down. -- -- (GM)
RSS Feed