Server 2008 Data Center x64 Hyper-V Host Crashes when Server 2008 Ent x32 Guest runs Windows Update
i have host hyper-v system running server 2008 data center x64 , created vm guest on system running server 2008 enterprise x32. pretty try run windows update on guest os host blue screens.... holy cow, builds confidence - if wrong thing in guest vm i'll kill host , of it's vm's... said holy cow! anyway, ideas? here setup @ moment:
host:
- ibm blade server hs21 32gb ram
- server 2008 data center x64
- joined our domain
- hyper-v role installed
guest (so far 1 guest os)
- server 2008 enterprise edition x32
- allocated 4gb ram vm
- vm located on san accessed via cifs file share (netapp)
- have preffered using iscsi targets multiple hyper-v hosts can't access same iscsi target far can tell sa can have multiple vm's on same iscsi target running on different hosts. problem appears resolved when 2008 r2 shipped
- installed integration services on guest
- launched ie , ran windows update
- while windows update scanning updates, watched host blue-screen.
- tried again, , same result dosn't seem happen @ same point it.
host:
- ibm blade server hs21 32gb ram
- server 2008 data center x64
- joined our domain
- hyper-v role installed
guest (so far 1 guest os)
- server 2008 enterprise edition x32
- allocated 4gb ram vm
- vm located on san accessed via cifs file share (netapp)
- have preffered using iscsi targets multiple hyper-v hosts can't access same iscsi target far can tell sa can have multiple vm's on same iscsi target running on different hosts. problem appears resolved when 2008 r2 shipped
- installed integration services on guest
- launched ie , ran windows update
- while windows update scanning updates, watched host blue-screen.
- tried again, , same result dosn't seem happen @ same point it.
first thing notice vm on cifs share.
msft not 'officially' support this.
it isn't solid enough production (regardless of jose's blog mentioning can done).
the first suggestion present vm in different way. in supported storage configuration.
multiple msft hosts can access same lun in r2 beta , r2 when released (when lun , vms both managed failover clustering only).
until each host must given own lun, or each vm must given own lun if using failover clustering provide high availability.
brian ehlert (hopefully have found useful)
msft not 'officially' support this.
it isn't solid enough production (regardless of jose's blog mentioning can done).
the first suggestion present vm in different way. in supported storage configuration.
multiple msft hosts can access same lun in r2 beta , r2 when released (when lun , vms both managed failover clustering only).
until each host must given own lun, or each vm must given own lun if using failover clustering provide high availability.
brian ehlert (hopefully have found useful)
Windows Server > Hyper-V
Comments
Post a Comment