When you attempt to start a MED-V 1.0 workspace using a test image or a deployed image, the Virtual PC engine may crash and generate a Fault Report using Windows Error Reporting. Subsequently, the MED-V Workspace will fail to start.
The Virtual PC engine crash will show the following fault:
{virtual pc.exe, 6.0.210.0, unknown, 0.0.0.0, ffff08ef}
You will also see the following event in the Application Event Log:
Log Name: Application
Source: MED-V Workspace
Date: 9/22/2009 12:24:30 PM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: CSS-W013
Description:
The following information was included with the event:
Failed intializing the service log: System.TimeoutException: Timed out waiting for the shared memroy client to initialize
at Kidaro.Foundation.Log.PrettyLogProxy.InitializeSharedMemoryClient()
at Kidaro.Foundation.Log.PrettyLogProxy.Start()
at Kidaro.Workspaces.Service.WorkspaceService.ServiceStartThread()
Failed intializing the service log: System.TimeoutException: Timed out waiting for the shared memroy client to initialize
at Kidaro.Foundation.Log.PrettyLogProxy.InitializeSharedMemoryClient()
at Kidaro.Foundation.Log.PrettyLogProxy.Start()
at Kidaro.Workspaces.Service.WorkspaceService.ServiceStartThread()
Cause
This can happen if the MED-V Workspace (the workspace installation) binaries have been installed along with the client on the physical host machine. The MED-V workspace installer should only be run inside the virtual machine being used to create the workspace.
To resolve this issue, please do the following:
1.) Uninstall both the MED-V Workspace and the MED-V Client.
2.) Reinstall the MED-V Client.
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
