Jan 19 2009
Intel releases patch for IPMI driver causing conflicts in Microsoft Hyper-V (General Access Denied error)
Users of S3000 & S5000V/X/S chipsets running on Microsoft Windows Server 2008 will experience “General Access Denied” error when Hyper-V host machine is restarted after Intel IPMI driver installation.
IPMI or “Intelligent Platform Management Interface” is a piece of software that sends status messages from vital system parts also allowing management applications to interact at low level hardware layers for real-time system health checks (yes, also temperatures, fan speeds, voltages, etc.) / configuration changes.
Intel IPMI driver is installed by one of the following products: Intel Active System Console 3.0; Intel Server Management Pack 3.0; Intel One Boot Flash Update Utility 9.7; Intel System Configuration Utility for Windows 5.0.1 & Intel System Event Log Viewer (SEL) 2.0.1.
If you we’re unlucky, like I was, after installing the IPMI driver which is a must for the above Intel applications to function correctly, Hyper-V will be unable to start any of your virtual machines with a “General Access Denied” error.
Adding other virtual machines will also fail with the same error. What is actually happening is that somehow the Intel IPMI driver is messing with the NTFS ACLs of all the virtual HDD (*.VHD) files. Instead of the actual built-in Hyper-V account there are orphan SID entries. Trying to restore the NTFS ACLs to the original state will do no good. Some suggested to grant access to everyone group with full control to the VHD file or even adding the system account under local admin group (trust me, it will not work). Trying to uninstall the Intel IPMI driver and revert back to the IPMI driver provided by default from Microsoft, leads to same Hyper-V error.
From what I’ve seen until now, reinstall of the system is the only viable solution, or, if you have a back-up handy, you’re in luck as the system restore process in Windows 2008 is working like a charm (another reason to keep your boot partition as clean as possible: less to re-install / less to backup).
As far as I know this issue dates back to the introduction of Hyper-V in February 2008. In November 2008, Intel releases a fix for the issue. The problem is briefly described in Intel Technical Advisory 922 (TA-0922-1). A small program “ResetAccess.exe” build by Intel can be executed which resets the NTFS ACLs entry on VHD files. After the program is executed, the server must be restarted. The tool itself can be downloaded directly here.
Intel announced that future release of IPMI driver, scheduled for Q1 2009 will fix interference with Windows 2008 Hyper-V enabled systems / then again, Microsoft is planning for both Windows Server 2008 SP2 & Windows Server 2008 R2 (which will also bundle Hyper-V 2.0 and SCVMMC). I hope Intel & Microsoft will not “patch” each other out.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.