We had a hardware issue recently where we need to service the hardware of one of our Hyper-V cluster hosts.\u00a0 The HP engineer originally believed there was an issue with the server’s motherboard so this needed to be replaced.\u00a0 So it was.\u00a0 This didn’t fix the problem – it turned out to be something else but that’s a tangent.<\/p>\n
When the server was fixed we brought it back online.\u00a0 Thanks to us using diskless blades and HP Virtual Connect, the OS and the data are stored on our fibre channel SAN.\u00a0 Nothing was damaged.\u00a0 The server started up and I tested VM failover using VMM.\u00a0 I was getting a failure of:<\/p>\n
"Error (2915) Recommended Action To debug I went into the Failover Cluster MMC.\u00a0 I expanded the service (VM) I was testing and expanded the properties.\u00a0 I failed it over.\u00a0 I could see the state saving and the disk going offline.\u00a0 However, the configuration would fail.\u00a0 The cluster would then move the VM to a working host.\u00a0 I tried a few more VM’s and then I had some luck.\u00a0 A VM stayed on the "bad" host after failing.<\/p>\n I went into the Hyper-V MMC and tried to start the VM there.\u00a0 I was told that:<\/p>\n "The virtual machine could not start because the hypervisor is not running".<\/em><\/p>\n Ah!\u00a0 The penny had dropped?\u00a0 There are two BIOS requirements for Hyper-V to work.\u00a0 CPU virtualisation assistance and DEP must be enabled.\u00a0 In a HP Proliant, they are in something like Advanced – Processor Options.\u00a0 My motherboard had been replaced, flashed with an upgrade and the old settings would be in the replaced motherboard.\u00a0 I enable the settings (requiring a reboot) and fired up the box.\u00a0 <\/p>\n All was now well.\u00a0 I could move VM’s with no issue.<\/p>\n BTW, if you will have a node offline in a cluster for some time then you need to be aware of your cluster quorum settings.\u00a0 Clusters with even numbers of nodes need a quorum and those with uneven numbers must not have a quorum.\u00a0 I keep a quorum disk in place just in case a node is going to be added\/removed from the cluster.\u00a0 In our scenario, we had N+2 fault tolerance so I could afford to safely remove this node and alter the quorum settings without losing fault tolerance.<\/p>\n","protected":false},"excerpt":{"rendered":" We had a hardware issue recently where we need to service the hardware of one of our Hyper-V cluster hosts.\u00a0 The HP engineer originally believed there was an issue with the server’s motherboard so this needed to be replaced.\u00a0 So it was.\u00a0 This didn’t fix the problem – it turned out to be something else … Continue reading “Hyper-V Hosts and Clusters – Changing Hardware”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[20],"tags":[],"class_list":["post-9320","post","type-post","status-publish","format-standard","hentry","category-hyper-v"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
The WS-Management service cannot process the request. Object not found on the myserver.domain.internal server.
(Unknown error (0x80338000)) <\/em><\/p>\n
Ensure that the agent is installed and running. If the error persists, reboot myserver.domain.internal and then try the operation again."<\/em><\/p>\n