Viald, this is CRAZY how well and easy it works...thanks for the tip and the instructions...I think you forgot to mention "conary update kernel" to go from the update 2.2.24 to 2.2.26...I have had no end of problems with 2.6.24 and am happy to be on 2.2.26 as my system hung on "initializing hardware" under 2.2.24.  I'll be overjoyed when OF releases on 2.2.27 for the native SSD support...thanks again Viald!

Thanks for these instructions though I've been struggling to get it working for 32 bit.

Following the instructions got it installed 100% (took quite a while to work out how to re-compile kernel) but none of my VMs wanted to run. The error I got was 'Not enough physical memory is available to power on this virtual machine...'

Seems to be a problem in the vmware-any-any patch for vmmon. Anyway, after a bit of digging, I came across a post where someone provided a patch for VMWare 1.07 for Ubuntu. I tried it, and it works perfectly. The patch can be found here: http://stackoverflow.com/questions/1112 … -to-submit

You should not install the vmware-any-any patch; but you will need to extract the vmmon.tar and vmnet.tar files (both located in /usr/lib/vmware/modules/source) to apply the changes. Don't forget to tar the changes back again before running vmware-config.pl

gpeterson wrote:

Has anyone successfully installed VMWare Server 2.0 on Openfiler 32bit? Thanks.

Not at all, because 64bit release is perfect. Why are you using the 32bit release ?

mmb wrote:

Viald, this is so simple, almost plug and play.  Running Openfiler 2.3 and vmware2 (64bit) and a couple VMs


Thanks!

You're welcome

wolfgang wrote:

I am rerally interested to install vmware server on openfiler 86bit, but my knowledge of linux is low :-)
Well I need a little more help on this. My question, the process described has to be done after a complete install of openfiler baremetal on a x86 box? This means there is also some part from vmware allready installed in the standard openfiler install, because it has to be removed? Could you please help me out and describe the beginning of the procedure more in detail ?

Thanks a lot, Wolfgang

If you need informations regarding Openfiler installation, please consult the WiKi.

can't do this after conary update kernel to 2.6.29
1) install OF
2) unpin the current kernel
3) conary update conary, gcc, updateall, kernel
4) conary erase kernel:vmware
5) install vmware server 2.01
fail because all the symbols are already defined so can't build vmware

after looking at the vmware forums, looks like no one has vmware server running on 2.6.29, although patches are available for vmware workstation.  But those patches have not yet fixed host only networking, but bridged is OK.

Last edited by lukasware (2009-04-30 15:10:28)

OF 64 bit
yes I know that i don't have to update the kernel (see my happy post above on 2.6.26) but I'm a newer is better person...each 2.6 kernel upgrade has been dramatically better for my hardware.  like i said, it's completely broken (but fixable) by patching the vmware server.    Patches are available here: http://www.spryweb.co.uk/vmware-serv...-2.6.29.tar.gz  and better patches here: http://communities.vmware.com/thread/18 … p;tstart=0

Last edited by lukasware (2009-04-30 15:32:12)

lukasware wrote:

and the second patch does not work for me....still tracking this down...

I'm running Vmware 2.01 with kernel 2.6.26.8-1.0.11 (the default given by update all, but not by a kernel update)
The goal of this topic is to run Vmware without touch the default and recommended Openfiler configuration.

I suppose that the release kernel you need will be available one day. And if you want Openfiler support you can't update the kernel like this. (I suppose that adding vmware is already too much ;-)

Thank you.

I appreciate all the efforts and work which has been put in this howto, but why would you want this to begin with?

-Patrick-

Why would you want to install vmware on an OF box?

Ah ok then.
I was more thinking about an enterprise set up. For home usage  it is very useful

Last edited by padonker (2009-05-08 15:43:35)

GRRRR! This is doing my head in!

Iam running OF on a 32 bit machine, so can not use the 64 bit guide above. Also hate VMWare server 2 & above. So sticking with VMWare server 1.0.9 on OF 32 bit.

Anyway, following the above steps, i merrily get to the end of step 2 (Reboot), and I get some errors on boot. No problem, boot with Knoppix, and change grub.conf and fstab to use the paths to the disks instead of labels.

reboot again, and I get kernel panics:

mount: error 6 mounting ext3
ERROR opening /dev/console!!!!:2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic: Attempted to kill init!

Does anyone have any ideas?

I'd also like to understand how I go about recompiling the kernel as per step 3

added after I've gone back to using labels

OK, so I'm using labels in grub.conf and fstab again.

if I boot using the kernel installed when I installed 2.3 (2.6.24.7-0.2.6.smp.gcc3.4.x86.i686) there are no problems.

However, booting using either of the other kernels I've managed to install (2.6.26.6-1.smp.gcc4.1.x86.i686 and 2.6.29.4-0.6.smp.gcc3.4.x86.i686), I hit the same problem:

mkrootdev: label root not found
mounting root filesystem
mount: error 2 mounting ext3
switching to new root
ERROR opening /dev/console!!!!:2


This despite the fact that hda7 is indeed labeled "root", and is the root partition - after all, everything works using 2.6.24!

I've checked the initrd files, the only additional entry in the 2.6.26 file is:

< echo "Loading dock.ko module"
< insmod /lib/dock.ko

otherwise they are identical.

My MB is a Tyan Tiger MPX (2466).

I'm using the on-board IDE controller and also have a 3Ware 9500S-8 installed

Last edited by fcollingwood (2009-06-09 13:22:07)