The trial version of VMware Workstation 9 expired last night. I bought a new version but after the expiration I found it would not accept an entry for a new key so I ran the vmware uninstall app. and installed the new one from scratch. It starts but only runs to the point where I get the message:
VMware kernel module updater
Before you can run VMware, several modules must be compiled and installed in the running kernel.
Cancel - Install
I click on install and that does nothing.
Starting vmware from the command line produces the following errors:
[root@box10 bobg]# cat /tmp/vmware-root/vmware-modconfig-6296.log
.............. Snip ........
2013-09-05T12:32:39.424-05:00| vthread-3| I120: The header path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for the kernel "3.10.10-200.fc19.x86_64" is valid. Whoohoo! 2013-09-05T12:32:39.424-05:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove. 2013-09-05T12:32:39.426-05:00| vthread-3| I120: Validating path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for kernel release "3.10.10-200.fc19.x86_64". 2013-09-05T12:32:39.426-05:00| vthread-3| I120: Failed to find /lib/modules/3.10.10-200.fc19.x86_64/build/include/linux/version.h 2013-09-05T12:32:39.426-05:00| vthread-3| I120: /lib/modules/3.10.10-200.fc19.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2013-09-05T12:32:39.445-05:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.10-200.fc19.x86_64". 2013-09-05T12:32:39.445-05:00| vthread-3| I120: The header path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for the kernel "3.10.10-200.fc19.x86_64" is valid. Whoohoo! 2013-09-05T12:32:39.445-05:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove. 2013-09-05T12:32:39.446-05:00| vthread-3| I120: Using temp dir "/tmp". 2013-09-05T12:32:39.449-05:00| vthread-3| I120: Invoking modinfo on "vmnet". 2013-09-05T12:32:39.455-05:00| vthread-3| I120: "/sbin/modinfo" exited with status 256. 2013-09-05T12:32:39.455-05:00| vthread-3| I120: Invoking modinfo on "vmblock". 2013-09-05T12:32:39.462-05:00| vthread-3| I120: "/sbin/modinfo" exited with status 256. 2013-09-05T12:32:39.577-05:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.10.10-200.fc19.x86_64/misc/vmnet.ko". 2013-09-05T12:32:39.577-05:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2013-09-05T12:32:39.593-05:00| vthread-3| I120: Successfully extracted the vmnet source. 2013-09-05T12:32:39.594-05:00| vthread-3| I120: Building module with command "/bin/make -j4 -C /tmp/modconfig-2ncGE1/vmnet-only auto-build HEADER_DIR=/lib/modules/3.10.10-200.fc19.x86_64/build/include CC=/bin/gcc IS_GCC_3=no" 2013-09-05T12:32:41.285-05:00| vthread-3| W110: Failed to build vmnet. Failed to execute the build command. 2013-09-05T12:32:41.290-05:00| vthread-3| I120: Setting destination path for vmblock to "/lib/modules/3.10.10-200.fc19.x86_64/misc/vmblock.ko". 2013-09-05T12:32:41.290-05:00| vthread-3| I120: Extracting the vmblock source from "/usr/lib/vmware/modules/source/vmblock.tar". 2013-09-05T12:32:41.305-05:00| vthread-3| I120: Successfully extracted the vmblock source. 2013-09-05T12:32:41.306-05:00| vthread-3| I120: Building module with command "/bin/make -j4 -C /tmp/modconfig-2ncGE1/vmblock-only auto-build HEADER_DIR=/lib/modules/3.10.10-200.fc19.x86_64/build/include CC=/bin/gcc IS_GCC_3=no" 2013-09-05T12:32:43.232-05:00| vthread-3| W110: Failed to build vmblock. Failed to execute the build command.
Perhaps someone has experience with VMware and can make a suggestion?
Bob
Am 05.09.2013 18:43, schrieb Bob Goodwin ~ Zuni, Virginia, USA:
2013-09-05T12:32:39.424-05:00| vthread-3| I120: The header path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for the kernel "3.10.10-200.fc19.x86_64" is valid. Whoohoo! 2013-09-05T12:32:43.232-05:00| vthread-3| W110: Failed to build vmblock. Failed to execute the build command.
Perhaps someone has experience with VMware and can make a suggestion?
as lways if you think you need the latest kernel and a bleeding-edge OS
https://www.google.at/search?q=wmare+workstation+kernel+3.10 and replace the 3.10 with the kernel you try
http://uwot.eu/blog/2013/07/linux-kernel-3-10-and-vmware-workstation-9/
u[root@srv-rhsoft:~]$ uname -r 3.10.10-100.fc18.x86_64 #1 SMP Thu Aug 29 20:13:09 UTC 2013
[root@srv-rhsoft:~]$ /scripts/vmware/vmrun.sh HOST: srv-rhsoft.rhsoft.net Total running VMs: 2 /mnt/data/fileserver/vmware/testserver/config.vmx /mnt/data/fileserver/vmware/arrakis/arrakis.vmx
On 05/09/13 13:01, Reindl Harald wrote:
Am 05.09.2013 18:43, schrieb Bob Goodwin ~ Zuni, Virginia, USA:
2013-09-05T12:32:39.424-05:00| vthread-3| I120: The header path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for the kernel "3.10.10-200.fc19.x86_64" is valid. Whoohoo! 2013-09-05T12:32:43.232-05:00| vthread-3| W110: Failed to build vmblock. Failed to execute the build command.
Perhaps someone has experience with VMware and can make a suggestion?
as lways if you think you need the latest kernel and a bleeding-edge OS
https://www.google.at/search?q=wmare+workstation+kernel+3.10 and replace the 3.10 with the kernel you try
http://uwot.eu/blog/2013/07/linux-kernel-3-10-and-vmware-workstation-9/
u[root@srv-rhsoft:~]$ uname -r 3.10.10-100.fc18.x86_64 #1 SMP Thu Aug 29 20:13:09 UTC 2013
[root@srv-rhsoft:~]$ /scripts/vmware/vmrun.sh HOST: srv-rhsoft.rhsoft.net Total running VMs: 2 /mnt/data/fileserver/vmware/testserver/config.vmx /mnt/data/fileserver/vmware/arrakis/arrakis.vmx
I am not fond of any particular kernel, they just come with the system updates as you well know.
Booted the oldest kernel I have left,
[root@box10 source]# uname -a Linux box10 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
And get the error:
[root@box10 source]# patch -p0 -i /tmp/vmblock-9.0.2-5.0.2-3.10.patch patch: **** Can't open patch file /tmp/vmblock-9.0.2-5.0.2-3.10.patch : No such file or directory
Do I need an older kernel? I don't understand what I am doing, just following instructions, where does the "patch" come from?
Am 05.09.2013 19:54, schrieb Bob Goodwin ~ Zuni, Virginia, USA:
On 05/09/13 13:01, Reindl Harald wrote:
Am 05.09.2013 18:43, schrieb Bob Goodwin ~ Zuni, Virginia, USA:
2013-09-05T12:32:39.424-05:00| vthread-3| I120: The header path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for the kernel "3.10.10-200.fc19.x86_64" is valid. Whoohoo! 2013-09-05T12:32:43.232-05:00| vthread-3| W110: Failed to build vmblock. Failed to execute the build command.
Perhaps someone has experience with VMware and can make a suggestion?
as lways if you think you need the latest kernel and a bleeding-edge OS
https://www.google.at/search?q=wmare+workstation+kernel+3.10 and replace the 3.10 with the kernel you try
http://uwot.eu/blog/2013/07/linux-kernel-3-10-and-vmware-workstation-9/
I am not fond of any particular kernel, they just come with the system updates as you well know.
Booted the oldest kernel I have left,
[root@box10 source]# uname -a Linux box10 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
3.10 remains 3.10 - the 10 makes the difference because it is a new kerne version and not only a bugfix release
And get the error:
[root@box10 source]# patch -p0 -i /tmp/vmblock-9.0.2-5.0.2-3.10.patch patch: **** Can't open patch file /tmp/vmblock-9.0.2-5.0.2-3.10.patch : No such file or directory
Do I need an older kernel? I don't understand what I am doing, just following instructions, where does the "patch" come from?
you are *not* following the instructions because they are clearly contain these two curl-commands downloading the patches, if you follwed the first step "cd /tmp" to the /tmp directory and the full path is referred by the next steps
curl -O http://pkgbuild.com/git/aur-mirror.git/plain/vmware-patch/vmblock-9.0.2-5.0.... curl -O http://pkgbuild.com/git/aur-mirror.git/plain/vmware-patch/vmnet-9.0.2-5.0.2-...
On 05/09/13 13:54, Bob Goodwin ~ Zuni, Virginia, USA wrote:
On 05/09/13 13:01, Reindl Harald wrote:
Am 05.09.2013 18:43, schrieb Bob Goodwin ~ Zuni, Virginia, USA:
2013-09-05T12:32:39.424-05:00| vthread-3| I120: The header path "/lib/modules/3.10.10-200.fc19.x86_64/build/include" for the kernel "3.10.10-200.fc19.x86_64" is valid. Whoohoo! 2013-09-05T12:32:43.232-05:00| vthread-3| W110: Failed to build vmblock. Failed to execute the build command.
Perhaps someone has experience with VMware and can make a suggestion?
as lways if you think you need the latest kernel and a bleeding-edge OS
https://www.google.at/search?q=wmare+workstation+kernel+3.10 and replace the 3.10 with the kernel you try
http://uwot.eu/blog/2013/07/linux-kernel-3-10-and-vmware-workstation-9/
u[root@srv-rhsoft:~]$ uname -r 3.10.10-100.fc18.x86_64 #1 SMP Thu Aug 29 20:13:09 UTC 2013
[root@srv-rhsoft:~]$ /scripts/vmware/vmrun.sh HOST: srv-rhsoft.rhsoft.net Total running VMs: 2 /mnt/data/fileserver/vmware/testserver/config.vmx /mnt/data/fileserver/vmware/arrakis/arrakis.vmx
I am not fond of any particular kernel, they just come with the system updates as you well know.
Booted the oldest kernel I have left,
[root@box10 source]# uname -a Linux box10 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
And get the error:
[root@box10 source]# patch -p0 -i /tmp/vmblock-9.0.2-5.0.2-3.10.patch patch: **** Can't open patch file /tmp/vmblock-9.0.2-5.0.2-3.10.patch : No such file or directory
Do I need an older kernel? I don't understand what I am doing, just following instructions, where does the "patch" come from?
Ok, I see the patch has to come from "git"? This is the same version of VMware as the trial that I installed about a month ago and it worked until yesterday so I must conclude that the "patch" is tied to a specific kernel. So what I need is the kernel from 30 days ago?
How do I deal with that? Can I still install an older kernel, I suspect that will cause trouble?
I'm in over myhead here.
Bob
On 05/09/13 14:12, Reindl Harald wrote:
you are *not* following the instructions because they are clearly contain these two curl-commands downloading the patches, if you follwed the first step "cd /tmp" to the /tmp directory and the full path is referred by the next steps
curl -Ohttp://pkgbuild.com/git/aur-mirror.git/plain/vmware-patch/vmblock-9.0.2-5.0.... curl -Ohttp://pkgbuild.com/git/aur-mirror.git/plain/vmware-patch/vmnet-9.0.2-5.0.2-...
No, I followed the instructions exactly, copy/paste!
I went through it again and this time it worked!
However I am still unable to enter the key. It wont even let me type in the "enter key" box.
Now it wants me to buy VMware 10 instead! I don't know what's going on but I guess I will have to deal with VMware directly. I have been reluctant to do that after earlier phone contacts that accomplished nothing.
Can I enter the key from the command line, does anyone know how to do that?
Bob
On 09/05/2013 03:08 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote:
However I am still unable to enter the key. It wont even let me type in the "enter key" box.
Yeah, I had this problem too. Try this:
sudo /usr/lib/vmware/bin/vmware-vmx --new-sn xxx
(from: https://communities.vmware.com/thread/415595?start=0&tstart=0)
Regards, Raman
On 05/09/13 16:51, Raman Gupta wrote:
On 09/05/2013 03:08 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote:
However I am still unable to enter the key. It wont even let me type in the "enter key" box.
Yeah, I had this problem too. Try this:
sudo /usr/lib/vmware/bin/vmware-vmx --new-sn xxx
(from: https://communities.vmware.com/thread/415595?start=0&tstart=0)
Regards, Raman
Raman
Yes, that seems to have done the trick. I've wasted most of the day fiddling with this. That probably would have enabled my trial subscription to work had I known ...
Thank you,
Bob
-
Bob Goodwin -
Raman Gupta -
Reindl Harald