From owner-freebsd-virtualization@FreeBSD.ORG Wed Dec 25 00:28:20 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 ESMTPS id 7BCBEE89 for ; Wed, 25 Dec 2013 00:28:20 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE041DE9 for ; Wed, 25 Dec 2013 00:28:20 +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 07B5512373; Wed, 25 Dec 2013 10:28:18 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-71-196-188-222.hsd1.co.comcast.net [71.196.188.222]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BQW76567 (AUTH peterg@ptree32.com.au); Wed, 25 Dec 2013 10:28:16 +1000 Message-ID: <52BA26A1.10204@freebsd.org> Date: Tue, 24 Dec 2013 17:28:17 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Dennis Glatting Subject: Re: nmdm doesn't create entries in /dev (10.0-RC2+) References: <1387926826.71651.129.camel@btw.pki2.com> In-Reply-To: <1387926826.71651.129.camel@btw.pki2.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 25 Dec 2013 00:28:20 -0000 Hi Dennis, > Bhyve newbie trying to get it to start. No problems. > I am getting the FreeBSD loader but it then exits when the loader goes > to boot. I've also found "kldload nmdm" does not create any entries > in /dev. Isn't it suppose to? I'm not sure what I am doing wrong. nmdm(4) is a cloneable device so device nodes won't show up until they're opened. Also, vmrun.sh is hard-coded to use stdio for output. You'll have to modify the script to get bhyveload (the -c option) and bhyve (the "-l com1," option) to use an nmdm device. > System: > > Elmer# uname -a > FreeBSD Elmer 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #0 r259838: Tue > Dec 24 15:21:17 MST 2013 > root@Elmer:/disk-2/obj/usr/src/sys/PENFORD-FreeBSD10-amd64 amd64 > > > I am executing the following instructions: > > kldload nmdm > kldload vmm > kldload if_tap > ifconfig tap0 create > ./vmrun.sh -c 4 -d /disk-2/VMs/nms.img -i > -I /disk-3/tmp/FreeBSD-10.0-RC2-amd64-disc1.iso -m 2G -t /dev/tap0 nms > > > FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > CPU: Intel(R) Xeon(R) CPU E5540 @ 2.53GHz (2533.47-MHz > K8-class CPU) This is a Nehalem Xeon - it doesn't have the VT-x feature known as "unrestricted guest" aka 16/32-bit emulation which arrived in Westmere. This won't allow FreeBSD to spin up APs (16-bit emulation required) or to run Linux via grub-bhyve (32-bit paging-disabled emulation). You'll be restricted to single CPU FreeBSD guests on this model :( later, Peter.