From owner-freebsd-virtualization@FreeBSD.ORG Tue Sep 24 13:53:44 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 068FC57A for ; Tue, 24 Sep 2013 13:53:44 +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 BC2402F42 for ; Tue, 24 Sep 2013 13:53:43 +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 r8ODrZqG093211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 24 Sep 2013 14:53:35 +0100 (BST) Date: Tue, 24 Sep 2013 14:53:35 +0100 From: Karl Pielorz To: freebsd-virtualization@freebsd.org Subject: PXE booting into a Hyper-V 2012 R2 instance - slows to a crawl? Message-ID: <9779D76A3AD1B8097FFC552A@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: Tue, 24 Sep 2013 13:53:44 -0000 Hi, We just updated our Windows Server 2012 test setup here to Windows Server 2012 R2 (i.e. using Hyper-V 2012 R2 now). We are creating new Hyper-V instances using our PXE boot environment (which boots you into a FreeBSD 9.1 amd64 O/S) - we'd build a Hyper-V aware kernel etc. from that (after SVN'ing the latest Hyper-V project source). Hyper-V would take seconds to boot this - but since changing over to R2 it takes a 'very, very long time'. The initial PXE bit happens quickly (i.e. seeing the server, and getting the BTX output out) but then it gets stuck with the \ spinner - it'll spin for a short time, stop, spin again for a short time, stop again. It *does complete* if you leave it - but it takes minutes (e.g. around 5-10 minutes!). This is with creating a 'Generation 1' Hyper-V instance - and replacing the 'Network Card' (which is added by default) with the 'Legacy Network Card'. Anyone noticed anything similar? -Karl