Installing VMware Server on unRAID Box


Recommended Posts

  • 1 month later...
  • Replies 333
  • Created
  • Last Reply

Top Posters In This Topic

Some beginner questions here:

 

It's important for me to be able to also use my unraid fileserver as a dc++ client with a gui. After reading about it, seems like the easiest and most straightforward method for this is to install a linux distro on the box, then load vmware, and install unRAID on a vm.

 

Got a few question about this idea though:

-first of all, is this really the best and easiest way?

-is this going to be a major resource hog? Planned system is this new Supermicro mb with Atom D510, and 2/4 GB memory (advice needed here)

-is there a step-by-step guide for this (or any similar method)?

 

Ty in advance

Link to comment

Some beginner questions here:

 

It's important for me to be able to also use my unraid fileserver as a dc++ client with a gui. After reading about it, seems like the easiest and most straightforward method for this is to install a linux distro on the box, then load vmware, and install unRAID on a vm.

 

Got a few question about this idea though:

-first of all, is this really the best and easiest way?

-is this going to be a major resource hog? Planned system is this new Supermicro mb with Atom D510, and 2/4 GB memory (advice needed here)

-is there a step-by-step guide for this (or any similar method)?

 

Ty in advance

 

I do not personally run unRAID with VMWare but running VMWare on an Atom is, more than likely, going to be painful.  I kn ow running VMWare fusion on my Mac with an XP client can be a major pain in the arse at times and make me want to through the laptop across the room.  I would suggest that you reconsider what motherboard and processor you are going to use.  Probably need a Core 2 Duo or Quad for the best results.

Link to comment
  • 2 weeks later...

Brit, agreed but you need not install slackware to run it in a vm.  You can download a preexisting slackware 13 VM and free vmware player and be on your way very quickly.

 

I used bagsides slackware 12.2 vm for my unraid 4.4.2/vmware server 2.0.1 install and it worked like a charm.  I am not yet running unraid 4.5.1 after one failed attempt at compiling the vmware binaries myself.

 

What would be very helpful is if someone in this community could download bagside slackware 13 vm.  Install all prerequisites, take snapshot, install vmware, verify things work, restore snapshot and redistribute the vm.  If I wanted to get greedy the commands to get the onetime.tgz and realtime.tgz files could even preloaded.  So it's simple as as download and run VM, put vmware server install in a predetermined place, run command to get .tgz, copy .tgzs to tower.  I'd be thrilled with just the prereq part.  I have a hard time finding all prereqs with exact kernel versions matching (but I haven't visited this forum in a month or so either).

 

Regards,

 

--dimes

 

Actually, installing a full slackware distro then installing unRAID on that would be far easier than having to install vmware then unRAID within vmware.

Link to comment
What would be very helpful is if someone in this community could download bagside slackware 13 vm.  Install all prerequisites, take snapshot, install vmware, verify things work, restore snapshot and redistribute the vm.  If I wanted to get greedy the commands to get the onetime.tgz and realtime.tgz files could even preloaded.  So it's simple as as download and run VM, put vmware server install in a predetermined place, run command to get .tgz, copy .tgzs to tower.  I'd be thrilled with just the prereq part.  I have a hard time finding all prereqs with exact kernel versions matching (but I haven't visited this forum in a month or so either).

 

Fantastic idea.  I'm sure I'm only one of a number of folks who would very much appreciate this.

Link to comment
  • 3 weeks later...

Hi,

 

Has anyone had any luck with unraid 4.5.1 and vmware server 2.0.2?

 

I started by creating a vmware guest on my existing ESXi server and installed Slackware 12.2.  I downloaded the updated kernel (2.6.31.12) from kernel.org to match unraid 4.5.1.  After a bit of fiddling with the .config file, I eventually got Slackware 12.2 to boot using the 2.6.31.12 kernel.

 

Unfortunately, the install of vmware server 2.0.2[-203138] didn't go according to plan and there were a few compiler errors (sorry, I didn't record them).  However, a bit of web searching turned up a potential fix at http://blog.mymediasystem.net/uncategorized/vmware-server-2-0-1-installation-howto-for-karmic-koala-x86_64/.  After following the instructions there and applying the patches provided, vmware server now compiles and installs, but it isn't working.  A 'netstat -tulpn' shows that there's nothing listening on ports 8222 or 8333 - which I believe is where I'm meant to administrate vmware server from (eg. http://<myip>:8222/).

 

Anyone else had more luck?

 

Cheers,

Bryan

 

Link to comment

Hi,

 

Has anyone had any luck with unraid 4.5.1 and vmware server 2.0.2?

 

I started by creating a vmware guest on my existing ESXi server and installed Slackware 12.2.  I downloaded the updated kernel (2.6.31.12) from kernel.org to match unraid 4.5.1.  After a bit of fiddling with the .config file, I eventually got Slackware 12.2 to boot using the 2.6.31.12 kernel.

 

Unfortunately, the install of vmware server 2.0.2[-203138] didn't go according to plan and there were a few compiler errors (sorry, I didn't record them).  However, a bit of web searching turned up a potential fix at http://blog.mymediasystem.net/uncategorized/vmware-server-2-0-1-installation-howto-for-karmic-koala-x86_64/.  After following the instructions there and applying the patches provided, vmware server now compiles and installs, but it isn't working.  A 'netstat -tulpn' shows that there's nothing listening on ports 8222 or 8333 - which I believe is where I'm meant to administrate vmware server from (eg. http://<myip>:8222/).

 

Anyone else had more luck?

 

Cheers,

Bryan

 

I believe your install issue may be related to a previous post I made and how VMware server 2.0.2 handles the linux 2.6.31.x kernel.  A user made an automated script to patch the install, which makes things much easier:

 

http://radu.cotescu.com/2009/10/30/how-to-install-vmware-server-2-0-x-on-ubuntu-9-10-karmic-koala/

 

Although I am not running 4.5.1, i was successful in using this patch to get 4.5.3. up and running with the 2.6.32.9 kernel yesterday.  I have not rolled the new unRAID version and VMware server into my production system yet, but I was able to boot with 4.5.3 and navigate the VMware management webpages and create/start a VM on a test system.

 

On a side note, I have always had problems with the VMware management page.  It crashes or stops responding every time I try to create or add another VM.  I always have to reboot my unRAID server to add another VM, which is a pain.

 

Link to comment
  • 3 months later...

Hi,

 

I am new, happy  unraid user and currently trying to get vmware 2.0.2 to work with 4.5.4. So far not successful.

 

Here's what I did so far:

- install slackware 13.1 in VMware session

- 'downgrade' the kernel from 2.6.33.4 to 2.6.32

- install VMware per instructions on page 8 of this thread (including raducotescus 'patch')

- VMware works like a charm on the dev server

- make packages, ensuring to change source path to /lib/modules/2.6.32-smp and dest path to 2.6.32.9-unRAID

- trying to start VMware on prod server and it fails

 

root@unraid-dev:/tmp# /etc/rc.d/init.d/vmware start
Starting VMware services:
   Virtual machine monitor                                 [  OK  ]
   Virtual machine communication interface                 [  OK  ]
   VM communication interface socket family:               [  OK  ]
   Virtual ethernet                                        [  OK  ]
   Bridged networking on /dev/vmnet0                       [  OK  ]
   Host-only networking on /dev/vmnet1 (background)        [  OK  ]
   DHCP server on /dev/vmnet1                              [  OK  ]
   Host-only networking on /dev/vmnet8 (background)        [  OK  ]
   DHCP server on /dev/vmnet8                              [  OK  ]
   NAT service on /dev/vmnet8                              [  OK  ]
   VMware Server Authentication Daemon (background)        [  OK  ]
   Shared Memory Available                                 [  OK  ]
Starting VMware management services:
   VMware Server Host Agent (background)                   [  OK  ]
   VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
   Virtual machines                                        [  OK  ]
root@unraid-dev:/tmp# uname -r
2.6.32-smp
root@unraid-dev:/tmp#

 

Dev server looks ok, now the prod server:

 

root@Tower:/tmp# /etc/rc.d/init.d/vmware start
Starting VMware services:
   Virtual machine monitor                                            failed
   Virtual machine communication interface                            failed
   VM communication interface socket family:                          failed
   Virtual ethernet                                                   failed
Module vmnet is not loaded.  Please verify that it is loaded before
running this script.

root@Tower:/tmp# /etc/rc.d/init.d/vmware start
VMware Server is installed, but it has not been (correctly) configured
for the running kernel. To (re-)configure it, invoke the
following command: /mnt/cache/.custom/vmware/usr/bin/vmware-config.pl.

root@Tower:/tmp# /etc/rc.d/init.d/vmware status
Bridged networking on /dev/vmnet0 is not running
Host network detection is not running
Host-only networking on /dev/vmnet1 is not running
DHCP server on /dev/vmnet1 is not running
Host-only networking on /dev/vmnet8 is not running
DHCP server on /dev/vmnet8 is not running
NAT networking on /dev/vmnet8 is not running
Module vmmon not loaded
Module vmnet not loaded
root@Tower:/tmp#

root@Tower:/tmp# ls /lib/modules/
2.6.32.9-unRAID/
root@Tower:/tmp# ls /lib/modules/2.6.32.9-unRAID/
build@   modules.alias        modules.inputmap   modules.pcimap    source@
extra/   modules.ccwmap       modules.isapnpmap  modules.seriomap
kernel/  modules.dep          modules.ofmap      modules.symbols
misc/    modules.ieee1394map  modules.order      modules.usbmap
root@Tower:/tmp# ls /lib/modules/2.6.32.9-unRAID/misc/
vmci.ko@  vmci.o  vmmon.ko@  vmmon.o  vmnet.ko@  vmnet.o  vsock.ko@  vsock.o
root@Tower:/tmp#

root@Tower:/tmp# uname -r
2.6.32.9-unRAID
root@Tower:/tmp#

 

 

What am I missing here? I understand that the 2.6.32 complied modules should work on the 2.6.32.9 prod kernel. Should I recompile the dev server to 2.6.32.9? How would I change the kernel name to 2.6.32.9-unRAID instead of the default 2.6.32.9-smp to ensure 1:1 naming? Is that even the problem?

 

How can I check, what exactly the problem is on the prod system? Can I 'test' the vm* modules to see if they are basically compatible with the kernel and there is maybe something wrong with the configuration?

 

Appreciate all help

Marco

 

Link to comment

Hi,

 

thanks for the feedback. unfortunately that did not help either. As mentioned, previously I tried the step-by-step from page 8 of this thread, with the raducotescus patch. So, instead of step 4 and 5:

tar zxpf VMware-server*

cd vmware-server-distrib
./vmware-install.pl

 

I did

 

root@unraid-dev:/tmp/raducotescu-vmware-server-linux-2.6.3x-kernel-592e882# ./vmware-server-2.0.x-kernel-2.6.3x-install.sh /tmp

 

with the VMware*tgz in /tmp.

 

That's what I did originally and what worked in that sense, that I have a running vmware instance on my unraid dev-server.

 

Now I tried your method, without using the radu package at all.

 

So, after unpacking the server package

 

tar zxpf VMware-server*

 

I replaced the .tar packages in vmware-server-distrib/lib/modules/source with the ones you provided in the source file. It was succesful in that way, that the vmware instance on the dev server worked fine, but after creating the install packages and copying them over to the production box, I still cannot start vmware on my prod box:

 

root@Tower:/mnt/user/backup# /etc/rc.d/init.d/vmware start
Starting VMware services:
   Virtual machine monitor                                            failed
   Virtual machine communication interface                            failed
   VM communication interface socket family:                          failed
   Virtual ethernet                                                   failed
Module vmnet is not loaded.  Please verify that it is loaded before
running this script.

root@Tower:/mnt/user/backup#

 

 

So, the problem is not getting vmware server 2.0.2 to run on the 2.6.32-smp unraid dev server, but to get it run on the 2.6.32.9-unRAID production server.

 

 

Link to comment

OK, when you create the installer, you must copy these directories and files to the respective path in unRAID Server:

 

/etc/vmware/*.*

/etc/vmware-vix/*.*

/lib/modules/YOUR_KERNEL/vmci.ko

                                  /vmmon.ko

                                  /vmnet.ko

                                  /vsock.ko

                                  /vmci.o

                                  /vmmon.o

                                  /vmnet.o

                                  /vsock.o

 

/usr/lib/vmware-vix/lib/libvixAllProducts.so

Link to comment

UPDATE: thanks for the support. I decided to go back to square one, and set up a 2.6.32.9 based dev system. I probably screwed up the first install, so I'll give it another try.

 

 

 

still not working. I noticed, that there was a screwup with the REALTIME install script. /lib/modules/2.6.32.9-unRAID/misc/v*.ko that should have symblinked to the v*.o in the same directory, were pointing to /lib/modules/2.6.32-smp/misc/v*.o instead. and on my prod box I obviously dont have a /lib/modules/2.6.32-smp directory. so I changed those symlinks:

 

Dev Box:

root@unraid-dev:/lib/modules/2.6.32-smp# ls -lisa
total 3001
352416   1 drwxr-xr-x  4 root root    656 2010-06-24 16:34 ./
16744   0 drwxr-xr-x  5 root root    136 2010-06-24 15:42 ../
352419   0 lrwxrwxrwx  1 root root     23 2010-06-24 15:42 build -> /tmp/patch/linux-2.6.32/
352417   0 drwxr-xr-x 10 root root    240 2010-06-24 15:44 kernel/
368183   0 drwxr-xr-x  2 root root    240 2010-06-24 16:15 misc/
355183 456 -rw-r--r--  1 root root 465037 2010-06-24 16:34 modules.alias
355184 452 -rw-r--r--  1 root root 460021 2010-06-24 16:34 modules.alias.bin
13113   4 -rw-r--r--  1 root root     69 2010-06-24 16:34 modules.ccwmap
   12 240 -rw-r--r--  1 root root 241760 2010-06-24 16:34 modules.dep
   13 340 -rw-r--r--  1 root root 345912 2010-06-24 16:34 modules.dep.bin
13124   4 -rw-r--r--  1 root root   1257 2010-06-24 16:34 modules.ieee1394map
285733   4 -rw-r--r--  1 root root    218 2010-06-24 16:34 modules.inputmap
284939  20 -rw-r--r--  1 root root  19452 2010-06-24 16:34 modules.isapnpmap
285737   4 -rw-r--r--  1 root root     74 2010-06-24 16:34 modules.ofmap
352420  84 -rw-r--r--  1 root root  84092 2010-06-24 15:42 modules.order
   15 284 -rw-r--r--  1 root root 288751 2010-06-24 16:34 modules.pcimap
285740   4 -rw-r--r--  1 root root   1387 2010-06-24 16:34 modules.seriomap
355185 180 -rw-r--r--  1 root root 181048 2010-06-24 16:34 modules.symbols
355186 232 -rw-r--r--  1 root root 234418 2010-06-24 16:34 modules.symbols.bin
   20 693 -rw-r--r--  1 root root 706451 2010-06-24 16:34 modules.usbmap
352418   0 lrwxrwxrwx  1 root root     23 2010-06-24 15:42 source -> /tmp/patch/linux-2.6.32/
root@unraid-dev:/lib/modules/2.6.32-smp# ls -lisa misc
total 213
368183  0 drwxr-xr-x 2 root root   240 2010-06-24 16:15 ./
352416  1 drwxr-xr-x 4 root root   656 2010-06-24 16:34 ../
368148  0 lrwxrwxrwx 1 root root    35 2010-06-24 16:13 vmci.ko -> /lib/modules/2.6.32-smp/misc/vmci.o
368147 60 -rw-r--r-- 1 root root 61054 2010-06-24 16:13 vmci.o
368185  0 lrwxrwxrwx 1 root root    36 2010-06-24 16:13 vmmon.ko -> /lib/modules/2.6.32-smp/misc/vmmon.o
368184 80 -rw-r--r-- 1 root root 80702 2010-06-24 16:13 vmmon.o
368157  0 lrwxrwxrwx 1 root root    36 2010-06-24 16:15 vmnet.ko -> /lib/modules/2.6.32-smp/misc/vmnet.o
368156 52 -rw-r--r-- 1 root root 51250 2010-06-24 16:15 vmnet.o
368129  0 lrwxrwxrwx 1 root root    36 2010-06-24 16:13 vsock.ko -> /lib/modules/2.6.32-smp/misc/vsock.o
368128 20 -rw-r--r-- 1 root root 17237 2010-06-24 16:13 vsock.o
root@unraid-dev:/lib/modules/2.6.32-smp#

 

 

Prod Box:

root@Tower:/lib/modules/2.6.32.9-unRAID# ls -lisa
total 276
  438   0 drwxr-xr-x 5 root root     0 2010-07-02 10:06 ./
  437   0 drwxr-xr-x 3 root root     0 2010-06-24 16:20 ../
257596   0 lrwxrwxrwx 1 root root    15 2010-07-02 10:05 build -> /usr/src/linux//
  441   0 drwxr-xr-x 3 root root     0 2010-05-15 18:13 extra/
  456   0 drwxr-xr-x 6 root root     0 2010-05-15 18:13 kernel/
30267   0 drwxr-xr-x 2 root root     0 2010-07-02 10:02 misc/
  554  64 -rw-r--r-- 1 root root 65199 2010-05-15 18:13 modules.alias
  557   4 -rw-r--r-- 1 root root    69 2010-05-15 18:13 modules.ccwmap
  558   8 -rw-r--r-- 1 root root  6131 2010-05-15 18:13 modules.dep
  559   4 -rw-r--r-- 1 root root    73 2010-05-15 18:13 modules.ieee1394map
  454   4 -rw-r--r-- 1 root root   141 2010-05-15 18:13 modules.inputmap
  552   4 -rw-r--r-- 1 root root    81 2010-05-15 18:13 modules.isapnpmap
  555   4 -rw-r--r-- 1 root root    74 2010-05-15 18:13 modules.ofmap
  556   4 -rw-r--r-- 1 root root  2221 2010-05-15 18:13 modules.order
  561  64 -rw-r--r-- 1 root root 64800 2010-05-15 18:13 modules.pcimap
  560   4 -rw-r--r-- 1 root root    43 2010-05-15 18:13 modules.seriomap
  455  12 -rw-r--r-- 1 root root  9165 2010-05-15 18:13 modules.symbols
  439 100 -rw-r--r-- 1 root root 98472 2010-05-15 18:13 modules.usbmap
257172   0 lrwxrwxrwx 1 root root    15 2010-07-02 10:03 source -> /usr/src/linux//
root@Tower:/lib/modules/2.6.32.9-unRAID# ls -lisa misc
total 212
30267  0 drwxr-xr-x 2 root root     0 2010-07-02 10:02 ./
  438  0 drwxr-xr-x 5 root root     0 2010-07-02 10:06 ../
256644  0 lrwxrwxrwx 1 root root     6 2010-07-02 10:01 vmci.ko -> vmci.o
256450 60 -rw-r--r-- 1 root root 61054 2010-06-24 16:13 vmci.o
256721  0 lrwxrwxrwx 1 root root     7 2010-07-02 10:01 vmmon.ko -> vmmon.o
256451 80 -rw-r--r-- 1 root root 80702 2010-06-24 16:13 vmmon.o
256763  0 lrwxrwxrwx 1 root root     7 2010-07-02 10:01 vmnet.ko -> vmnet.o
256452 52 -rw-r--r-- 1 root root 51250 2010-06-24 16:15 vmnet.o
256810  0 lrwxrwxrwx 1 root root     7 2010-07-02 10:02 vsock.ko -> vsock.o
256453 20 -rw-r--r-- 1 root root 17237 2010-06-24 16:13 vsock.o
root@Tower:/lib/modules/2.6.32.9-unRAID#

 

 

 

etc directories Dev

root@unraid-dev:/# ls -lisa /etc/vmware/
total 781
355196   0 drwxr-xr-x 10 root root    464 2010-06-24 16:16 ./
361956   0 drwxr-xr-x  4 root root    104 2010-06-24 16:17 ../
368079   4 -rw-r--r--  1 root root   1073 2010-06-24 16:16 config
361928   1 drwxr-xr-x  3 root root    736 2010-06-25 05:09 hostd/
355195   0 lrwxrwxrwx  1 root root     44 2010-06-24 16:16 icu -> /mnt/cache/.custom/vmware/usr/lib/vmware/icu/
361955  28 -r-xr-xr-x  1 root root  27879 2010-06-24 16:11 installer.sh*
368114   4 -rw-r--r--  1 root root   2535 2010-06-25 05:09 license.cfg
368082   4 -rw-r--r--  1 root root    559 2010-06-24 16:15 license.vs.1.0-00
361927 737 -rw-r--r--  1 root root 749972 2010-06-24 16:16 locations
368037   4 -rw-r--r--  1 root root    242 2010-06-24 16:14 netmap.conf
361951   0 drwxr-xr-x  2 root root     80 2010-06-24 16:11 pam.d/
361953   0 drwxr-xr-x  2 root root     80 2010-06-24 16:11 service/
368051   0 drwxr-xr-x  2 root root     96 2010-06-24 16:15 ssl/
368080   0 drwxr-xr-x  2 root root     72 2010-06-24 16:15 state/
368045   0 drwxr-xr-x  3 root root     72 2010-06-24 16:14 vmnet1/
368038   0 drwxr-xr-x  4 root root     96 2010-06-24 16:14 vmnet8/
368061   0 drwxr-xr-x  2 root root    144 2010-06-24 16:15 webAccess/
root@unraid-dev:/# ls -lisa /etc/vmware-vix
368084 0 lrwxrwxrwx 1 root root 40 2010-06-24 16:17 /etc/vmware-vix -> /mnt/cache/.custom/vmware/etc/vmware-vix/
root@unraid-dev:/# ls -lisa /mnt/cache/.custom/vmware/etc/vmware-vix/
total 68
368490  0 drwxr-xr-x 2 root root   112 2010-06-24 16:15 ./
361956  0 drwxr-xr-x 4 root root   104 2010-06-24 16:17 ../
368492 28 -r-xr-xr-x 1 root root 27880 2010-06-24 16:15 installer.sh*
368491 40 -rw-r--r-- 1 root root 40507 2010-06-24 16:16 locations
root@unraid-dev:/#

 

 

etc directory Prod

root@Tower:/lib/modules/2.6.32.9-unRAID# ls -lisa /etc/vmware/
total 781
  7   0 drwxr-xr-x 10 root root    464 2010-07-02 10:07 ./
  6   0 drwxr-xr-x  4 root root    104 2010-06-24 16:17 ../
 49   4 -rw-r--r--  1 root root   1073 2010-06-24 16:16 config
 11   1 drwxr-xr-x  3 root root    736 2010-06-24 16:17 hostd/
7202   0 lrwxrwxrwx  1 root root     44 2010-07-02 09:59 icu -> /mnt/cache/.custom/vmware/usr/lib/vmware/icu/
 48  28 -r-xr-xr-x  1 root root  27879 2010-06-24 16:11 installer.sh*
 64   4 -rw-r--r--  1 root root   2535 2010-06-24 16:16 license.cfg
 47   4 -rw-r--r--  1 root root    559 2010-06-24 16:15 license.vs.1.0-00
 51 737 -rw-r--r--  1 root root 750144 2010-07-02 10:07 locations
 65   4 -rw-r--r--  1 root root    242 2010-06-24 16:14 netmap.conf
 41   0 drwxr-xr-x  2 root root     80 2010-06-24 16:11 pam.d/
 45   0 drwxr-xr-x  2 root root     80 2010-06-24 16:11 service/
  8   0 drwxr-xr-x  2 root root     96 2010-06-24 16:15 ssl/
 43   0 drwxr-xr-x  2 root root     72 2010-06-24 16:15 state/
 52   0 drwxr-xr-x  3 root root     72 2010-06-24 16:14 vmnet1/
 57   0 drwxr-xr-x  4 root root     96 2010-06-24 16:14 vmnet8/
 50   0 drwxr-xr-x  2 root root    144 2010-07-02 09:59 webAccess/
root@Tower:/lib/modules/2.6.32.9-unRAID# ls -lisa /etc/vmware-vix/
total 68
66  0 drwxr-xr-x 2 root root   112 2010-06-24 16:15 ./
6  0 drwxr-xr-x 4 root root   104 2010-06-24 16:17 ../
67 28 -r-xr-xr-x 1 root root 27880 2010-06-24 16:15 installer.sh*
68 40 -rw-r--r-- 1 root root 40507 2010-06-24 16:16 locations
root@Tower:/lib/modules/2.6.32.9-unRAID#

 

 

Dont have a /usr/lib/vmware-vix/lib/libvixAllProducts.so file on the dev box. Looked for the name:

 

Dev

root@unraid-dev:/# ls -lisa /lib/libvixAllProducts.so
368617 0 lrwxrwxrwx 1 root root 69 2010-06-24 16:16 /lib/libvixAllProducts.so -> /mnt/cache/.custom/vmware/usr/lib/vmware-vix/lib/libvixAllProducts.so*
root@unraid-dev:/# ls -lisa /mnt/cache/.custom/vmware/usr/lib/vmware-vix/lib/libvixAllProducts.so
368534 689 -rwxr-xr-x 1 root root 702380 2010-06-24 16:16 /mnt/cache/.custom/vmware/usr/lib/vmware-vix/lib/libvixAllProducts.so*
root@unraid-dev:/#

 

 

Prod

root@Tower:/lib/modules/2.6.32.9-unRAID# ls -lisa /lib/libvixAllProducts.so
256476 0 lrwxrwxrwx 1 root root 69 2010-07-02 10:00 /lib/libvixAllProducts.so -> /mnt/cache/.custom/vmware/usr/lib/vmware-vix/lib/libvixAllProducts.so*
root@Tower:/lib/modules/2.6.32.9-unRAID# ls -lisa /mnt/cache/.custom/vmware/usr/lib/vmware-vix/lib/libvixAllProducts.so
7116 689 -rwxr-xr-x 1 root root 702380 2010-06-24 16:16 /mnt/cache/.custom/vmware/usr/lib/vmware-vix/lib/libvixAllProducts.so*
root@Tower:/lib/modules/2.6.32.9-unRAID#

 

 

so, a couple of differences to your path names. The v*o are not in /lib/modules/<kernel>/ but in /lib/modules/<kernel>/misc and the libvixAllProducts.so is not in /usr/lib/vmware-vix/lib/ but in /lib/

 

As it is identical on both the dev and the prod box though, that should be ok, right?

 

The only difference I see between dev and prod is that the symbolic links for the v*.ko files include the full path on the dev and only the name on the prod box. hmmmm

 

Link to comment
  • 4 weeks later...

Thanks to the great instructions from musicmann, WeeboTech and bubbaQ, I managed to compile VMware Server 2.0.2 on a Slack dev system (based on 12.2) on the most recent 4.5.6 kernel, 2.6.32.9-unRAID. Made the packages and everything's properly installed on a spare drive in my unRaid production box running off USB. Seriously, it's been many years since I had to compile a kernel and the clues about getting the right IDE/SATA drivers for booting were very useful.

 

My issue is with PAM. I've scoured these forums and others to figure out why my login as root is still being rejected. I have tried 4 different versions of pam — 0.99.10, 1.0.2, 1.0.4, 1.1.0, with no luck. All the VM modules start properly, and my error shows that the login is being rejected, not that it can't load the pam libs or configs, etc.

 

I've seen a few slackware/vmware-related threads where people solved it by either removing the third line from the config ("account required"), adding "shadow nullok" to the end of the second line, etc. I've tried these things but no luck. I noticed there's also pam config files in /etc/vmware/pam.d.. anyone know if these should be modified in any way?

 

I've found two slack threads where a confirmed solution is posted to a pastebin or some other forum two years ago, but of course those sites are disappeared by now.

 

 

It doesn't seem like I *should* have to modify the config files at all, because any issues that have come up on this thread have just required installing a specific version of pam and that's it. I'm wondering if there could be some issue with the fact that I'm running a more recent kernel than was available when most of the activity was happening in this thread (2008). Because otherwise the dev system and pam versions are the same, and my config files point to the right place. The only other thing I'm considering trying is just compiling and installing pam myself.

 

Or is it even possible that in recompiling the more recent kernel, I managed to leave out some option that PAM requires support for? I'd hope that if this were the case, the libraries would fail to load in the first place and would indicate in the error log.

 

 

Any ideas would be extremely helpful!

Link to comment

So, having read in the other thread that SysV is supported in recent unRaid kernels:

http://lime-technology.com/forum/index.php?topic=6939.msg69860#msg69860

 

I downloaded VirtualBox on my dev system. Steps:

 

1. Executed the downloaded .run file. VirtualBox was unpacked and modules were built once I pointed it to the default kernel source directory at /usr/src/linux, containing the matching kernel.

 

2. I created a Windows XP vm using a few VBoxManage commands.

 

3. Started the vm using VBoxHeadless.

 

 

That's it. It works flawlessly so far. I'm only interested in bridged ethernet and so that's all I've tried as far as networking, but it works great. I installed VirtualBox additions later by using the included .iso file.

 

I haven't tried running it on the stock unRaid, so I would need to look at how it's possible to manage any temp directories and possibly swapfiles. What's nice is that the install seems to keep everything in one place (/opt/VirtualBox). VM disks get created where you choose to put them, and the VM XML files get created by default in .VirtualBox in the root user directory. Seems easily manageable — the install footprint is about 100 MB. Creating VMs in command-line is probably more tedious than using a web interface like VMware, but I like the simplicity of it.

Link to comment

Thanks to the great instructions from musicmann, WeeboTech and bubbaQ, I managed to compile VMware Server 2.0.2 on a Slack dev system (based on 12.2) on the most recent 4.5.6 kernel, 2.6.32.9-unRAID. Made the packages and everything's properly installed on a spare drive in my unRaid production box running off USB. Seriously, it's been many years since I had to compile a kernel and the clues about getting the right IDE/SATA drivers for booting were very useful.

 

My issue is with PAM. I've scoured these forums and others to figure out why my login as root is still being rejected. I have tried 4 different versions of pam — 0.99.10, 1.0.2, 1.0.4, 1.1.0, with no luck. All the VM modules start properly, and my error shows that the login is being rejected, not that it can't load the pam libs or configs, etc.

 

I've seen a few slackware/vmware-related threads where people solved it by either removing the third line from the config ("account required"), adding "shadow nullok" to the end of the second line, etc. I've tried these things but no luck. I noticed there's also pam config files in /etc/vmware/pam.d.. anyone know if these should be modified in any way?

 

I've found two slack threads where a confirmed solution is posted to a pastebin or some other forum two years ago, but of course those sites are disappeared by now.

 

 

It doesn't seem like I *should* have to modify the config files at all, because any issues that have come up on this thread have just required installing a specific version of pam and that's it. I'm wondering if there could be some issue with the fact that I'm running a more recent kernel than was available when most of the activity was happening in this thread (2008). Because otherwise the dev system and pam versions are the same, and my config files point to the right place. The only other thing I'm considering trying is just compiling and installing pam myself.

 

Or is it even possible that in recompiling the more recent kernel, I managed to leave out some option that PAM requires support for? I'd hope that if this were the case, the libraries would fail to load in the first place and would indicate in the error log.

 

I vaguely remember some issues with PAM when I first started using this a year ago.  I currently use the PAM .99 version musicman points to in his guide - http://repository.slacky.eu/slackware-12.0/system/linux-pam/0.99.10.0/linux-pam-0.99.10.0-i486-1gufo.tgz

 

I had VMware running on 4.5.6 on my test box, so I do know it is possible.  (Running 4.5 on my live box - too lazy to upgrade it).  And no, you should not have to tweak any PAM settings or any other configuration settings for that matter.  I did use Slackware 13.0 when compiling my dev box, but that really shouldn't matter.

 

I also remember some odd password issue the first time I tried setting it up.  This was due to using a different password on the dev box versus the live box.  Try using whatever password you set up on the dev box and see if that lets you in. 

 

Link to comment

I had VMware running on 4.5.6 on my test box, so I do know it is possible.  (Running 4.5 on my live box - too lazy to upgrade it).  And no, you should not have to tweak any PAM settings or any other configuration settings for that matter.  I did use Slackware 13.0 when compiling my dev box, but that really shouldn't matter.

 

Looks like I might have spoke too soon on the 4.5.6 compatibility.  I just tried to fire this up on my production system and I cannot get the webAccess for VMware to load at all (hangs on loading...).  Everything looks like it loads and starts up, but I cannot access the management console.  I am not overly familiar with the command line tools for VMware, so I'll have to dig into those to see if I can get things added and booted up without the GUI.

 

Based upon my documentation and test system, it looks like I compiled and tested everything out for 4.5.3 and had no issues.  I do not believe there have been any kernel changes to unRAID since that version and that has always been the requirement for recompiling the packages.  Usually the VMware process will not start if there are serious errors, but everything loads correctly, just an issue with the webAccess portion.

 

Some quick digging around yields a suggestion to change a configuration file for VMware (http://www.geekprojects.org/2009/08/logging-into-a-vmware-server-stuck-on-the-loading-page/) to get past the loading page issue, but that throws another error that requires VMware to be reconfigured, which requires perl, which means I need to recompile everything in the test environment.

 

I am really not sure what changed between 4.5.3 and 4.5.6 that broke VMware functionality.  If anyone has any ideas or has gotten past this issue, please let me know.

 

Link to comment

SUCCESS!!!!

 

I got the webAccess portion working after tweaking the noproxy setting in my previous post!  Initially I was trying to edit it with VI, but evidently I corrupted the file and the VMware install.

 

The file that needs to be edited is in /mnt/cache/.etc/vmware/webAccess and is called proxy.properties  Change the proxy.noCache = false to proxy.noCache = true  then restart the VMware server (or reboot the whole server).  I edited the file in WordPad.

 

So, it looks like 4.5.6 works fine with VMware as long as you tweak one additional file.

 

Link to comment

I vaguely remember some issues with PAM when I first started using this a year ago.  I currently use the PAM .99 version musicman points to in his guide - http://repository.slacky.eu/slackware-12.0/system/linux-pam/0.99.10.0/linux-pam-0.99.10.0-i486-1gufo.tgz

 

I had VMware running on 4.5.6 on my test box, so I do know it is possible.  (Running 4.5 on my live box - too lazy to upgrade it).  And no, you should not have to tweak any PAM settings or any other configuration settings for that matter.  I did use Slackware 13.0 when compiling my dev box, but that really shouldn't matter.

 

I also remember some odd password issue the first time I tried setting it up.  This was due to using a different password on the dev box versus the live box.  Try using whatever password you set up on the dev box and see if that lets you in. 

 

Thanks for those suggestions. I finally cracked it, and am embarrassed I didn't find the solution much, much sooner (before even trying VirtualBox). I didn't notice until now the vmware folder in /var/log, and when I checked the hostd log, I saw that PAM wasn't being loaded due to missing libraries. PAM was installed fine all along, but I needed to install five other dependency libraries it was needing to run. It's too bad it didn't log that error to syslog, considering it breaks the entire VMware management subsystem! I now have these packages running in my go script, notice that I'm using pam 1.1.0:

 

 

installpkg /boot/packages/gnutls-2.2.2-i486-1sl.tgz

installpkg /boot/packages/libgpg-error-1.4-i486-1.tgz

installpkg /boot/packages/libtasn1-1.7-i486-1sl.tgz

installpkg /boot/packages/libgcrypt-1.2.4-i486-1.tgz

installpkg /boot/packages/libprelude-0.9.22-i486-1sl.tgz

installpkg /boot/packages/linux-pam-1.1.0-i486-1gufo.txz

 

I don't know if these packages would have been installed already on others systems.. or as part of a full dev system. My dev system probably was failing for the same reason, but I may have somehow left out those packages on it.

 

VMware turns out to be the best option for me, at least for now, anyway. My main reason for needing a VM was to consolidate my music library by managing it with iTunes, so it's accessible and modifiable via iTunes shares and the smb share.

 

My CPU is so old it doesn't support VT-x, and recent iTunes versions won't run under VBox without VT-x, at least not on my system, after trying various workarounds that work for some and not others. Under VMware the issue isn't there.

 

Although I now realize that it's time to spend the $50 and upgrade the CPU to something more substantial :)

Link to comment

SUCCESS!!!!

 

I got the webAccess portion working after tweaking the noproxy setting in my previous post!  Initially I was trying to edit it with VI, but evidently I corrupted the file and the VMware install.

 

The file that needs to be edited is in /mnt/cache/.etc/vmware/webAccess and is called proxy.properties   Change the proxy.noCache = false to proxy.noCache = true  then restart the VMware server (or reboot the whole server).  I edited the file in WordPad.

 

So, it looks like 4.5.6 works fine with VMware as long as you tweak one additional file.

 

 

Interesting, I never needed to tweak this for things to work, however I did sometimes experience a hang of the login screen if there had already been another session started in a different browser. When that happened, I would just restart the vmware init.d, which was easy enough since I'm only trying to manage a single VM, at least for now.

Link to comment
  • 2 weeks later...
  • 3 weeks later...

Can some one please help me. I have set up my first development system. I am tring to install VMware server. I have compiled and installed the 2.6.32.9 kernal. Whie configuring VMware I get the following message

 

bash-3.1# /mnt/cache/.vmware/usr/bin/vmware-config.pl

Making sure services for VMware Server are stopped.

 

Stopping VMware autostart virtual machines:

  Virtual machines                                        [FAILED]

Stopping VMware management services:

  VMware Virtual Infrastructure Web Access

  VMware Server Host Agent                                [FAILED]

Stopping VMware services:

  VMware Authentication Daemon                            [  OK  ]

  Virtual machine monitor                                [  OK  ]

 

None of the pre-built vmmon modules for VMware Server is suitable for your

running kernel.  Do you want this program to try to build the vmmon module for

your system (you need to have a C compiler installed on your system)? [yes]

 

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

 

What is the location of the directory of C header files that match your running

kernel? [/lib/modules/2.6.32.9-smp/build/include] /usr/src/linux-2.6.32.9/include

 

Extracting the sources of the vmmon module.

 

Building the vmmon module.

 

Unknown VMware Server 2.0.2 build 203138 detected. Building for Server 1.0.0.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config10/vmmon-only'

make -C /usr/src/linux-2.6.32.9/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.32.9'

  CC [M]  /tmp/vmware-config10/vmmon-only/linux/driver.o

In file included from /tmp/vmware-config10/vmmon-only/./include/x86.h:21,

                from /tmp/vmware-config10/vmmon-only/linux/driver.h:15,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:53:

/tmp/vmware-config10/vmmon-only/./include/x86apic.h:80:1: warning: "APIC_BASE_MSR" redefined

In file included from /usr/src/linux-2.6.32.9/arch/x86/include/asm/apic.h:11,

                from /usr/src/linux-2.6.32.9/arch/x86/include/asm/smp.h:13,

                from include/linux/smp.h:36,

                from include/linux/topology.h:33,

                from include/linux/gfp.h:7,

                from include/linux/kmod.h:22,

                from include/linux/module.h:13,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:16:

/usr/src/linux-2.6.32.9/arch/x86/include/asm/apicdef.h:136:1: warning: this is the location of the previous definition

In file included from /tmp/vmware-config10/vmmon-only/./include/x86.h:24,

                from /tmp/vmware-config10/vmmon-only/linux/driver.h:15,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:53:

/tmp/vmware-config10/vmmon-only/./include/x86paging.h:61:1: warning: "PTE_PFN_MASK" redefined

In file included from /usr/src/linux-2.6.32.9/arch/x86/include/asm/processor.h:19,

                from include/linux/prefetch.h:14,

                from include/linux/list.h:6,

                from include/linux/module.h:9,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:16:

/usr/src/linux-2.6.32.9/arch/x86/include/asm/pgtable_types.h:182:1: warning: this is the location of the previous definition

In file included from /tmp/vmware-config10/vmmon-only/./include/vmci_kernel_defs.h:26,

                from /tmp/vmware-config10/vmmon-only/./common/vmciContext.h:19,

                from /tmp/vmware-config10/vmmon-only/linux/driver.h:21,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:53:

/tmp/vmware-config10/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined

/tmp/vmware-config10/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined

In file included from /tmp/vmware-config10/vmmon-only/./include/vmci_kernel_defs.h:26,

                from /tmp/vmware-config10/vmmon-only/./common/vmciContext.h:19,

                from /tmp/vmware-config10/vmmon-only/linux/driver.h:21,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:53:

/tmp/vmware-config10/vmmon-only/./include/compat_wait.h:60: error: conflicting types for 'poll_initwait'

include/linux/poll.h:70: error: previous declaration of 'poll_initwait' was here

In file included from /tmp/vmware-config10/vmmon-only/linux/vmhost.h:13,

                from /tmp/vmware-config10/vmmon-only/linux/driver.c:84:

/tmp/vmware-config10/vmmon-only/./include/compat_semaphore.h:5:27: error: asm/semaphore.h: No such file or directory

/tmp/vmware-config10/vmmon-only/linux/driver.c:171: error: unknown field 'nopage' specified in initializer

/tmp/vmware-config10/vmmon-only/linux/driver.c:172: warning: initialization from incompatible pointer type

/tmp/vmware-config10/vmmon-only/linux/driver.c:175: error: unknown field 'nopage' specified in initializer

/tmp/vmware-config10/vmmon-only/linux/driver.c:176: warning: initialization from incompatible pointer type

/tmp/vmware-config10/vmmon-only/linux/driver.c: In function 'LinuxDriver_Open':

/tmp/vmware-config10/vmmon-only/linux/driver.c:558: error: 'struct task_struct' has no member named 'euid'

/tmp/vmware-config10/vmmon-only/linux/driver.c: In function '__LinuxDriver_Ioctl':

/tmp/vmware-config10/vmmon-only/linux/driver.c:1495: error: 'struct task_struct' has no member named 'suid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1496: error: 'struct task_struct' has no member named 'cap_permitted'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1761: error: 'struct task_struct' has no member named 'euid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1761: error: 'struct task_struct' has no member named 'uid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1762: error: 'struct task_struct' has no member named 'fsuid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1762: error: 'struct task_struct' has no member named 'uid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1763: error: 'struct task_struct' has no member named 'egid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1763: error: 'struct task_struct' has no member named 'gid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1764: error: 'struct task_struct' has no member named 'fsgid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1764: error: 'struct task_struct' has no member named 'gid'

/tmp/vmware-config10/vmmon-only/linux/driver.c:1781: error: too many arguments to function 'smp_call_function'

make[2]: *** [/tmp/vmware-config10/vmmon-only/linux/driver.o] Error 1

make[1]: *** [_module_/tmp/vmware-config10/vmmon-only] Error 2

make[1]: Leaving directory `/usr/src/linux-2.6.32.9'

make: *** [vmmon.ko] Error 2

make: Leaving directory `/tmp/vmware-config10/vmmon-only'

Unable to build the vmmon module.

 

For more information on how to troubleshoot module-related problems, please

visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and

"http://www.vmware.com/go/unsup-linux-tools".

 

Execution aborted.

 

I have tried installing the patches from gfjardim but have had no luck so far. Any other suggestions.

 

Thanks

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.