https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
Peter Grehan changed:
What|Removed |Added
Status|Open|Issue Resolved
Resolution|-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:
Author: grehan
Date: Thu Sep 18 19:20:09 UTC 2014
New revision: 271800
URL: http://svnweb.freebsd.org/changeset/base/271800
Log:
MFC nmdm driver changes, r2595
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:
Author: grehan
Date: Wed Sep 10 05:44:16 UTC 2014
New revision: 271350
URL: http://svnweb.freebsd.org/changeset/base/271350
Log:
Fix issue with nmdm and leadin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #7 from Craig Rodrigues ---
+1
Being able to put the VM name in the nmdm device name is super useful.
--
You are receiving this mail because:
You are the assignee for the bug.
___
fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #6 from Peter Grehan ---
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 c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #5 from Dave Smith ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
Peter Grehan changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment #4 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
Craig Rodrigues changed:
What|Removed |Added
CC||rodr...@freebsd.org
As
