[Bug 192281] [kern] nmdm with bhyve causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 Peter Grehan gre...@freebsd.org changed: What|Removed |Added Status|Open|Issue Resolved Resolution|--- |FIXED --- Comment #10 from Peter Grehan gre...@freebsd.org --- Fixed in CURRENT and in 10-stable. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192281] [kern] nmdm with bhyve causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 --- Comment #7 from Craig Rodrigues rodr...@freebsd.org --- +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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192281] [kern] nmdm with bhyve causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 --- Comment #6 from Peter Grehan gre...@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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192281] [kern] nmdm with bhyve causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 --- Comment #5 from Dave Smith dsm...@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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192281] [kern] nmdm with bhyve causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 Craig Rodrigues rodr...@freebsd.org changed: What|Removed |Added CC||rodr...@freebsd.org Assignee|freebsd-b...@freebsd.org|freebsd-virtualization@Free ||BSD.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
