From owner-freebsd-virtualization@FreeBSD.ORG  Thu Sep  4 06:03:06 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 4A51D773
 for <freebsd-virtualization@FreeBSD.org>; Thu,  4 Sep 2014 06:03:06 +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 31454107E
 for <freebsd-virtualization@FreeBSD.org>; Thu,  4 Sep 2014 06:03:06 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s84636tf033158
 for <freebsd-virtualization@FreeBSD.org>; Thu, 4 Sep 2014 06:03:06 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: Thu, 04 Sep 2014 06:03:06 +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: grehan@FreeBSD.org
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-UDzZeIPois@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: Thu, 04 Sep 2014 06:03:06 -0000

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

--- Comment #6 from Peter Grehan <grehan@FreeBSD.org> ---
Thanks - yes, easy repro on 10. Doesn't crash on CURRENT, but the bug is
still there in that the leading zeros are stripped when the devfs entry
is created. This in turn means that it isn't possible to connect to the
'B' end using the same text string.

After a chat with Neel, the proposed solution will be to allow any valid
devfs character string between the 'nmdm' and trailing 'A' or 'B'. That way
you can even encode the VM name in the nmdm device name :)

I'll see if I can get this into CURRENT shortly, and then MFC in time for
10.1.

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