Date: Tue, 12 Sep 2023 11:06:00 +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-01f8w1SOK5@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 #9 from crest@rlwinm.de --- (In reply to Bjoern A. Zeeb from comment #7) I get the impression you don't use the VMIO_SIOCIFFLAGS ioctl if possible a= nd the existing code works if an IP socket can be created to invoke the SIOCGIFFLAGS ioctl on. Treating the inability to create a IP new socket as non-fatal would allow deploying bhyve in a jail, but it would still depend on the net.link.tap.up_on_open sysctl. I've looked for alternatives, but the VMIO_SIOCIFFLAGS ioctl is only API I've found that's useable from inside ja= il a without access to an IP stack. It would be possible to fall back to VMIO_SIOCIFFLAGS only if the IP socket creation fails and keep using an IP socket if possible. I would like bhyve to always use the ioctl directly on the tap device inste= ad of bringing the interface up indirectly by name through a socket ioctl sinc= e it covers all cases with a single code path, but any fix that allows an unpatc= hed bhyve to be started inside a jail with both IPv4 and IPv6 disabled would he= lp. How would you like to proceed? I'll be at EuroBSDcon later this week. Is th= ere anything I can do to help get a fix for this regression into FreeBSD 14.0 (= and errata into the older releases if release engineering agrees)? --=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-01f8w1SOK5>