From owner-freebsd-virtualization@FreeBSD.ORG  Mon Sep  1 03:36:19 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
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 049B6114
 for <freebsd-virtualization@FreeBSD.org>; Mon,  1 Sep 2014 03:36:19 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E02461192
 for <freebsd-virtualization@FreeBSD.org>; Mon,  1 Sep 2014 03:36:18 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s813aIEI039955
 for <freebsd-virtualization@FreeBSD.org>; Mon, 1 Sep 2014 03:36:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 192281] [kern] nmdm with bhyve causes kernel panic
Date: Mon, 01 Sep 2014 03:36:19 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: dsmith@johncompanies.com
X-Bugzilla-Status: Open
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192281-27103-r75lpL7ZeI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192281-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-192281-27103@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 03:36:19 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281

--- Comment #5 from Dave Smith <dsmith@johncompanies.com> ---

Hi Peter,

I had 3 VMs running with a slightly modified vmrc.   The vms had names like
col02325.

When I tried to start a 4th VM it happened to have a name like col00345.  I was
using the last 4 digits as the nmdm device number.  Apparently a leading zero
for the nmdm number caused a problem. The whole system crashed.  I changed the
vm name to col05345, and it worked.

To my way of thinking, nothing that can be entered on a command line should be
able to cause a kernel crash.

Let me know if you need more information.  I even have a couple of crash dumps.

Dave Smith

-- 
You are receiving this mail because:
You are the assignee for the bug.