Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Sep 2013 14:23:26 +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:  <155969fa70a34e41a84649bf3cb81c21@BL2PR03MB210.namprd03.prod.outlook.com>
In-Reply-To: <18D121A056145C32F0501114@Mail-PC.tdx.co.uk>
References:  <18D121A056145C32F0501114@Mail-PC.tdx.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Karl,=0A=
=0A=
Thanks for reporting the issue. Please give us some time to investigate and=
 get back to you on this. In the meantime I wanted to ask if setting up a H=
yper-V replica for the FreeBSD VM and then a manual failover reproduces the=
 same symptoms? Please let me know.=0A=
=0A=
Thanks,=0A=
Abhishek=0A=
________________________________________=0A=
From: owner-freebsd-virtualization@freebsd.org <owner-freebsd-virtualizatio=
n@freebsd.org> on behalf of Karl Pielorz <kpielorz_lst@tdx.co.uk>=0A=
Sent: Wednesday, September 18, 2013 5:42 AM=0A=
To: freebsd-virtualization@freebsd.org=0A=
Subject: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?=
=0A=
=0A=
Hi,=0A=
=0A=
As you've probably seen from my previous posts, we're looking at using=0A=
Hyper-V with FreeBSD.=0A=
=0A=
We built a test system (2 node cluster) - and had 2 HA hosts running on it=
=0A=
(a Windows 7 install, and a FreeBSD install from base/projects/hyperv=0A=
r255634).=0A=
=0A=
Live migration works for both hosts (i.e. to the other cluster node, and=0A=
back) - but a failure of the node [power pulled / non-graceful shutdown]=0A=
running the VM's - seems to trash the FreeBSD system.=0A=
=0A=
Hyper-V correctly see's the node fail, and restarts both VM's on the=0A=
remaining node. Windows 7 boots fine (says it wasn't shut down correctly -=
=0A=
which is correct) - but FreeBSD doesn't survive.=0A=
=0A=
At boot time we get a blank screen with "-" on it (i.e. the first part of=
=0A=
the boot 'spinner') - and nothing else.=0A=
=0A=
Booting to a network copy of FreeBSD and looking at the underlying virtual=
=0A=
disk - it appears to be trashed. You can mount it (but it understandably=0A=
warns it's not clean) - however, any access leads to an instant panic ('bad=
=0A=
dir ino 2 at offset 0: mangled entry').=0A=
=0A=
Trying to run fsck against the file system throws up an impressive amounts=
=0A=
of 'bad magic' errors and 'rebuild cylinder group?' prompts.=0A=
=0A=
Should the current FreeBSD Hyper-V drivers support this? (like I said, live=
=0A=
migration worked without an issue - and Windows recovered fine from the=0A=
failure).=0A=
=0A=
The Hyper-V is running under WS2012, with a Synology SAN - if you need any=
=0A=
more info, let me know,=0A=
=0A=
Thanks,=0A=
=0A=
-Karl=0A=
_______________________________________________=0A=
freebsd-virtualization@freebsd.org mailing list=0A=
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization=0A=
To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs=
d.org"=0A=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?155969fa70a34e41a84649bf3cb81c21>