slackware 64bit virtualbox guest

guanx · 11-30-2013, 09:57 PM

Quote:

Originally Posted by re_nelson

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

No. I am not patient enough to dig out where the WMware source code is in this tarball

Code:

$ tar -tf VMware-ws-open-source-1379776.tgz
gettext-0.14.6.tgz
glibmm-2.22.1.tgz
glibmm-2.16.4.tgz
glib-2.16.4.tgz
glib-2.24.2-1.tgz
libglade-2.6.0.tgz
libaio-0.3.106.tgz
gettext-0.17-1.tgz
glibmm-2.22.1-3.tgz
libgcrypt-1.4.3.tgz
gtkmm-2.20.1.tgz
atk-2.3.93.tgz
at-spi2-atk-2.3.91.tgz
glibmm-2.24.0.tgz
pango-1.20.5.tgz
glib-2.22.4-3.tgz
gail-1.22.3.tgz
libart_lgpl-2.3.17.tgz
at-spi-1.22.1.tgz
libgpg-error-1.5.tgz
gtk-engines-2.18.4.tgz
procps-3.2.7-1.tgz
alsa-lib-1.0.13.tgz
cairo-1.10.2.tgz
glib-2.22.4-1.tgz
librsvg-2.16.0.tgz
atk-1.22.0.tgz
cairomm-1.6.0.tgz
gcc-4.4.3-1.tgz
gtk+-2.20.0.tgz
libsigc++-2.2.11.tgz
gksu-2.0.2_1371468.tgz
pango-1.26.0.tgz
ocaml-3.12.1.tgz
libjpeg-turbo-1.1.1.tgz
libiconv-1.9.2.tgz
iconv-1.9.2.tgz
cairomm-1.10.0.tgz
gcc-4.1.2-7.tgz
libbonobo-2.22.0.tgz
zenity-2.30.0.tgz
jansson-2.3.tgz
atk-1.30.0.tgz
libgtop-2.14.9.tgz
gcc-4.1.2-4.tgz
dbus-1.4.16.tgz
startup-notification-0.9.tgz
ocaml-3.11.0.tgz
cairo-1.6.4.tgz
glib-2.22.1-1.tgz
gtkmm-2.12.7.tgz
libfuse-2.5.3.tgz
uriparser-0.7.0-1.tgz
gettext-0.17.tgz
gnome-keyring-2.91.93.tgz
at-spi2-core-2.3.91.tgz
gtk+-2.12.11.tgz
pangomm-2.26.0.tgz

guanx · 12-01-2013, 12:31 PM

Quote:

Originally Posted by guanx

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!

I am happy to say I will not spend more time on VMware Player. I did work around the bridged network problem by creating a wrapper script for vmnet-bridge but later I have problems installing VMware tools. The VMware nowadays is not that VMware ten years ago. Using VMware is simply causing me endless troubles and benefiting negligible performance gain.

Qemu or VirtualBox is the solution.

re_nelson · 12-01-2013, 12:55 PM

Quote:

Originally Posted by guanx

I am happy to say I will not spend more time on VMware Player. I did work around the bridged network problem by creating a wrapper script for vmnet-bridge but later I have problems installing VMware tools. The VMware nowadays is not that VMware ten years ago. Using VMware is simply causing me endless troubles and benefiting negligible performance gain.

Qemu or VirtualBox is the solution.

Like you, I have all three virtualization applications. And all of them are running Slackware64-current so that I can compare QEMU, VirtualBox and VMplayer. While there are more CPU flags present with VMplayer such as SSE4.2, benchmarks that I have run reveal that VirtualBox matches VMplayer in every metric that interests me (I don't do games). The flexibility of QEMU is also very appealing to me since I can experiment with different hardware. I do keep VMplayer around on my system but since its hood is welded shut, it doesn't have the hack value of the other two.

JMHO and YMMV.