Date: Wed, 18 Sep 2013 14:50:07 +0000 From: "Abhishek Gupta (LIS)" <abgupta@microsoft.com> To: Karl Pielorz <kpielorz_lst@tdx.co.uk>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues? Message-ID: <9cabc6fbba754dd3aa357943ef82db22@BL2PR03MB210.namprd03.prod.outlook.com> In-Reply-To: <4787C47D82401721B4C53B49@Mail-PC.tdx.co.uk> References: <18D121A056145C32F0501114@Mail-PC.tdx.co.uk> <155969fa70a34e41a84649bf3cb81c21@BL2PR03MB210.namprd03.prod.outlook.com>, <4787C47D82401721B4C53B49@Mail-PC.tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks again Karl! Yes, it should work. My understanding is that the failov= er should be agnostic to the guest OS but there could be some integration c= omponent that we might have missed. So it would be good to get to the botto= m of this.=0A= =0A= Regards,=0A= =0A= Abhishek=0A= ________________________________________=0A= From: Karl Pielorz <kpielorz_lst@tdx.co.uk>=0A= Sent: Wednesday, September 18, 2013 7:45 AM=0A= To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org=0A= Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issue= s?=0A= =0A= --On 18 September 2013 14:23 +0000 "Abhishek Gupta (LIS)"=0A= <abgupta@microsoft.com> wrote:=0A= =0A= > Hi Karl,=0A= >=0A= > Thanks for reporting the issue. Please give us some time to investigate= =0A= > and get back to you on this. In the meantime I wanted to ask if setting= =0A= > up a Hyper-V replica for the FreeBSD VM and then a manual failover=0A= > reproduces the same symptoms? Please let me know.=0A= =0A= Hi,=0A= =0A= Manual fail-over appears to work OK - in order, I tested:=0A= =0A= - Live migration from one node to the other, and back again (worked)=0A= =0A= - Stopping the cluster service on one of the nodes (i.e. from Failover=0A= Cluster Manager) - this showed the VM moving from the node that was=0A= stopped, over to the other node (again worked).=0A= =0A= - Pulling the power on the active node hosting both VM's (i.e. Windows=0A= guest, and FreeBSD guest) - this showed the remaining node trying to bring= =0A= up the VM's (of which Windows came up OK, and FreeBSD got corrupted).=0A= =0A= =0A= I've had to stop now as the guy here looking after the Synology kit on the= =0A= test network is applying a firmware update (this is apparently for some=0A= appletalk issue or something).=0A= =0A= I'll re-run the test after this has been done - if it still fails, I'll=0A= come back with a 'how to reproduce' type report (and I'll obviously let you= =0A= know if we can't reproduce it again!).=0A= =0A= At least I know it 'should' work now :)=0A= =0A= Thanks,=0A= =0A= -Karl=0A= =0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9cabc6fbba754dd3aa357943ef82db22>