From owner-freebsd-virtualization@FreeBSD.ORG Thu Sep 26 22:44:37 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6FD8E6A7 for ; Thu, 26 Sep 2013 22:44:37 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D5CE42FC3 for ; Thu, 26 Sep 2013 22:44:36 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id eo20so1541232lab.34 for ; Thu, 26 Sep 2013 15:44:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kBJSHStNa2d+poyXyKvddJBNhwR6vlCKZzg5whDebJY=; b=s7kbog9nueKZSMR+rSu0SAqiW0NuD4Rs6+H4JOgxA/hMd/0VYlpl911TBcxAqqT/OV ncgUrKjXOfCLoWRB5mmasUA/XVeflR7rQOPm/e4naaFoLo1lZgS1WW/IU1GzjLGA14wV gzgt8dpVdQWxbUjPLVwE5hzxK6EdULN/0qBjfgdrB2YquR8Tkuy1ZWhN1PCWHMG2QeYN FtVePfYFQFGt7FwVwkRLqB2dRyJTEX/oRW3WDNnpwYmf+yMpwVpVjD3fd7cNPO/pctwq 5ghAddE+UztMCD/p0raH7Veg2XU4agV9ZxJ2lvD+/maJoq3kqV/p3Z62DXJzcCZu/ERz vIHQ== MIME-Version: 1.0 X-Received: by 10.112.146.33 with SMTP id sz1mr5783653lbb.14.1380235474718; Thu, 26 Sep 2013 15:44:34 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.168.136 with HTTP; Thu, 26 Sep 2013 15:44:34 -0700 (PDT) In-Reply-To: <9779D76A3AD1B8097FFC552A@Mail-PC.tdx.co.uk> References: <9779D76A3AD1B8097FFC552A@Mail-PC.tdx.co.uk> Date: Thu, 26 Sep 2013 15:44:34 -0700 X-Google-Sender-Auth: hcXfYZwBCck3l8t0wl0uIjofSeQ Message-ID: Subject: Re: PXE booting into a Hyper-V 2012 R2 instance - slows to a crawl? From: Craig Rodrigues To: Karl Pielorz Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-virtualization@freebsd.org" 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: Thu, 26 Sep 2013 22:44:37 -0000 On Tue, Sep 24, 2013 at 6:53 AM, Karl Pielorz wrote: > > > 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). > PXE involves DHCP and TFTP. I would recommend that you do the following: (1) On the machine hosting your TFTP server, look at the TFTP logs and look for any clues. If your TFTP server is a FreeBSD box, look at /var/log/xferlog. I don't know what logs are available for a Windows TFTP server. (2) In between your booting machine, and your TFTP server, use Wireshark or tcpdump to capture the network traffic and analyze what is going on. (3) By default, the FreeBSD PXE loader uses a TFTP blocksize of 512 bytes per block (which is the original TFTP standard). You can increase the size of that to something bigger, depending on the MTU of your network. Usually 1400 bytes will work. In /boot/defaults/loader.conf, you can see this: #tftp.blksize="1428" # Set the RFC 2348 TFTP block size. # If the TFTP server does not support RFC 2348, # the block size is set to 512. If the value # is out of range ( < 8 || > 9008 ) an error is # returned. If you put in yout /boot/loader.conf file: tftp.blksize="1428" you can see if that speeds up the TFTP transfer during PXE booting. > > 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. > The spinner is the part where it is loading the kernel. For PXE, this is happening over TFTP. This looks like a slow network problem, so you need to analyze it a bit. I wrote some notes on PXE booting in FreeBSD which you might want to get some ideas from: http://www.freebsd.org/doc/handbook/network-pxe-nfs.html -- Craig