Trying to find where to post a BUG in Hyper-V on Win 8 and Win 2012 Server
-
Friday, September 28, 2012 11:06 AM
Trying to find where to post a BUIG in Hyper-V on Win 8 and Win 2012 Server, not looking to pay Microsoft for a support case since I have identify an issue.
Here is the Info:
I can now confirm Issues with hard drives being recognized by Windows Server 2012 and Hyper-V, while using the 5th SATA port ( RED SATA eSATA 4) on Intel DH67BL & DH67GD motherboards. Windows Server can recognize the drive and will operate properly, but Hyper-V has issues recognizing the hard drive and showing ""any"" folder structure on any hard drive connected to the SATA (eSATA) port on the motherboard.
When in Hyper-V manager or even SCVMM 2012, HYper-V only sees the drive letter, and SCVMM 2012 does even see the drive letter.
This issue is being experienced on two Windows 2012 Servers, using Intel motherboard, and also issues have been experienced with Win 8 Pro with Hyper-V and drives.
So this means there are three Intel motherboards experiencing issues when using the internal 5th SATA (eSATA port - internal Red ëSATA Connector on Board).
I suspect other users who are having VHD creation issues on drives are also working on newer motherboards.
Note: This issue is was not experienced when using Windows Server 2008R2 and SCVMM 2008R2
Hope this helps.......
Other links to users postings, along with mine....
RF
- Edited by RUOK2 Monday, October 08, 2012 9:05 AM
All Replies
-
Friday, September 28, 2012 2:50 PMModerator
Go to connect.microsoft.com
Create an account if you don't have one.
Find Windows Server.
File your bug.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Friday, September 28, 2012 3:57 PM
I did, and I have a TechNet account...but there is no acceptance for Windows Server 2012...nor hyper-v......and my only other option is to Pay to Communicate with MS. And that's not gonna happen .....
Unless there is something else I am missing .....there is no way to file a bug unless they keep the product in Open phase....and I checked for anything Win Serv, Hyper-V, even SCVMM....no way to file.....all closed....
Kinda Stupid ....its not like bugs go away just because they closed "accepting" them.
RF
-
Friday, September 28, 2012 4:42 PMsame thing for me. Unable to submit a bug...
-
Friday, September 28, 2012 4:45 PMModerator
I feedback into Windows Server. Eventhough it is not "2012" it is still worked.
There has never been a Hyper-V specific Connect site, it has always been through Server. Primarily to support triage, since Hyper-V takes advantage of many feaures of Server (or the kernel core) that very few bugs actaully belong to the hypervisor, most are at other layers and actaully end up on the plates of other feature teams.
For SCVMM it is "system center in the datacenter and cloud" - it is all of system center.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.- Marked As Answer by Clarence ZhangModerator Tuesday, October 09, 2012 3:23 AM
-
Friday, September 28, 2012 4:52 PM
Well I just quadruple checked Connect, and did a search for Windows Server 2012 or just windows server( again) and there is no feedback or bug report specific to the OS.
These are the options:
Windows MultiPoint Server WMS 2012 Public Beta Join <input type="hidden" value="16" /> Bugs & Suggestions <input type="hidden" value="3" /> Secure <input type="hidden" value="3" /> 7/16/2012 <input type="hidden" value="2012-07-16T13:53:45" /> 
Windows Server Windows Server 2012 Essentials Pre-Release Feedback Site Join <input type="hidden" value="16" /> Bugs <input type="hidden" value="1" /> Secure <input type="hidden" value="3" /> 5/4/2012 <input type="hidden" value="2012-05-04T16:56:33" />
Windows MultiPoint Server Windows MultiPoint Server 2011 Public Beta - Archive Join <input type="hidden" value="16" /> None (read only) <input type="hidden" value="4" /> Secure <input type="hidden" value="3" /> 10/15/2010 <input type="hidden" value="2010-10-15T16:50:27" /> 
Windows Server Solutions Windows Small Business Server Public Connection Join <input type="hidden" value="16" /> Bugs & Suggestions <input type="hidden" value="3" /> Secure <input type="hidden" value="3" /> 5/9/2008 <input type="hidden" value="2008-05-09T12:41:32" />
Windows Server Solutions Participate <input type="hidden" value="40" /> Bugs <input type="hidden" value="1" /> Registered <input type="hidden" value="2" /> 2/28/2006 RF
-
Friday, September 28, 2012 4:59 PMModerator
I am submitting it for you folks.
We will see if it gets traction.
Thanks and sorry for that.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Friday, September 28, 2012 5:12 PM
Thanks.......
No Problem .....
As I was saying though....You would think they would make it easier, and also not close out from accepting Bugs.....I would think this would be a constant open door, more so with an OS that has not officially released....
I had compiled to posting on top so that they may summarize the issue without having to read a lot of postings / details.
Thanks!
Hey I just noticed your http address ...Love it ....Speaks words for the whole industry.. and where some may keep their hands, as the saying goes..
Ron
RF
-
Friday, September 28, 2012 5:17 PMModerator
I dreamed that up years ago when I was doing IT (systems / network admin) at my third employer.
Thanks for your expertise and time digging into this.
BTW - since this issue is specific to a particular vendor partner, don't be surprised if you really don't hear an official response from a MSFT person. I have seen this type of thing before.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Monday, October 01, 2012 6:47 AMModerator
Hi,I did, and I have a TechNet account...but there is no acceptance for Windows Server 2012...nor hyper-v......and my only other option is to Pay to Communicate with MS. And that's not gonna happen .....
Unless there is something else I am missing .....there is no way to file a bug unless they keep the product in Open phase....and I checked for anything Win Serv, Hyper-V, even SCVMM....no way to file.....all closed....
Kinda Stupid ....its not like bugs go away just because they closed "accepting" them.
RF
If this is a blocking issue for you, i suggest that you open a paid support case to request a hotfix. The product team will consider a hotfix based on the business impact and risks involved. If it is the bug issue, then MS will pay back the fee.
But as this issue is invovled with the 3rd party hardware, I also suggest you ask the vendor for this compatibility issue.
Regards,
Clarence
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by Clarence ZhangModerator Monday, October 01, 2012 6:52 AM
-
Monday, October 01, 2012 8:50 AM
Hello,
Appreciate the feedback....
Not a blocking issue for me, as no one in their proper IT business mind would apply a new product in an production environment, at least until SP1.
In regards to paying to open a case with an issue with a Microsoft product, sorry but that is not an option I would ever consider, this is a Microsoft/Intel issue not an "end user" issue. For me to shell out money to report issues with MS/Intel is just ludacris.
Clearly this has to be resolved between MS and Intel, as this is not the first time an issue with chipset drivers has surfaced with MS/Intel.
Trying to help here, so it makes no sense that I should have to Pay/ Shell out $$, in hopes that they will address the issue, and hopefully obtain a credit.....
As I have stated in the previous posts, this issue is relevant to 3 newer models of Intel Motherboards and the 5th onboard eSATA port. If you want to pass this Posting along to the proper developers/ channels feel free, if not, wait until the official release, and the issue will be enhanced, and the workload increased.
Note: Clearly this IS a bug issue, as 3 newer Intel motherboards are experiencing the issue, Also, ALL three of these board worked fine with Windows Server 2008R2, hyper-V, SCVMM 2008R2. The issue is happening with BOTH Win 8 & Win Serv 2012. so that should tell you something with regards to product/ issues.
Regards,
Thanks for your thoughts
RF
- Edited by RUOK2 Monday, October 01, 2012 8:53 AM
-
Monday, October 01, 2012 3:14 PMModerator
Be aware, I have raised this bug and the forum references are serving as the documentation source.
Thank you RUOK2 for taking the time and bringing this up.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Monday, October 01, 2012 3:20 PM
Thanks Brian,
Hopefully they can address the issue before the release.
RF
-
Monday, October 01, 2012 3:25 PM
Hi RUOK2, Brain,
Thanks for brining this to our notice.
I am taking this to the product teams for investigation. The RTM build for both server and client is already built, so this might be something that will require a hotfix/update from intel or us, based on what we find after researching this. We really appreciate your feedback and testing on this.
Thanks again for reporting this.
Regards,
Vimal
- Marked As Answer by Clarence ZhangModerator Tuesday, October 09, 2012 3:23 AM
-
Monday, October 01, 2012 4:16 PM
Hi Vimal,
Yaaaaa Someone from the inside !!!
I will provide the Intel Chipset / BIOS versions, Chipset Driver Version, along with the Motherboard models that this issue is being experienced on/with.
Intel DP67DE motherboard
- Running Win 8 x64
- Chipset 6 Series
- Chipset Driver Version ( Only one available for Win 8 x64, is the "Intel tech Recommended" Win 7 x64 for which he stated it supports Win 8) Driver version: INF_allOS_9.3.0.1021_PV
- eSata attached SATA WD Hard Drive IS recognized and working with Win 8, but when trying to create a Hyper V VHD drive, on the eSATA attached Internal Drive it cannot be performed.
Error
Failed to add device "Virtual Hard Disk
Hyper-V VMM service account does not have permissions to open attachment
General Access Denied (0x80070005)
Intel DH67GD motherboard & Intel DH67BL motherboard
- Running Windows Server 2012 x64
- Chipset 6 Series
- Chipset Driver Version ( Only one available for Win 8 x64, is the "Intel tech Recommended" Win 7 x64 for which he stated it supports Win 8) Driver version: INF_allOS_9.3.0.1021_PV
- eSata attached SATA WD Hard Drive IS recognized and working with Win Server 2012, but when trying to create a Hyper V VHD drive, on the eSATA attached Internal Drive it cannot be performed.
Error
Failed to add device "Virtual Hard Disk
Hyper-V VMM service account does not have permissions to open attachment
General Access Denied (0x80070005)
Both of these servers can use the eSATA with no problems from the OS.
When using Hyper-V Manager local or remote, you cannot create a VHD file on the attached eSATA internal drive.
Error that occurs ONLY on the one drive in each Win 2012 server is the internally attached eSATA drive, all other drives work fine, more so after the chipset driver updates, as there were issue prior with more than 1 drive, but after the chipset update and the Reg Permissions Issue Fix listed in the link below that was recommended by MS a ways back for another Intel Server Board, I had experienced the same issue in the reg permissions after checking, and applied the fix , for which helped the other drives but not the eSATA attached drives.
Also, When using SCVMM 2012 CTP2, on both servers, and from a remote or local SCVMM console, the eSATA drive don't even display drive letter or directory structure, on the eSATA drives only - its as if the drive isn't even there.....but all other attached drives show full folder structure and drive letters fine.
The Win 2012 os itself has no problem with using the eSATA drives, Issue only pertains to Hyper-V & SCVMM 2012 CTP 2
Hope this helps !!
Regards,
RF
- Marked As Answer by Clarence ZhangModerator Tuesday, October 09, 2012 3:23 AM
-
Saturday, November 17, 2012 2:03 PM
RUOK2,Thanks so much for reporting this, it was a difficult one to narrow down, but we found the issue was happening because of a change in the way our auditing code works now. Here is what we have as a workaround to get you moving :
>> Check the audit policy on removable storage:
C:\Windows\system32>auditpol /get /subcategory:"removable storage"
System audit policy
Category/Subcategory Setting
Object Access
Removable Storage Success and Failure
>> Disable them for success and failure.
C:\Windows\system32>auditpol /set /subcategory:"removable storage" /success:disable /failure:disable
The command was successfully executed.
>> Check again to make sure auditing is disabled
C:\Windows\system32>auditpol /get /subcategory:"removable storage"
System audit policy
Category/Subcategory Setting
Object Access
Removable Storage No Auditing>> Check creation of the VM now.
>> Remove the policy to enable Audit object access from the machines. Open rsop.msc – and scroll down to – Computer Configuration > Windows Settings > Security Settings > Local Policies > Audit Policy. Check which Group policy object is defining this policy. Unlink this object or move the machine to an OU where this policy no longer applies. Then reboot the machine, confirm that the Object access policy shows “not defined”.
Then try creating the VM. -
Saturday, November 17, 2012 5:41 PM
HI,
You are very welcome......
I have tried what you have recommend, and it is not working. I still cannot create a VM on the specific HDrive connected to the internal port eSATA.
From my experience, and research this is related to the Chipset drivers, an is not a Local or Domain policy issue.
Thank You
Regards
Ron
RF
-
Sunday, November 18, 2012 12:15 AM
Oh ok, I apologize, I must have gotten confused between the threads I am tracking. We are still narrowing that one down. It looks like we have a couple of different scenarios where Access denied errors are popping up.
.png)
