Dear all
Hello,
I currently run 10 operating systems (Windows 10) simultaneously by VMware Workstation 15, on a powerful server device; and I think this server device has enough resources, initially the project work good with few problems, one of this problem I faced which happened only one time yet is severe hang in the device (host) and the following messages appeared:
Actually, I don’t know what exactly the problem, anyway I solved this problem by just restart the host and after the restart, I turned on virtual machine, and worked good.
But my question, what the mean of this messages ?, what the reason for this problem? How can I prevent this problem from happening again?
This is to avoid this problem from happening again.
Thank you
This issue occurs if there are issues with the underlying storage, which results in subsequent writes to the NVRAM file to fail.
Make sure you have enough storage to run all the virtual machines and you will not run into the issue again.
Firstly, thank you for your response
Secondly, from the start of my project I purchased an external hard disk SSD 1 TB to avoid such problems; Currently all virtual machine files on this external hard drive; Currently there is an unused free space on this external hard drive, about 700 GB. so what is the problem ?!
It's not about free space, it's about there being too much I/O to this disk either as a result of the interface (how the external drive is connected), the enclosure and its quality, or the drive itself. You've probably run into one of those bottlenecks as a result of trying to run too many VMs concurrently.
Excuse me, I am not an expert like you; But simply what can I do to avoid this problem from happening again?
Turn off some of your VMs.
Ok, but What about move some VMs to another Hard desk. for example put 5 VMs on Hard desk, and 5 VMs on another hard desk, is this will contribute to solve the problem ?
Yes. That might solve it too. You can monitor the storage usage and performance on your Windows performance monitor. See if the disk usage is hitting 100% all the time.
What is running on these machines? Are they storage intensive applications?
Ok, fine
running on VMs just Windows 10 LTS (the most lite versions) with remove all applications not necessary + Accounting software (not heavy, and not including Database) SQL and database already running on server device.
Also, I made something to help the server device, I dedicated some of external hard drive to support Virtual memory in server device (100,000 MB), as this picture:
Also, I have idea, but I don't not will make difference or not in my case,
Which is better open 10 VMs concurrently in one instance (ten tabs in one instance) or open 10 instances (one VM per instance) ??
Finally, thank you so much for your help.
Have you considered using a more efficient hypervisor such as ESXi for running that many VMs?
There is a free version known as vSphere Hypervisor.
You might need different hardware components to run it, as it has a limited driver set compared to Windows - but it is much more efficient and robust.
For vSphere Hypervisor, I will take it in consideration seriously.
Thanks
I also think what you've done with your pagefile might make things worse - you now have it on the same partition as the VMs, so if it is used by the host OS that will just generate more IO to the same device.
What is the "power server device" do you have a model? I'd suggest installing internal driver vs external if there is room instead of USB, if your drive is using USB 2 or lower its very likely its the USB controller that's too slow. Also
Mr.scott28tt
I don't understand exactly what you mean by your last response , because I'm not a specialist or an expert in this field, but your response make me worry.
In the worst case scenarios the project will fail ok; But the question is, can the server device be damaged , for example one of the components like CPU may damaged??
Your issue is too much IO on that storage device from the VMs you have placed there, and now you have set your Windows page file to be on the same disk - which can cause disk IO.
So you MIGHT have made your current problem worse.