Date: Thu, 07 Sep 2023 14:33:17 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 273557] Regression preventing bhyve from running inside a jail without IP after f74147e26999838e03a522bf59ea33bef470d356) breaks support for jailing bhyve with IPv4 and IPv6 disabled. Patch included. Message-ID: <bug-273557-27103-R1Sza1PVvN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273557-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-273557-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273557 --- Comment #3 from Bjoern A. Zeeb <bz@FreeBSD.org> --- The patch seems to work more by accident because the kernel side adds an IF= F_UP and IFF_UP is in the TUN_VMIO_FLAG_MASK set: {{{ case VMIO_SIOCSIFFLAGS: /* VMware/VMnet SIOCSIFFLAGS */ iflags =3D *(int *)data; iflags &=3D TUN_VMIO_FLAG_MASK; iflags &=3D ~IFF_CANTCHANGE; iflags |=3D IFF_UP; }}} What's the actual error you get? "Could open socket"? I think the real solution is to make the code "advisory" and not to error o= ut in case it cannot UP the interface in that case? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273557-27103-R1Sza1PVvN>