View previous topic :: View next topic |
Author |
Message |
Saundersx Apprentice
Joined: 11 Apr 2005 Posts: 294
|
Posted: Sun Mar 01, 2009 6:11 am Post subject: vmware got borked [SOLVED] |
|
|
Vmware suddenly stopped working and I can't for the life of me tell why. I have been reading and trying everything but nothing works. I am pretty positive it's not a module/permissions error but I cannot find the solution.
here's a snippit from the log.
Code: |
Mar 01 01:34:07.901: vmui| VMHSVMCbPower: Setting state of VM /vm/#42246aa468fd1ac9/ to powerOn with option hard
Mar 01 01:34:07.902: vmui| VMHS: Exec()'ing /opt/vmware/workstation/lib/vmware/bin/vmware-vmx-debug, /home/XXXXX/vmware/WinXPPro/Windows XP Professional.vmx
Mar 01 01:34:07.961: vmui| vmdbPipe_Streams: Couldn't read
Mar 01 01:34:07.962: vmui| Internal VMDB error: Pipe: Read failed
Mar 01 01:34:11.136: vmui| GLib: g_source_unref: assertion `source != NULL' failed
Mar 01 01:34:11.136: vmui| VixVM_FinalRelease: Close VM socket.
Mar 01 01:34:11.157: vmui| GLib: g_source_unref: assertion `source != NULL' failed
Mar 01 01:34:11.157: vmui| VixVM_FinalRelease: Close VM socket.
Mar 01 01:34:11.173: vmui| GLib: g_source_unref: assertion `source != NULL' failed
Mar 01 01:34:11.173: vmui| VixVM_FinalRelease: Close VM socket.
Mar 01 01:34:11.512: vmui| AIOMGR-S : stat o=67 r=0 w=0 i=0 br=0 bw=0 |
and the ui errors out with this
Code: | Unable to change virtual machine power state: Internal error. |
what's extra annoying is this little part right here
Code: | Internal VMDB error: Pipe: Read failed |
is not in any search engine/vmware forums. I have completely uninstalled/reinstalled everything to no avail. Nothing has changed vmware-wise it suddenly stopped working. If I had to guess, it may be related to either the new kernel I have updated to (2.6.28-zen11) or nvidia drivers (180.35) as these are the only real changes to the system. I have updated everything since the issue started (emerge -auvDN world) and nothing helped.
Last edited by Saundersx on Sun Mar 01, 2009 6:38 am; edited 1 time in total |
|
Back to top |
|
|
Saundersx Apprentice
Joined: 11 Apr 2005 Posts: 294
|
Posted: Sun Mar 01, 2009 6:38 am Post subject: |
|
|
My guess was right, downgrading nvidia-drivers to 180.29 fixed the problem completely... |
|
Back to top |
|
|
nsahoo l33t
Joined: 17 Jul 2003 Posts: 618
|
Posted: Mon Mar 02, 2009 4:38 pm Post subject: |
|
|
Thanks. I was having the same trouble. Downgrading the nvidia-drivers fixed it. |
|
Back to top |
|
|
sharmay n00b
Joined: 01 Apr 2004 Posts: 27
|
Posted: Mon Mar 02, 2009 8:03 pm Post subject: |
|
|
Also if you get following message in a popup dialog box:
vmware workstation unable to change virtual machine power state: internal error
downgrading nvidia fixes this issue
From x11-drivers/nvidia-drivers-180.35 downgraded to x11-drivers/nvidia-drivers-177.82 |
|
Back to top |
|
|
SHINODATT n00b
Joined: 07 Jan 2006 Posts: 70 Location: Ontario, Canada
|
Posted: Tue Mar 10, 2009 5:47 am Post subject: |
|
|
sharmay wrote: | Also if you get following message in a popup dialog box:
vmware workstation unable to change virtual machine power state: internal error
downgrading nvidia fixes this issue
From x11-drivers/nvidia-drivers-180.35 downgraded to x11-drivers/nvidia-drivers-177.82 |
Indeed it does. How goofy. _________________ Board: Maximus Formula, Rampage conversion, BIOS 308
CPU: Q6600 G0 @ 3.47Ghz (385x9), CM Hyper 212 Cooler
RAM: 4x 2GB Kingston 667 @ 771Mhz, 2V
Video: ASUS GeForce 8800GTS 512MB
OS: Gentoo 2.6.29 x86_64 |
|
Back to top |
|
|
86me n00b
Joined: 20 Jul 2009 Posts: 20
|
Posted: Sun Jun 20, 2010 4:37 am Post subject: |
|
|
That would fine if by downgrading nvidia-drivers (195.36.24 -> 180.60) portage didn't want me to also downgrade xorg-server from 1.7 -> 1.6.
This includes mesa and libvdpau blocks also
Anyone know how to manually reset a virtual machine's power state to "off"?
This is what I can gather from /tmp/vmware-user/ui-pid.log:
Quote: |
Jun 19 23:39:05.402: vmui| Reloading config state: /mnt/ext3_500/VMWare Virtual Machines/Windows_XP_Professional/Windows XP Professional.vmx
Jun 19 23:39:05.436: vmui| VMHS: Transitioned vmx/execState/val to suspended
Jun 19 23:39:05.441: vmui| connect to /var/run/vmware/egon_1000/1276989874742424_10744/testAutomation-fd: Connection refused
Jun 19 23:39:05.471: vmui| Setting power state suspended (reported)
Jun 19 23:39:05.479: vmui| IPC Manager: Error while connecting socket client: No such file or directory
Jun 19 23:39:05.481: vmui| ReplayMgr::OnFoundryEventNotify --- got event 12
Jun 19 23:39:05.568: vmui| Reloading config state: /mnt/ext3_500/VMWare Virtual Machines/Windows_XP_Professional/Windows XP Professional.vmx
Jun 19 23:39:05.595: vmui| VMHS: Transitioned vmx/execState/val to suspended
Jun 19 23:39:05.599: vmui| DUMPER: restoring checkpoint version 8
Jun 19 23:39:05.712: vmui| Setting power state suspended (reported)
Jun 19 23:39:09.599: vmui| VMHSVMCbPower: Setting state of VM /vm/#b57fa2028e6f9735/ to resume with option hard
Jun 19 23:39:09.599: vmui| VMHS: Exec()'ing /opt/vmware/workstation/lib/vmware/bin/vmware-vmx, /mnt/ext3_500/VMWare Virtual Machines/Windows_XP_Professional/Windows XP Professional.vmx
Jun 19 23:39:09.640: vmui| vmdbPipe_Streams: Couldn't read
Jun 19 23:39:09.641: vmui| Internal VMDB error: Pipe: Read failed
Jun 19 23:39:17.764: vmui| Caught signal 20 -- pid 13224 (eip 0x7ff8bd1854b3)
|
Hoping for an alternate solution to downgrading nvidia-drivers. |
|
Back to top |
|
|
|