Hello everyone, I have the following rather anoying problem with VMware workstation 5.5.2 build-29772 on my SuSE Linux 10.1 host, namely everytime I reboot the vmmon module I had compiled and loaded in the kernel is for some reason gone and I get error messages like these: "Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded." "Failed to initialize monitor device." "Unable to change virtual machine power state: Cannot find a valid peer process to connect to." Is there a way to just load the module and keep it there? Is this a VMware issue or is it SUSE? TIA George
Hello everyone, Hi
I have the following rather anoying problem with VMware workstation 5.5.2 build-29772 on my SuSE Linux 10.1 host, namely everytime I reboot the vmmon module I had compiled and loaded in the kernel is for some reason gone and I get error messages like these: "Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded."
"Failed to initialize monitor device."
"Unable to change virtual machine power state: Cannot find a valid peer process to connect to."
Is there a way to just load the module and keep it there? Is this a VMware issue or is it SUSE? That build is working fine on my SuSE10.1... except for /dev/rtc problem
George Stoianov wrote: that I will ask this list in a while... A few questions - Have you installed it from the tar.gz or rpm ? If have no experience in installing VMWare from rpm but, if you install from tar.gz you also need the following: - kernel-sources and all goodies to compile a kernel among others. Try to install the kernel.development section - It should do. - you need to go to /usr/src/linux and type: - make cloneconfig - make prepare Then unpack and run vmware-config.pl as root You have to run vmware-config.pl script every time you upgrade your kernel. You also should do a make cloneconfig and make prepare too. Hope it helps you.
TIA George Rui Santos
-- Rui Santos http://www.ruisantos.com/ They that would give up essential liberty for temporary safety deserve neither one of them.
A few questions - Have you installed it from the tar.gz or rpm ?
Yes
If have no experience in installing VMWare from rpm but, if you install from tar.gz you also need the following: - kernel-sources and all goodies to compile a kernel among others. Try to install the kernel.development section - It should do. - you need to go to /usr/src/linux and type: - make cloneconfig - make prepare Then unpack and run vmware-config.pl as root
I have installed the gcc compiler and the kernel sources, ofcourse at the time I had already upgraded the kernel to a newer version and did not have the matching sources on the DVD so I had to uninstall and reinstall the original kernel with sources and then apply the patch and keep the source and after that run vmware-config.pl
You have to run vmware-config.pl script every time you upgrade your kernel. You also should do a make cloneconfig and make prepare too.
Yes I have run the vmware-config.pl script my problem is that the module disappears after each reboot. Can eloborate on why I should run cloneconfig and make prepare too?? Thanks. George
George Stoianov wrote: >> >> A few questions >> - Have you installed it from the tar.gz or rpm ? > > Yes > >> If have no experience in installing VMWare from rpm but, if you install >> from tar.gz you also need the following: >> - kernel-sources and all goodies to compile a kernel among others. >> Try to install the kernel.development section - It should do. >> - you need to go to /usr/src/linux and type: >> - make cloneconfig >> - make prepare >> Then unpack and run vmware-config.pl as root > > I have installed the gcc compiler and the kernel sources, ofcourse at > the time I had already upgraded the kernel to a newer version and did > not have the matching sources on the DVD so I had to uninstall and > reinstall the original kernel with sources and then apply the patch > and keep the source and after that run vmware-config.pl > >> >> You have to run vmware-config.pl script every time you upgrade your >> kernel. You also should do a make cloneconfig and make prepare too. > > Yes I have run the vmware-config.pl script my problem is that the > module disappears after each reboot. Can eloborate on why I should run > cloneconfig and make prepare too?? - make cloneconfig configures your kernel with SuSE settings from /proc/config.gz - make prepare: I don't know exactly what it does but, at VMware's site they say one should do this every time you upgrade your kernel. > > Thanks. > George Rui > > -- Rui Santos http://www.ruisantos.com/ They that would give up essential liberty for temporary safety deserve neither one of them.
On Friday 13 October 2006 04:16, Rui Santos wrote:
George Stoianov wrote:
A few questions - Have you installed it from the tar.gz or rpm ?
Yes
If have no experience in installing VMWare from rpm but, if you install from tar.gz you also need the following: - kernel-sources and all goodies to compile a kernel among others. Try to install the kernel.development section - It should do. - you need to go to /usr/src/linux and type: - make cloneconfig - make prepare Then unpack and run vmware-config.pl as root Rui Santos
make that make modules_prepare. there is a difference and the modules prefix is required for a vmware compile. d
On Fri, 2006-10-13 at 09:50 -0400, George Stoianov wrote:
I have installed the gcc compiler and the kernel sources, ofcourse at the time I had already upgraded the kernel to a newer version and did not have the matching sources on the DVD so I had to uninstall and reinstall the original kernel with sources and then apply the patch and keep the source and after that run vmware-config.pl
This shouldn't be necessary with 10.1. If you have the update configured, you should get the latest version automatically if you install a package for the first time
George Stoianov wrote:
Hello everyone,
I have the following rather anoying problem with VMware workstation 5.5.2 build-29772 on my SuSE Linux 10.1 host, namely everytime I reboot the vmmon module I had compiled and loaded in the kernel is for some reason gone [...]
Is there a way to just load the module and keep it there? Is this a VMware issue or is it SUSE?
The module is normale loaded at boot time by the init.d-script vmware. What's the output of chkonfig -l vmware ? It should show "on" for run levels 2, 3, and 5. If it doesn't, issue the command chkconfig -a vmware If it outputs "vmware: unknown service", you have a problem with your installation. HTH, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
Thanks Joachim, I have already fund the answer thanks to Kevin from VMware. There forum is really good. Solution link: http://www.vmware.com/community/thread.jspa?threadID=58126&messageID=494371#494371. Thank you. George On 10/14/06, Joachim Schrod <jschrod@acm.org> wrote:
George Stoianov wrote:
Hello everyone,
I have the following rather anoying problem with VMware workstation 5.5.2 build-29772 on my SuSE Linux 10.1 host, namely everytime I reboot the vmmon module I had compiled and loaded in the kernel is for some reason gone [...]
Is there a way to just load the module and keep it there? Is this a VMware issue or is it SUSE?
The module is normale loaded at boot time by the init.d-script vmware.
What's the output of chkonfig -l vmware ? It should show "on" for run levels 2, 3, and 5. If it doesn't, issue the command chkconfig -a vmware If it outputs "vmware: unknown service", you have a problem with your installation.
HTH, Joachim
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
On Monday 23 October 2006 12:22 pm, George Stoianov wrote:
I have already fund the answer thanks to Kevin from VMware. Their forum is really good. Solution link: http://www.vmware.com/community/thread.jspa? threadID=58126&messageID=494371#494371. ^ Beware of line-wrap ^
... then I looked inside "/etc/init.d/init.d" as I thought there is usually only one???
Ah Hah. One-eyed RedHat RPMs strike again. That's RH's init.d setup, happens to me every time I install slimserver for my squeezeboxes. Just look in "/etc/init.d/init.d" and reef anything useful back in to "/etc/init.d". Test your startup and delete the unwanted inner init.d The startup script you were given is probably just as RedHat centric. Have a look at a standard SuSE one and re-model it, adding the active runlevel comment block and using SuSE's better preloads. VMware used to work well out-of-the-box. Have they gone backwards? michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 No matter how much you pay for software, you always get less than you hoped. Unless you pay nothing, then you get more.
participants (6)
-
Anders Johansson
-
George Stoianov
-
Joachim Schrod
-
kanenas@hawaii.rr.com
-
Michael James
-
Rui Santos