From owner-freebsd-virtualization@FreeBSD.ORG Fri Mar 15 21:27:33 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 E12C06CE for ; Fri, 15 Mar 2013 21:27:33 +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 9AA966D1 for ; Fri, 15 Mar 2013 21:27:33 +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 4E4C211DDC; Sat, 16 Mar 2013 07:27:31 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro.local (mobile-166-137-212-024.mycingular.net [166.137.212.24]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BKS24327 (AUTH peterg@ptree32.com.au); Sat, 16 Mar 2013 07:27:26 +1000 Message-ID: <51439239.1030404@freebsd.org> Date: Fri, 15 Mar 2013 14:27:21 -0700 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: Alfred Perlstein Subject: Re: bhyve in -current 4/14/13 can no longer support FreeBSD stable install References: <514350E9.4020100@mu.org> In-Reply-To: <514350E9.4020100@mu.org> 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.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: Fri, 15 Mar 2013 21:27:33 -0000 Hi Alfred, > What will happen is during the extract process the install will hang. No > network IO happens and on the host I see bhyve's CPU hit 100% for each > core assigned. > > For reference this is the bhyve command invoked via Neel's "vmrun.sh". > > 0 3915 3908 0 103 0 2122208 103428 - R+ 2 1048:45.75 /usr/sbin/bhyve -c > 2 -m 2048 -M 0 -AI -H -P -g 0 -s 0:0,hostbridge -s 1:0,virtio-net,tap0 > -s 2:0,virtio-blk,../freebsd-stable.img -s > 3:0,virtio-blk,../FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso > -S 31,uart,stdio freebsd-stable > > I tried to gdb the bhyve process but that was bad news. Is there a set > of steps usually taken to help pinpoint what is going on when we this > state? Does the previous snapshot (r247640) work better ? The relevant change there was the recent virtio guest MFC. Some things to try: - boot bhyve uniprocessor - is the bhyve process performing any disk i/o, or is it just spinning ? the bhyvectl program can dump a lot of vm state - you can try something like sudo bhyvectl --get-all --cpu=0 --vm= sudo bhyvectl --get-all --cpu=1 --vm= If you do this repeatedly, it may be possible to see some patterns e.g. counters incrementing, %RIP values being the same etc. Regarding gdb and bhyve, for debugging I usually start bhyve under gdb in the foreground and send output to another pty with the gdb "set tty" command (note the other pty should have a 'sleep 100000' command run to avoid input being captured) - this way, a ctl-C in the gdb session will drop into gdb and allow breakpoints to be set etc. later, Peter.