Date: Sun, 26 Aug 2018 18:45:00 -0600 From: Nathan Friess <nathan.friess@gmail.com> To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>, Marko Zec <zec@fer.hr> Cc: freebsd-xen@freebsd.org Subject: Re: xen+vimage kernel panic Message-ID: <7b6200a7-aa93-e54e-8a0d-159a5cd5222b@gmail.com> In-Reply-To: <20180820094904.xdvsdowllpjcivlx@mac> References: <1f010180-30c3-3a28-a2ca-b9f6279aee9c@gmail.com> <20180819224852.40754d2a@x23> <20180820094904.xdvsdowllpjcivlx@mac>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-08-20 03:49 AM, Roger Pau Monné wrote: >>> Are there any thoughts on why the xn interface would cause a panic >>> there? >> >> The xn driver calls arp_ifinit() without setting the vnet context >> first. Perhaps the attached patch could help (not even compile >> tested...) > > I know nothing about VNET, so is this initialization required now that > VNET is enabled? Is this an existing bug in netfront that was harmless > before VNET was activated? > > Can you please file a bug report and attach the patch? Hi Roger and everyone, My apologies for not opening the bug report earlier this week. I tested the patch this weekend and it indeed does fix the panic in my domUs. Cheers, Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7b6200a7-aa93-e54e-8a0d-159a5cd5222b>