If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by going to the following location in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor
Or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm
And changing the 'Start' value to '4'.
In the mean time we have made some subtle changes to the way our hardware exposes the processor in Virtual Server R2 so that in future products these drivers should never get loaded inside of virtual machines.
http://blogs.msdn.com/b/virtual_pc_guy/archive/2005/10/24/484461.aspx
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor
Or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm
And changing the 'Start' value to '4'.
In the mean time we have made some subtle changes to the way our hardware exposes the processor in Virtual Server R2 so that in future products these drivers should never get loaded inside of virtual machines.
http://blogs.msdn.com/b/virtual_pc_guy/archive/2005/10/24/484461.aspx
Комментариев нет:
Отправить комментарий