Kobridge Forum  

Go Back   Kobridge Forum > Technical Solution Center [기술정보센터] - Korean, English Mixed Topics > Computer Center [컴퓨터]

Computer Center [컴퓨터] Computer related information is in this place [컴퓨터와 관련된 정보 저장소]

 
 
Thread Tools Rating: Thread Rating: 5 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 06-26-2009, 10:41 PM
JJ's Avatar
JJ JJ is offline
Administrator
 
Join Date: Jan 2006
Posts: 285
JJ is on a distinguished road
Default VMWARE Workstation - Not able to launch more than two guest machine

This post is for the users who purchased iBUYPOWER Core i7-920 2.66GHz 1GB ATI 4870 HD from COSTCO. If you are using this machine for your VMWARE, you may experience the following issue.

From the Vista Home premium x64 host machine, not able to launch more than 2 guest machines regardless of guest operating system.
Vista host fails with the following errors:

Jun 26 21:24:05.144: vmx| VMware Workstation has measured your CPU speed to be 2664 MHz, but Windows reports that it is 2793 MHz. This may mean that your computer has a power-saving feature that varies the processor speed. As a result, the clock in your virtual machine may run too fast or too slow.
Jun 26 21:24:05.144: vmx|
Jun 26 21:24:05.144: vmx| For a workaround, please refer to the VMware knowledge base article at:
Jun 26 21:24:05.144: vmx| http://vmware.com/info?id=97---------------------------------------
Jun 26 21:24:05.359: vmx| VMAutomation_ReportEvent: Received event (type 5) before power on; ignoring it.
Jun 26 21:24:05.359: vmx| VMMon_RememberkHzEstimate: Calculated 2793000 kHz
Jun 26 21:24:05.360: vmx| CPU # 0 TSC = 552680262205
Jun 26 21:24:05.360: vmx| CPU # 1 TSC = 552680262000
Jun 26 21:24:05.360: vmx| CPU # 2 TSC = 552680261952
Jun 26 21:24:05.360: vmx| CPU # 3 TSC = 552680262063
Jun 26 21:24:05.360: vmx| CPU # 4 TSC = 552680262173
Jun 26 21:24:05.360: vmx| CPU # 5 TSC = 552680261947
Jun 26 21:24:05.360: vmx| CPU # 6 TSC = 552680262153
Jun 26 21:24:05.360: vmx| CPU # 7 TSC = 552680262004

...................

Jun 26 22:11:19.632: vmx| LOG failed to remove stats\stats32-2 failed: The system cannot find the path specified
Jun 26 22:11:19.632: vmx| LOG failed to rename stats\stats32-1 -> stats\stats32-2 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to rename stats\stats32-0 -> stats\stats32-1 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to rename stats\stats32 -> stats\stats32-0 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to remove stats\stats64-2 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to rename stats\stats64-1 -> stats\stats64-2 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to rename stats\stats64-0 -> stats\stats64-1 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to rename stats\stats64 -> stats\stats64-0 failed: The system cannot find the path specified
Jun 26 22:11:19.633: vmx| LOG failed to remove stats32-2 failed: The system cannot find the file specified
Jun 26 22:11:19.633: vmx| LOG failed to remove stats64-2 failed: The system cannot find the file specified

.............................

Jun 26 21:24:37.447: vmx| AIOWIN32C: 'E:\VM\Venus\Venus - XP test.vmdk' : Failed to read: Insufficient quota to complete the requested service (1453).
Jun 26 21:24:37.447: vmx| VMXAIOMGR: Retry on read "E:\VM\Venus\Venus - XP test.vmdk" : Insufficient quota to complete the requested service.
Jun 26 21:24:37.447: vmx| VMXAIOMGR: system : err=371970 errCode=1453 freeSpace=380284219392
Jun 26 21:24:37.447: vmx| VMXAIOMGR: "E:\VM\Venus\Venus - XP test.vmdk" : read s=2675572736 n=36864 ne=9
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[0]=4887000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[1]=488B000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[2]=470C000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[3]=48B7000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[4]=48AB000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[5]=4712000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[6]=4716000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[7]=4720000:4096
Jun 26 21:24:37.447: vmx| VMXAIOMGR: v[8]=472A000:4096
Jun 26 21:24:37.447: vmx| AIOWIN32C: 'E:\VM\Venus\Venus - XP test.vmdk' : Failed to read: Insufficient quota to complete the requested service (1453).
Jun 26 21:24:37.448: vmx| VMXAIOMGR: Retry on read "E:\VM\Venus\Venus - XP test.vmdk" : Insufficient quota to complete the requested service.
Jun 26 21:24:37.448: vmx| VMXAIOMGR: system : err=371970 errCode=1453 freeSpace=380284219392
Jun 26 21:24:37.448: vmx| VMXAIOMGR: "E:\VM\Venus\Venus - XP test.vmdk" : read s=2675572736 n=36864 ne=9
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[0]=4887000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[1]=488B000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[2]=470C000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[3]=48B7000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[4]=48AB000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[5]=4712000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[6]=4716000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[7]=4720000:4096
Jun 26 21:24:37.448: vmx| VMXAIOMGR: v[8]=472A000:4096

Solution:

The problem was on the Memory which is coming with IBUYPOWER machine sold in Costco (See the thread, http://www.kobridge.com/Forums/showthread.php?t=494). After returning the PC to Costco, I rebuilt the PC with totally new configuration - different motherboard, HD, DDR3 memory, graphics card but stayed same with DVD Drive, CPU. If you are using the PC purchased from Costo and pre-built by iBuypower, be sure that you are testing out all the fuctions that you need before the 90 days you purchased PC. After 90 days, there is no option that you could return the PC. If you do not use VMware or HDTV monitor like Samsung, you may not need to worry about that.... but worries about the future upgrade because of 16GB maximum memory.

Possible resolution on the existing iBUYPOWER machine is,
1. Replace the current memory with Consair XMS DDR3 memory
2. If the memory exchange does not work, then place any separate PCI Network card and try it again.

Hope this help.
__________________
Thanks for reading,
J.J.

Last edited by JJ; 07-16-2009 at 04:32 PM.
Reply With Quote
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump


All times are GMT -4. The time now is 06:37 PM.


Copyright ©2000 - 2018, Kobridge Co.
이곳의 모든 내용은 허락없이 사용, 복제를 금합니다.