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

Generating Event ID 91, 44 with CA (In Event Viewer with source as Certsvc)

-
hi we in process of migrating win 2003 ad win2008 r2. when noticed logs found many errors , warning alerts ca below --could not connect active directory. certificate services retry when processing requires active directory access. (event id 91)----certificate services sagia ca can not open certificate store @ cn=ntauthcertificates,cn=public key services,cn=services in active directory's configuration container. (event id 94, warning)--                                                                                            ...
Read more

Group policy default policy cannot be edited because network name not found

-
hey everyone, i have been having issues on , off domain. pdc crashed (the domain controller). started old server , made domain controller , forced roles over. repaired pdc , elevated back. although appeared work found cannot rid of other dc because pdc can no longer contact domain things group policy or else. start secondary , domain magically reachable. although while secondary down can ping domain , replies ip of pdc appears pdc has no control on anything. questions following. 1. gpos created before crash no longer work. rebuilt sysvol , default problem can't edit default domain policy. don't believe having replication problems new repairing domains setting them , maintaining them of education came from.  2. if pdc gpo management console can't access gpos can secondary not have installed? 3. why domain unreachable if no dcs online when shutdown secondary. thanks in advance , try edit dc diag log right there on fails want narrow of out guys concentrate on...
Read more

Problem when changing update source

-
hi all, we use win server 2008 r2 enterprise , wsus 3.2. until last friday, downoloading updates microsoft's website. had change the source wsus server in our headquarters (not being replica server). started problem: our product , classification changed, downloading lot of updates hadn't ever downloaded. now, when try modify update soure (to microsoft's web site again) set option console falls down - database error - , copying error clipboard, have message bellow: the wsus administration console unable connect wsus server database.     verify sql server running on wsus server. if problem persists, try restarting sql.     system.data.sqlclient.sqlexception -- maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32). info:spsetconfiguration - synctomu or upstreamservername config value changed - no reset source .net sqlclient data provider stack trace:    @ microsoft.updateservices.ui.admi...
Read more