MED-V 1.0: Errors that can occur when you allocate too little Memory to the Virtual PC

If you fail to allocate enough memory to the MED-V Guest Workspace operating system, you will find yourself having a tremendous amount of performance problems and possibly including the following errors:

“Your computer is running low on free memory. This may cause the Workspace to run slowly. Please close applications you are not using and try again.”

and/or

“Workspace ‘<NAME>’ failed to start. Please try starting the Workspace again.”

“Encountered an unexpected error. Internal error: Timed out waiting for VM to load: <IMAGENAME>”

The workspace policy option in MED-V v1 bases allocation of memory based upon a matrix constructed of specific memory allocations based on physical memory ranges on the host. Too often the memory is configured with the ratio allocatting an insufficient amount of memory to the workspace (i.e. where only 256MB memory is allocated to the workspace when the physical memory is 1GB or above; 128MB of memory if lower then 1GB of physical memory.)

The settings for these can be adjusted in the MED-V Management Console and confirmed in the ClientPolicy.XML file within the following section:

<PerformanceSettings>
              <WorkspaceId>27</WorkspaceId>
              <MemoryEnabled>true</MemoryEnabled>
            </PerformanceSettings>
            <MemoryRules>
              <WorkspaceId>27</WorkspaceId>
              <Host>0</Host>
              <VM>128</VM>
            </MemoryRules>
            <MemoryRules>
              <WorkspaceId>27</WorkspaceId>
              <Host>550</Host>
              <VM>192</VM>
            </MemoryRules>
            <MemoryRules>
              <WorkspaceId>27</WorkspaceId>
              <Host>1100</Host>
              <VM>256</VM>
            </MemoryRules>
            <Images>