I tried to install Vmware Player 5.0.1 last night. I need a copy of windows to do my taxes on. In the process I put a big bind in the coggs.
I reloaded the system today and then
# dpkg --add-architecture i386
# apt-get update
I installed Vmware Player 4 and once up and running upgraded it to 5.0.1. The only issue so far is the sound is more static than sound. Muting the sound in the VM doesn't help. Installed Windows 7 Enterprise, and Office 2013. I will work on the sound issue in the near future. I might install paintitblack, or LMDE and see if I have the same problem or if it is a windows issue.
I then installed TeamViewer 7 so I could work on my mom's computer from 2000 miles away and all went well.
If anyone has any suggestions on the sound I would appreciate them.
Opened my mouth to soon and chrashed 5.0.1. Back to 4.0.5 and a little search and read time ahead.
You could give Oracles Virtualbox a try or kvm (if your hardware is capable) Vbox with 3.7.x needs the vbox package straight from Oracle (the one for Wheezy). The one in unstable is too old, due to the freeze.
greetz
devil
Player 5.0.1 is running perfectly on 3 siduction systems here -- two 64-bit and one 32-bit. I don't routinely need the audio in Windows, but I just tested one VM and it plays music no problem. The sound volume is controlled by pulseaudio on the host. If your audio is working correctly on the host, it should work correctly on the Windows VM. I'm running Win 7 Pro. and I also have a Win XP VM that works fine.
But, I did not try the upgrade path -- I purged ver. 4 and installed 5 from the downloaded bundle, which needs to be renamed after you download it because somehow it becomes .txt instead of .bundle during the download process (maybe chromium does that).
The sound isuue was Windows 7. Some adjusting the settings fixed the sound. Updated to 5 and it errored out.
Opened terminal
su
apt-get install chkconfig
vmware-modconfig --console --install-all
All is working fine.
A rather annoying process to go through just to load a program to do your taxes so can loose more of your money.
Back to 4.0.5 but for now it is working. 5 crashed again. I had to quit messing with it for now and do some work on it.
It has never been necessary for me to do that -- I did not have chkconfig installed. However, just to see what happens ....
root@imerabox:/home/don# vmware-modconfig --console --install-all
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-Gc2JI4/vmmon-only'
/usr/bin/make -C /lib/modules/3.7-1.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/task.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-Gc2JI4/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-Gc2JI4/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-Gc2JI4/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-Gc2JI4/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Gc2JI4/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Gc2JI4/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-Gc2JI4/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-Gc2JI4/vmnet-only'
/usr/bin/make -C /lib/modules/3.7-1.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/driver.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/hub.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/userif.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/netif.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/bridge.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/procfs.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/filter.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/smac.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-Gc2JI4/vmnet-only/vnetUserListener.o
/tmp/modconfig-Gc2JI4/vmnet-only/driver.c: In function 'VNetFileOpIoctl.isra.5':
/tmp/modconfig-Gc2JI4/vmnet-only/driver.c:1009:17: warning: 'hubJack' may be used uninitialized in this function [-Wmaybe-uninitialized]
LD [M] /tmp/modconfig-Gc2JI4/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-Gc2JI4/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-Gc2JI4/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Gc2JI4/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Gc2JI4/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-Gc2JI4/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-Gc2JI4/vmblock-only'
/usr/bin/make -C /lib/modules/3.7-1.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/stubs.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/module.o
CC [M] /tmp/modconfig-Gc2JI4/vmblock-only/linux/super.o
/tmp/modconfig-Gc2JI4/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default]
/tmp/modconfig-Gc2JI4/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for 'LinkDentryOps.d_revalidate') [enabled by default]
/tmp/modconfig-Gc2JI4/vmblock-only/linux/dentry.c: In function 'DentryOpRevalidate':
/tmp/modconfig-Gc2JI4/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of 'actualDentry->d_op->d_revalidate' makes integer from pointer without a cast [enabled by default]
/tmp/modconfig-Gc2JI4/vmblock-only/linux/dentry.c:104:7: note: expected 'unsigned int' but argument is of type 'struct nameidata *'
/tmp/modconfig-Gc2JI4/vmblock-only/linux/control.c: In function 'ExecuteBlockOp':
/tmp/modconfig-Gc2JI4/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/modconfig-Gc2JI4/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of 'putname' from incompatible pointer type [enabled by default]
In file included from include/linux/proc_fs.h:5:0,
from /tmp/modconfig-Gc2JI4/vmblock-only/linux/control.c:28:
include/linux/fs.h:2045:13: note: expected 'struct filename *' but argument is of type 'char *'
/tmp/modconfig-Gc2JI4/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
/tmp/modconfig-Gc2JI4/vmblock-only/linux/inode.c:49:4: warning: (near initialization for 'RootInodeOps.lookup') [enabled by default]
LD [M] /tmp/modconfig-Gc2JI4/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "putname" [/tmp/modconfig-Gc2JI4/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-Gc2JI4/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-Gc2JI4/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Gc2JI4/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Gc2JI4/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-Gc2JI4/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-Gc2JI4/vmci-only'
/usr/bin/make -C /lib/modules/3.7-1.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-Gc2JI4/vmci-only/driverLog.o
LD [M] /tmp/modconfig-Gc2JI4/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-Gc2JI4/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-Gc2JI4/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Gc2JI4/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Gc2JI4/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-Gc2JI4/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-Gc2JI4/vsock-only'
/usr/bin/make -C /lib/modules/3.7-1.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/linux/util.o
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-Gc2JI4/vsock-only/driverLog.o
LD [M] /tmp/modconfig-Gc2JI4/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-Gc2JI4/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-Gc2JI4/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Gc2JI4/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Gc2JI4/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-Gc2JI4/vsock-only'
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Shared Memory Available done
Interesting to see that more services were started at the end than were stopped at the beginning -- not sure what that's about. However, it is also consistent with what I see in the terminal:
root@imerabox:/home/don# service vmware stop
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
root@imerabox:/home/don# service vmware start
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Shared Memory Available done
root@imerabox:/home/don#
I'm wondering if there's something about your video setup. Can you show the output of
inxi -v3?
System: Host: bc-lt Kernel: 3.7-1.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2)
Desktop: Xfce 4.10.0 (Gtk 2.24.10) Distro: siduction 12.2.0 Riders on the Storm - xfce - (201212092126)
Machine: Mobo: Acer model: Aspire 5733Z version: V1.06 Bios: Acer version: V1.06 date: 09/07/2011
CPU: Dual core Intel Pentium CPU P6200 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 ssse3) bmips: 8513.92
Clock Speeds: 1: 933.00 MHz 2: 933.00 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller bus-ID: 00:02.0
X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.0hz
GLX Renderer: Mesa DRI Intel Ironlake Mobile GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes
Network: Card-1: Broadcom NetLink BCM57780 Gigabit Ethernet PCIe driver: tg3 ver: 3.125 bus-ID: 01:00.0
IF: eth0 state: down mac: dc:0e:a1:0c:cb:97
Card-2: Atheros AR9485 Wireless Network Adapter driver: ath9k bus-ID: 02:00.0
IF: wlan0 state: up mac: 74:de:2b:ae:47:4c
Drives: HDD Total Size: 500.1GB (6.2% used) 1: model: Hitachi_HTS54755
Info: Processes: 155 Uptime: 3 min Memory: 261.1/3634.6MB Runlevel: 5 Gcc sys: 4.7.2
Client: Shell (bash 4.2.37) inxi: 1.8.24
I was hagging out with my MC today and got a quart of apple pie from a Brother. So I wasn't in a big hurry to get home.lol
Above is the out put from inxi -v3.
I wrapped the output in code tags -- makes it easier to read. Left-bracket, the word "code", and right-bracket at the beginning, and then at the end left-bracket "/code" and right-bracket.
In your BIOS, does it show that it supports virtualization? I don't know the P6200, and I don't see "vmx" which is the flag indicating support for virtualization.
http://www.howtogeek.com/howto/linux/linux-tip-how-to-tell-if-your-processor-supports-vt/
In recent times, VMware has gotten more "picky" about which CPUs can run it. I have a Toshiba NB205 that could run Player v.4 but not v.5, as it does not have the "vmx" CPU flag. It might be that you have to use Virtual Box, which is what most of the siduction users use. They're saying that you need to download the current version from the Oracle site, and not to install the version from the Debian sid repo, which is pretty old at this point.
Quote from: "dibl"
In recent times, VMware has gotten more "picky" about which CPUs can run it. I have a Toshiba NB205 that could run Player v.4 but not v.5, as it does not have the "vmx" CPU flag. It might be that you have to use Virtual Box, which is what most of the siduction users use. They're saying that you need to download the current version from the Oracle site, and not to install the version from the Debian sid repo, which is pretty old at this point.
It looks like Virtual Box will be the next to try. May stick with VMware 4 for now untill tax season is over.
These are my flags no vmx:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid popcnt lahf_lm arat dtherm
I've installed vbox. Will work on installing Win 7 on it tomorrow after a good nights sleep and my brain cells recover from the abuse I am giving them.
Quote from: "devil"You could give Oracles Virtualbox a try or kvm (if your hardware is capable) Vbox with 3.7.x needs the vbox package straight from Oracle (the one for Wheezy). The one in unstable is too old, due to the freeze.
greetz
devil
Thanks for that info! I just came here looking for why VBox wasn't working. Installed virtualbox-4.2 and all is good. :)