From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 18 12:42:42 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E2AF6CF5 for ; Wed, 18 Sep 2013 12:42:42 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id AC0BB272B for ; Wed, 18 Sep 2013 12:42:42 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r8ICgY3o060229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 18 Sep 2013 13:42:34 +0100 (BST) Date: Wed, 18 Sep 2013 13:42:35 +0100 From: Karl Pielorz To: freebsd-virtualization@freebsd.org Subject: Hyper-V 2012 Cluster / Failover - supported? - Any known issues? Message-ID: <18D121A056145C32F0501114@Mail-PC.tdx.co.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Sep 2013 12:42:42 -0000 Hi, As you've probably seen from my previous posts, we're looking at using Hyper-V with FreeBSD. We built a test system (2 node cluster) - and had 2 HA hosts running on it (a Windows 7 install, and a FreeBSD install from base/projects/hyperv r255634). Live migration works for both hosts (i.e. to the other cluster node, and back) - but a failure of the node [power pulled / non-graceful shutdown] running the VM's - seems to trash the FreeBSD system. Hyper-V correctly see's the node fail, and restarts both VM's on the remaining node. Windows 7 boots fine (says it wasn't shut down correctly - which is correct) - but FreeBSD doesn't survive. At boot time we get a blank screen with "-" on it (i.e. the first part of the boot 'spinner') - and nothing else. Booting to a network copy of FreeBSD and looking at the underlying virtual disk - it appears to be trashed. You can mount it (but it understandably warns it's not clean) - however, any access leads to an instant panic ('bad dir ino 2 at offset 0: mangled entry'). Trying to run fsck against the file system throws up an impressive amounts of 'bad magic' errors and 'rebuild cylinder group?' prompts. Should the current FreeBSD Hyper-V drivers support this? (like I said, live migration worked without an issue - and Windows recovered fine from the failure). The Hyper-V is running under WS2012, with a Synology SAN - if you need any more info, let me know, Thanks, -Karl