Problem with dual e5320 processors - is there a fix on the way?

-

just installed w2k8 , hyper-v on ibm x3400 server. updated drivers , system bios.  when trying start new or imported vm error "the virtual machine could not start because hypervisor not running".  verifed processors on the approved list, dep turned on , virtualization turned on in bios.  looking through logs found , event id 48 said hyper-v launch failed; processsor 0x4 not provide features necessary run hyper-v (leaf 0xa, register 0x3: features needed 0x0, features supported 0x503).

upon further investigation learned hyper-v has problem  some intel processors posting

http://drewh70.wordpress.com/category/technology/microsoft/windows-server/windows-server-2008/hyper-v/

i did poster recommended , can run vms utilizing 1 processor.  there patch coming out or there can full use of clients server.  have egg on face suggested since had new server could go virtual environment , host couple of virtual servers on 1 physical server.

running hyper-v ver 6.0.6001.18016

dual intel e5320 1.86ghz processors

thanks

bret

issue supposed resolved in rtm release of hyper-v.  first thing recomend doing seeing if there bios updates available system.
cheers,
benjamin armstrong
============================
windows virtualization
senior lead program manager

posting provided no warranties, , confers no rights. assume risk use.


Windows Server  >  Hyper-V



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more