Re: Haldaemon and Vmware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have the same relationship problem with haldaemon and vmware, that's why I posted originally. I initially thought it was a timing sequence thing on boot, it says it is starting haldaemon but when I check after it boots up, it's not running. If I restart haldaemon after the pc comes up, all is ok to reboot the machine, no hangs. However, I cannot shut the pc down, then it hangs. I then noticed that there is no script for vmware in rc.0, so I made a link for vmware in rc.0 and it can then shut down but then hangs at the end (shuts all down but does not power off). This only happens with AMD cpus and can then be corrected with acpi=off in the grub line, not needed with Intel cpus, or so I have seen. Bitter sweet when the new releases come out, exciting and yet a pain to work out the bugs, lol.

Matthew Saltzman wrote:

On Tue, 7 Dec 2004, Paul Howarth wrote:



On Mon, 2004-12-06 at 15:46 -0500, Matthew Saltzman wrote:


On Mon, 6 Dec 2004, Cyber Source wrote:


Dan Anderson wrote:

For me,

chkconfig --add vmware

worked. Looks like they forgot to add a link to rc0.d when they did
the initscripts.


Interesting. I did a fresh install of VMware and applied the
vmware-any-any-update84 patch (and copied /dev/vm* to /etc/udev). All
links are there (although the rc5.d and rc6.d links are absolute and the
others are relative). This doesn't seem to affect the behavior.


My experience has been that copying /dev/vm* to /etc/udev/devices after
running vmware-config.pl was sufficient to get
VMwareWorkstation-4.5.2-8848 working, and that applying vmware-any-any-
update84 actually broke things.



I'm beginning to think so. I'm going to reinstall without the any-any patch. On the other hand, the any-any patch is not the cause of the unregister_netdevice error--I applied it hoping it would help with that, and it seems to have only made things worse.

I turned off the vmware service and haldaemon stopped crashing.  Not sure
yet if that's related to the patch or the original problem.




-- cybersource.us 115 Richfield Road Williamsville, New York 14221 716-553-8525


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux