hyperv clustering in 2008 on nodes with different processors
hi,
i have question failover clustering of hyperv since not understand how underlying hypervisor interprets this. preface saying working, want understand doing make work.
i have 2 dell servers, 1 2950 w/ dual quad core 3.16ghz xeon x series procs (server a), other 1950 dual quad core 1.83ghz xeon e series procs (server b).
i have both nodes set in failover cluster hyperv , works great. virtual machine in question vm server 2008 x86 standard installed. if start vm on server , go system properties of vm shows having sigle 3.16 ghz proc suspected. if tell failover serverb in failover clustering manager fails on appropriately , has 5 seconds of down time. once , running on server b if go system properties still shows having single 3.16 ghz proc (even though physical procs in server b 1.83ghz).
if reboot vm on server b, after comes in system properties of vm shows having single 1.83ghz proc. if reverse operation fail on server a, , once failed on , online go system properties sill shows havinga 1.83ghz proc (even though server b, physical host has 3.16ghz procs).
what going on 'behind scenes'? appropriate emulation make work? want understand if vm started on server , fails on server b if there issues cpu's not being identical.
thanks much.
/ehren
i have question failover clustering of hyperv since not understand how underlying hypervisor interprets this. preface saying working, want understand doing make work.
i have 2 dell servers, 1 2950 w/ dual quad core 3.16ghz xeon x series procs (server a), other 1950 dual quad core 1.83ghz xeon e series procs (server b).
i have both nodes set in failover cluster hyperv , works great. virtual machine in question vm server 2008 x86 standard installed. if start vm on server , go system properties of vm shows having sigle 3.16 ghz proc suspected. if tell failover serverb in failover clustering manager fails on appropriately , has 5 seconds of down time. once , running on server b if go system properties still shows having single 3.16 ghz proc (even though physical procs in server b 1.83ghz).
if reboot vm on server b, after comes in system properties of vm shows having single 1.83ghz proc. if reverse operation fail on server a, , once failed on , online go system properties sill shows havinga 1.83ghz proc (even though server b, physical host has 3.16ghz procs).
what going on 'behind scenes'? appropriate emulation make work? want understand if vm started on server , fails on server b if there issues cpu's not being identical.
thanks much.
/ehren
when vm booted, processor speed checked , written registry (where gets pulled , shown in system properties). if processor speed changed (like in case), isn't refreshed until reboot.
make sense? :)
this posting provided "as is" no warranties, , confers no rights.
Windows Server > Hyper-V
Comments
Post a Comment