On 19 Oct, Matthew D. Fuller wrote:
> On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of
> Don Lewis, and lo! it spake thus:
>>
>> The first is that when I attempt to start a Virtualbox VM, the
>> system panics.
>
> Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460
Thank
On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of
Don Lewis, and lo! it spake thus:
>
> The first is that when I attempt to start a Virtualbox VM, the
> system panics.
Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460
--
Matthew Fuller (MF4839) | fulle...@over-
On 19 Oct, Don Lewis wrote:
> On 20 Oct, Graham Perrin wrote:
>> On 19/10/2018 23:47, Don Lewis wrote:
>>
>>> … when I attempt to start a Virtualbox VM, the system panics. … (guest)
>>> Windows 7 with
>> networking configured as > NAT and the underlying adapter being Intel
>> PRO/1000
>> MT Desk
On 20 Oct, Graham Perrin wrote:
> On 19/10/2018 23:47, Don Lewis wrote:
>
>> … when I attempt to start a Virtualbox VM, the system panics. … (guest)
>> Windows 7 with
> networking configured as > NAT and the underlying adapter being Intel PRO/1000
> MT Desktop (82540EM). …
>
> No panic here. 32-
On 19/10/2018 23:47, Don Lewis wrote:
> … when I attempt to start a Virtualbox VM, the system panics. … (guest)
> Windows 7 with
networking configured as > NAT and the underlying adapter being Intel PRO/1000
MT Desktop (82540EM). …
No panic here. 32-bit Windows 7 guest with the same virtual adap
It looks like there are a couple of problems here. The first is that
when I attempt to start a Virtualbox VM, the system panics. The DDB
backtrace seems to indicate that the panic is occuring inside the
ng_ether module, which was being called due to a virtualbox doing an
ioctl call. The VM guest
