Ticket #214 (assigned defect)

Opened 3 years ago

Last modified 1 year ago

Lockup under XP32, VMWare Player and notfred when VM gets stopped

Reported by: IwantAbetterPC Assigned to: uncle_fungus (accepted)
Priority: major Milestone: 2.4.0
Component: Monitoring system Keywords:
Cc:

Description

Hello,

I have a dual Xeon Dell 670 workstation running XP 32bit SP3, running the latest FAHMon client (2.3.99.1 installed this morning). Today, installed latest VMWare Player and notfred client (trying to get more points from SMP clients for CPCHimps!), and got it all set up working OK, including FAHmon clients pointing at the IP addresses of the two VMs I'd created - all working hunky dory.

As soon as I stopped and closed a VMWare client, FAHMon locked up and I couldn't get any control back over it. If I killed it via task manager and restarted it (with the VM still off), it started and locked up immediately - no messages or anything, as the client obviously can't detect the IP address of the (now non-existent) VM. Nothing looks odd in the logs, so I haven't included them. Please let me know if there are any other files or traces inside the machine I could send to assit.

Hope this is enough to point you in the right direction.

Regards,

Craig...

Change History

10/08/10 11:12:51 changed by uncle_fungus

  • status changed from new to assigned.
  • milestone set to 2.4.0.