Michael Smolens
asked on
New HyperV 2012 Cluster - Trying to create new VM on a CSV disk.
Okay so I ran into another issue and I am hoping that you can help. I created the cluster added a 100GB volume to the storage to use for a Virtual Machine. I then made the 100GB volume a CSV and can see the volume located in the c:\ClusterStorage folder.
My problem is when I try to create a VM on the CSV it failes with the error The computer "localhost" failed to perform the requested operation because it is out of memory or disk space. When I try to create a virtual on a none CSV disk it seems to work fine. What could I be missing, I have been trying to fiqure this one out for a few hours now with no luck... Call me insane b/c I keep doing the same things over and over and expecting a different result... :)
Thanks for your help and time!
My problem is when I try to create a VM on the CSV it failes with the error The computer "localhost" failed to perform the requested operation because it is out of memory or disk space. When I try to create a virtual on a none CSV disk it seems to work fine. What could I be missing, I have been trying to fiqure this one out for a few hours now with no luck... Call me insane b/c I keep doing the same things over and over and expecting a different result... :)
Thanks for your help and time!
I am having this exact problem as well - any input would be appreciated.
Try restarting WMI Service and Hyper-V services (all including dependencies) and then see if you get this error ?
Got this one a while a go and the following fixed it for me :
1. Open task manager
2. End WmiPrvSE.exe
3. Close task manager
4. Re-open Hyper-V Manager
Got this one a while a go and the following fixed it for me :
1. Open task manager
2. End WmiPrvSE.exe
3. Close task manager
4. Re-open Hyper-V Manager
ASKER
I tried to restart the WMI Service and HyperV with no luck. I also tried to end all WMIPRVSE .EXE Tasks, which seem to start again right away. Still no luck.
ASKER
@glenn10 - Do you have McAfee installed on the host?
I think I may have found the issue...
I uninstalled McAfee 8.8 w/ p3 and looks like that fixed the issue. I was able to create a VM on the CSV.
Now the question is should I just disable McAfee from scanning the c:\storagecluster folder and reinstall?
I think I may have found the issue...
I uninstalled McAfee 8.8 w/ p3 and looks like that fixed the issue. I was able to create a VM on the CSV.
Now the question is should I just disable McAfee from scanning the c:\storagecluster folder and reinstall?
Hi BayCCS
I am running Mcafee. Ive temporarily disabled access protection and on demand scan which resolved other issues i ran into regarding hyper V. Looks like ill be uninstalling completely and testing. Thanks for the update!
I am running Mcafee. Ive temporarily disabled access protection and on demand scan which resolved other issues i ran into regarding hyper V. Looks like ill be uninstalling completely and testing. Thanks for the update!
Yes you should exclude virus scanning for your Vm folders and disks ...
Glad to know its fixes :-)
Glad to know its fixes :-)
ASKER
So I went into my EPO server edited the On-Access Default Processes Policy for VS 8.8 and created an item exclusion with the string "C:\ClusterStorage\*.* with the subfolders also excluded. With this I am still getting the error. If I uninstall McAfee 8.8 everything is good, but once installed it causes the above mess....
Is there anything else that I can exclude or add to the policy to prevent this?
Is there anything else that I can exclude or add to the policy to prevent this?
Hi BAYCCS - try these additional exclusions for the cluster
•The path of the \mscs folder on the quorum hard disk. For example, exclude the Q:\mscs folder from virus scanning.
•The %Systemroot%\Cluster folder.
•The temp folder for the Cluster Service account. For example, exclude the \clusterserviceaccount\Loc al Settings\Temp folder from virus scanning. (this one may not apply)
•The path of the \mscs folder on the quorum hard disk. For example, exclude the Q:\mscs folder from virus scanning.
•The %Systemroot%\Cluster folder.
•The temp folder for the Cluster Service account. For example, exclude the \clusterserviceaccount\Loc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looks like we will be waiting for patch4 then... :)
Sometimes i have such problems on my 8-node testing cluster. Also McAfee 88p3.
But before i could not place over 10 VMs on 1 Hypervisor. Now I can locate up to 16 VMs (48 Gb of RAM is only physical limit for me).
Workaround is to Live Migrate VM to other node.
It works for me
But before i could not place over 10 VMs on 1 Hypervisor. Now I can locate up to 16 VMs (48 Gb of RAM is only physical limit for me).
Workaround is to Live Migrate VM to other node.
It works for me