In the last few days, I have noticed a drastic slowdown in my VMware Windows guest OS.. I recently bit the bullet and upgraded it from XP SP1 to SP2, and that seemed to work fine for quite a few days.
The two major changes I made to the system recently were:
1) The most recent update from CentOS (can't remember which one, but it was within the last two weekd for 5.0).
2) Adding another VM guest OS, this one a CentOS 5.0 guest.
What happens is, usually when I click the mouse in the Windows window, the system hangs up completely for some period of time that usually exceeds four minutes. Thereafter, once the VM is "running," it will occasionally just stop when I am transitioning into the VM from elsewhere.
I verified this using the CentOS system clock - last night it stopped at 23:01 and still read 23:01 when my cell phone, which is usually dead on in sync with the system clock, read 11:04pm.
I cut back on the amount of memory allowed to the Windows VM (768MB, down from 1GB) and that seemed to help a little, but I have 2GB and I'm thinking that this should not be a problem.
Any input would be helpful.
Thanks.
mhr
P.S.: Now I'm thinking that my earlier remark about applications was a bit overstated....
On Wed, Nov 28, 2007 at 04:47:57PM -0800, Mark Hull-Richter wrote:
In the last few days, I have noticed a drastic slowdown in my VMware Windows guest OS.. I recently bit the bullet and upgraded it from XP SP1 to SP2, and that seemed to work fine for quite a few days.
The two major changes I made to the system recently were:
- The most recent update from CentOS (can't remember which one, but
it was within the last two weekd for 5.0).
- Adding another VM guest OS, this one a CentOS 5.0 guest.
What happens is, usually when I click the mouse in the Windows window, the system hangs up completely for some period of time that usually exceeds four minutes. Thereafter, once the VM is "running," it will occasionally just stop when I am transitioning into the VM from elsewhere.
I verified this using the CentOS system clock - last night it stopped at 23:01 and still read 23:01 when my cell phone, which is usually dead on in sync with the system clock, read 11:04pm.
I cut back on the amount of memory allowed to the Windows VM (768MB, down from 1GB) and that seemed to help a little, but I have 2GB and I'm thinking that this should not be a problem.
Any input would be helpful.
Thanks.
Hmm, could be the memory thing -- as the result of the second guest. How much memory is allocated to it?
When the slowdown occurs, can you check vmstat / iostat on the host and see if the system is swapping? Watch free as well.
Ray
On Nov 28, 2007 4:53 PM, Ray Van Dolson rvandolson@esri.com wrote:
Hmm, could be the memory thing -- as the result of the second guest. How much memory is allocated to it?
768MB to each one.
When the slowdown occurs, can you check vmstat / iostat on the host and see if the system is swapping? Watch free as well.
It's not so much of a slowdown as a hang. The whole system stops (except for something that is hanging everything else).
After posting this, I went in and brought up the machine - it took a few minutes to get to the Windows login screen, and then when I clicked on it, the system hung for an hour. There is a hole in the log here, too, a little over an hour long:
Nov 28 16:41:36: app| New connection on socket server-vmdb from host localhost (ip address: local) , user: mhr Nov 28 16:41:36: app| SP: New user session for user: mhr, pos: 0 Nov 28 16:41:36: app| The vm-list file has changed! Reloading the list of registered vms Nov 28 16:41:36: app| Failed to lookup owner for: /F/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 16:41:36: app| Could not get canonical path for /F/vmware/Windows XP Professional/Windows XP Professional.vmx: No such file or directory Nov 28 16:41:36: app| Error Adding vm: /F/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:36: app| Failed to lookup owner for: /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx. Reason: No such file or directory Nov 28 16:41:36: app| Could not get canonical path for /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx: No such file or directory Nov 28 16:41:36: app| Error Adding vm: /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx Nov 28 16:41:36: app| Failed to lookup owner for: /home/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 16:41:36: app| Could not get canonical path for /home/vmware/Windows XP Professional/Windows XP Professional.vmx: No such file or directory Nov 28 16:41:36: app| Error Adding vm: /home/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:37: app| SP: Retrieved username: mhr Nov 28 16:41:44: app| Adding to list of running vms: /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:44: app| Attempting to launch vmx : /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:44: app| New connection on socket server-vmxvmdb from host localhost (ip address: local) , user: mhr Nov 28 16:41:44: app| Connection from : /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:44: app| Setting up autoDetect info. Nov 28 16:41:44: app| VMServerdConnect: connecting to /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:44: app| Connected to /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 16:41:44: app| SP: Retrieved username: mhr Nov 28 16:41:44: app| VM suddenly changed state: poweredOn. Nov 28 16:41:45: app| SP: Retrieved username: mhr Nov 28 16:41:45: app| cleanup: cleaned up 1 objects Nov 28 16:41:45: app| SP: Retrieved username: mhr Nov 28 16:42:22: app| VmsdRegister: Config file has changed: /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 18:05:49: app| OvlHostStartIo: errno 104 Nov 28 18:05:49: app| vmdbPipe_Streams: Couldn't read Nov 28 18:05:49: app| VM suddenly changed state: poweredOff. Nov 28 18:05:49: app| Removing from running vm list: /G/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 18:05:50: app| VMServerd IPC closed the connection with thread /G/vmware/Windows XP Professional/Windows XP Professional.vmx (0x8301ae8) Nov 28 18:05:50: app| Lost connection to /G/vmware/Windows XP Professional/Windows XP Professional.vmx (/G/vmware/Windows XP Professional/Windows XP Professional.vmx) unexpectedly. Nov 28 18:05:50: app| cleanup: cleaned up 1 objects Nov 28 18:05:52: app| VM suddenly changed state: poweredOff. Nov 28 18:05:52: app| VM suddenly changed state: poweredOff. Nov 28 18:05:52: app| VM suddenly changed state: poweredOff. Nov 28 18:05:53: app| SP: Retrieved username: mhr Nov 28 18:05:53: app| SP: Retrieved username: mhr Nov 28 18:06:52: app| SP: Retrieved username: mhr Nov 28 18:06:52: app| Error when reading from snhelper: Error:25:The system cannot find the file specified Nov 28 18:06:52: app| VMHS: failed to open '/E/vmware/CentOS 5/CentOS 5.0 x86-000001.vmdk' : The system cannot find the file specified (25) Nov 28 18:06:52: app| Cmd /host2/#dee67551b35613d0/util/disk/cmd/##68_8e/op/getDiskInfo/ failed: The system cannot find the file specified Nov 28 18:07:00: app| Failed to lookup owner for: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx. Reason: No such file or directory Nov 28 18:07:00: app| Could not get canonical path for /E/vmware/CentOS 5/CentOS 5.0 x86.vmx: No such file or directory Nov 28 18:07:00: app| Adding to list of running vms: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx Nov 28 18:07:00: app| Failed to lookup owner for: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx. Reason: No such file or directory Nov 28 18:07:00: app| Could not get canonical path for /E/vmware/CentOS 5/CentOS 5.0 x86.vmx: No such file or directory Nov 28 18:07:00: app| Failed to add running vm: Schema path not found Nov 28 18:07:00: app| Adding to list of running VM's failed Nov 28 18:07:00: app| VmsdVmxLostVmxMountCb failed: VMDB failure Nov 28 18:07:00: app| Failed to lookup owner for: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx. Reason: No such file or directory Nov 28 18:07:00: app| Attempting to launch vmx : /E/vmware/CentOS 5/CentOS 5.0 x86.vmx Nov 28 18:07:01: app| Error during launch: 9, The config file /E/vmware/CentOS 5/CentOS 5.0 x86.vmx is not registered. Nov 28 18:07:01: app| Please register the config file on the server. For example: Nov 28 18:07:01: app| vmware-cmd -s register "/E/vmware/CentOS 5/CentOS 5.0 x86.vmx" Nov 28 18:07:01: app| VmsdVmStatePendingCmdFailed: cmd status is already set Nov 28 18:07:27: app| VmsdRegister: Config file has changed: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx Nov 28 18:07:27: app| Error monitoring the file: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx: error: No such file or directory Nov 28 18:11:35: app| Accepted new connection at 36 for thread server (0x8301ae8) Nov 28 18:11:35: app| IPC version negotiation version: VMServerd returning 2.1 to server Nov 28 18:11:35: app| IPC vmcontrol-temp version: VMServerd returning 11.4 to server that tried 11.4 Nov 28 18:11:35: app| VMServerd IPC closed the connection with thread server (0x8301ae8) Nov 28 18:11:35: app| VMServerd: server disconnected. Nov 28 18:12:20: app| Accepted new connection at 36 for thread server (0x8301ae8) Nov 28 18:12:20: app| IPC version negotiation version: VMServerd returning 2.1 to server Nov 28 18:12:20: app| IPC vmcontrol-temp version: VMServerd returning 11.4 to server that tried 11.4 Nov 28 18:12:20: app| VMServerd IPC closed the connection with thread server (0x8301ae8) Nov 28 18:12:20: app| VMServerd: server disconnected. Nov 28 18:12:27: app| VmsdRegister: Config file has changed: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx Nov 28 18:12:27: app| VM suddenly changed state: poweredOff. Nov 28 18:12:27: app| VM suddenly changed state: poweredOff. Nov 28 18:12:47: app| Accepted new connection at 34 for thread server (0x8301ae8) Nov 28 18:12:47: app| IPC version negotiation version: VMServerd returning 2.1 to server Nov 28 18:12:47: app| IPC vmcontrol-temp version: VMServerd returning 11.4 to server that tried 11.4 Nov 28 18:12:47: app| Failed to lookup owner for: /F/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Failed to lookup owner for: /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Failed to lookup owner for: /home/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Failed to lookup owner for: /F/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Failed to lookup owner for: /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Failed to lookup owner for: /home/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 18:12:47: app| SP: Removing VM: /E/vmware/CentOS 5/CentOS 5.0 x86.vmx Nov 28 18:12:47: app| VMServerd IPC closed the connection with thread server (0x8301ae8) Nov 28 18:12:47: app| VMServerd: server disconnected. Nov 28 18:12:47: app| The vm-list file has changed! Reloading the list of registered vms Nov 28 18:12:47: app| Failed to lookup owner for: /F/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Could not get canonical path for /F/vmware/Windows XP Professional/Windows XP Professional.vmx: No such file or directory Nov 28 18:12:47: app| Error Adding vm: /F/vmware/Windows XP Professional/Windows XP Professional.vmx Nov 28 18:12:47: app| Failed to lookup owner for: /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Could not get canonical path for /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx: No such file or directory Nov 28 18:12:47: app| Error Adding vm: /C/vmware/WindowsXPPro2/Windows XP Professional 2.vmx Nov 28 18:12:47: app| Failed to lookup owner for: /home/vmware/Windows XP Professional/Windows XP Professional.vmx. Reason: No such file or directory Nov 28 18:12:47: app| Could not get canonical path for /home/vmware/Windows XP Professional/Windows XP Professional.vmx: No such file or directory Nov 28 18:12:47: app| Error Adding vm: /home/vmware/Windows XP Professional/Windows XP Professional.vmx
There should be only two registered VMs: /G/vmware/Windows... and /E/vmware/CentOS...
I have since unregistered the CentOS machine, and it still runs with a brief hang every time I click the mouse anywhere in the VM window.
I'll look into the other VMs - they should all have been deleted (the files do not, in fact, exist).
Thanks.
mhr
On Nov 29, 2007 1:47 AM, Mark Hull-Richter mhullrich@gmail.com wrote:
In the last few days, I have noticed a drastic slowdown in my VMware Windows guest OS.. I recently bit the bullet and upgraded it from XP SP1 to SP2, and that seemed to work fine for quite a few days.
It is always a good idea to look into the windows log for warning or error. Maybe some disk read error ?
The two major changes I made to the system recently were:
- The most recent update from CentOS (can't remember which one, but
it was within the last two weekd for 5.0).
- Adding another VM guest OS, this one a CentOS 5.0 guest.
What happens is, usually when I click the mouse in the Windows window, the system hangs up completely for some period of time that usually exceeds four minutes. Thereafter, once the VM is "running," it will occasionally just stop when I am transitioning into the VM from elsewhere.
I verified this using the CentOS system clock - last night it stopped at 23:01 and still read 23:01 when my cell phone, which is usually dead on in sync with the system clock, read 11:04pm.
I cut back on the amount of memory allowed to the Windows VM (768MB, down from 1GB) and that seemed to help a little, but I have 2GB and I'm thinking that this should not be a problem.
Any input would be helpful.
Thanks.
mhr
P.S.: Now I'm thinking that my earlier remark about applications was a bit overstated.... _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Nov 28, 2007 5:35 PM, Alain Spineux aspineux@gmail.com wrote:
On Nov 29, 2007 1:47 AM, Mark Hull-Richter mhullrich@gmail.com wrote:
In the last few days, I have noticed a drastic slowdown in my VMware Windows guest OS.. I recently bit the bullet and upgraded it from XP SP1 to SP2, and that seemed to work fine for quite a few days.
It is always a good idea to look into the windows log for warning or error. Maybe some disk read error ?
Sorry, which log are you referring to?
mhr
On Nov 29, 2007 3:29 AM, Mark Hull-Richter mhullrich@gmail.com wrote:
On Nov 28, 2007 5:35 PM, Alain Spineux aspineux@gmail.com wrote:
On Nov 29, 2007 1:47 AM, Mark Hull-Richter mhullrich@gmail.com wrote:
In the last few days, I have noticed a drastic slowdown in my VMware Windows guest OS.. I recently bit the bullet and upgraded it from XP SP1 to SP2, and that seemed to work fine for quite a few days.
It is always a good idea to look into the windows log for warning or error. Maybe some disk read error ?
Sorry, which log are you referring to?
The event viewer!
mhr
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Nov 28, 2007 7:05 PM, Alain Spineux aspineux@gmail.com wrote:
The event viewer!
I'll look, but, as much as I don't care for Windows, I don't think this is a Windows problem at all. If it were, it would only hang the vm, not the host and everything running on it, or so I would guess.
The vmware serverd log shows a hole of about an hour and twenty minutes with no entries at all.
I went in and removed all traces of the deleted vms that I could find, and that seemed to help a little, but it still has problems doing anything when the mouse moves or is clicked.
I just realized that I installed a replacement k/b/m last week. I've been using a Logitech EX110 cordless k/b/m for about a year or so, and the number pad went south. Logitech sent me a new set, and I just plugged it in. It seems to work fine, although the mouse takes more than a touch to wake up (now).
But, I have rebooted at least twice, so I would expect that to have taken care of the problem.
mhr
-
Alain Spineux -
Mark Hull-Richter -
Ray Van Dolson