From owner-freebsd-virtualization@FreeBSD.ORG Wed Apr 24 18:08:00 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A5689C37 for ; Wed, 24 Apr 2013 18:08:00 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 62A0C13C3 for ; Wed, 24 Apr 2013 18:08:00 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 2E089121DE; Thu, 25 Apr 2013 04:07:58 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro.local (c-67-190-11-104.hsd1.co.comcast.net [67.190.11.104]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BLR36910 (AUTH peterg@ptree32.com.au); Thu, 25 Apr 2013 04:07:56 +1000 Message-ID: <51781F73.1070605@freebsd.org> Date: Wed, 24 Apr 2013 12:07:47 -0600 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Importing the Microsoft hyper-v PV drivers into CURRENT References: <5176C98B.4050607@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Info: RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,SPF_SOFTFAIL X-Junkmail-Status: score=24/51, host=dommail.onthenet.com.au Cc: "Abhishek Gupta \(LIS\)" 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, 24 Apr 2013 18:08:00 -0000 Hi all, I'd like to start the process of bringing in Microsoft's hyper-v paravirtualized drivers into CURRENT. Here're the steps I'll follow: 1. Pull the hyperv driver-only git export (https://github.com/FreeBSDonHyper-V/VendorBranchForFreeBSDonHyper-V) into a vendor branch 2. A project branch off CURRENT will be created, and the vendor branch pulled into that. Folk can use that for testing/review until it's considered OK. 3. Lastly, when it's deemed ready, I'll drop the vendor branch into CURRENT and retire the project branch. Let me know if that sounds OK. later, Peter.