The OSE version is no more. There is only one.

2 members found this post helpful.

Nice to know!

Then there is no reason for trying to compile VirtualBox in a 64 bit environment unless you have specific needs or are just experimenting.

That was the key peice missing from my understanding of "why" - obvious when you think about it...

Which seems to be what everyone was doing as indicated in other threads and looks like the best way to go.

But still I was hoping to find a Slackbuild that repackaged the output of the installer as many others do.

This also had eluded me, I still had OSE in the back of the brain from earlier installs, now I know...

Thanks to all - sorry for the thread hijack.

I have also been playing around with choosing different templates. I found that with the generic Linux 64 template, you will have no access to other NIC then the e1000. I did not find a way to add them manually. In other words, it seems the templates do have some "magic"

and all these problems above, made me happy that I use VMware.

later you will have issues with videodrivers, etc on VirtualBox

Oops...

Don't know on what I was on when I read this thread and posted. I'm also using VMware and not Virtualbox!

@bartgymnast: what template do you advice for VMware and Slackware 14.1?

A 64-bit box, install 64-bit VirtualBox (from http://download.virtualbox.org/virtu...inux_amd64.run). Be sure to get the Extension Pack (http://download.virtualbox.org/virtu...5.vbox-extpack).

Read the instructions.

That VirtualBox installs and functions properly on Slackware 64-bit 14.0 and 14.1.

You can then install any 32-bit or 64-bit OS as a guest in that 64-bit installation.

You do not need nor do you require Multilib to install or use 64-bit VirtualBox.

You can install 32-bit VirtualBox on a 64-bit machine but... why?

In spite of the religious controversy about the binary version or the compile-it-yourself version, the one from Oracle works the other way sometimes has problems with useful things like USB... I prefer "works," you mileage may vary.

Hope this helps some.

+1. No problem to run a 64 bit VM on a 32 bit host, easier to manage, and doesn't make my Thinkpad overheat as VirtualBox does.

The are some limitations though, for instance of video drivers that in some case do not honor "nomodeset", but all in all I find VMplayer pretty handy.

If a software is able to overheat your machine there is a flaw in that machine's cooling system. Virtualbox can not go for more then 100% CPU load, which your cooling system should be able to handle, regardless which software runs the CPU at 100%.

Having said that, I use both, Virtualbox and VMware Player and until now I had no driver problems with any of them.

@eRJe: I use the generic Linux kernel 3.x (in workstation 10.0)

VMware Player even doesn't install on my computer and it doesn't say what's wrong nor which log file to look into. Very MS-ish software.

@bartgymnast: thanks. I'm using ESXi icw vsphere 5.5 which only goes up to kernel 2.6. I'm using that atm which enabled at least the nic.

For some reason VMware Player thinks it encountered an error when installing on Slackware. Only that there is no error, it is running fine after a forced install with --ignore-errors.

1 members found this post helpful.

Have you carefully checked the source code for VMware? Oh wait...

Thanks very much for the tip! It now installs. The problem might be that the installer can't setup the bridged virtual net. My guest system actually cannot connect to anywhere when I choose "bridged networking".

This can be fixed by killing the vmnet-bridge process and re-launch it with the correct "-i" option. I've searched /etc/rc.d/init.d but found vmnet-bridge in nowhere. Any idea how to keep this settings across system restart? Thanks!