Date: Fri, 23 Apr 2021 10:41:36 +0200 From: Peter Blok <pblok@bsd4all.org> To: Chris <bsd-lists@BSDforge.com> Cc: Ian Lepore <ian@freebsd.org>, Daniel Dettlaff <dmilith@me.com>, freebsd-hackers@freebsd.org Subject: Re: 32-bit jail on 64-bit host Message-ID: <5735CD11-0688-4C25-AE32-2D29ECA4ABD8@bsd4all.org> In-Reply-To: <a17b95538c873a8a27ff32985490c677@bsdforge.com> References: <F9E8A7E3-C041-49C6-93E3-F44CB83A0858@bsd4all.org> <06CAF4FA-CBC1-4F89-9CA9-532A6B370E51@me.com> <c56c59249fa4b8d2c6b0e3595d410270a9d0c383.camel@freebsd.org> <FC6126FF-99F0-46C1-8D0B-24676E5E155F@bsd4all.org> <a17b95538c873a8a27ff32985490c677@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris, that was the right hint. I copied host /rescue/route to the jail in /amd64. Changed the = dhclient-script to use /amd64/route and it worked. Using dynamic linked version failed with /libexec/ld-elf.so.1. Peter > On 22 Apr 2021, at 21:27, Chris <bsd-lists@BSDforge.com> wrote: >=20 > On 2021-04-22 11:13, Peter Blok wrote: >> I tried to replace some of the 32-bit binaries before, but it started = to require >> shared libs as well, so I stopped. I=E2=80=99ll give it a shot later. > I'm not sure which binaries you might need either. But could /rescue = bring you > any closer? >=20 > --Chris >> I now run it with out vnet and it indeed works. I have managed to = compile >> p5-DBD-Oracle which works now. >> Because all of my other jails were vnet jails, I didn=E2=80=99t think = about doing it the >> old way without vnet. >> Peter >>> On 22 Apr 2021, at 15:39, Ian Lepore <ian@freebsd.org> wrote: >>> On Thu, 2021-04-22 at 12:32 +0200, Daniel Dettlaff via = freebsd-hackers >>> wrote: >>>> If you need to run 32bit software with 64bit base system just try >>>> creating 64bit jail with lib32 subsystem present. Then 32bit = software >>>> should be able to run properly in such jail, but you can't run = 32bit >>>> jail on 64bit base as Eugene said. >>> That is not what Eugene said, and you CAN run a 32-bit jail on a = 64-bit >>> host; I do so on this machine. As Eugene said, you simply need to = copy >>> a few selected 64-bit binaries into the jail, replacing the 32-bit >>> version of those programs. That is, install the jail from a 32-bit >>> build or packages, and then just copy the necessary few binaries = from >>> your host root filesystem into the jail. >>> It would be nice if there was a list somewhere of which binaries = need >>> to be replaced. I just did it by trial and error... when I ran into >>> things that didn't work, I tried using a 64-bit copy of that program >>> and if it worked: problem solved. >>> -- Ian >>>>> On 22 Apr 2021, at 10:36, Peter Blok <pblok@bsd4all.org> wrote: >>>>> Hi, >>>>> I have created a 32-bit jail on a 64-bit running 12-STABLE. The >>>>> jail is also build using the same source. >>>>> The jail gives me a 32-bit environment. I=E2=80=99m getting an IP = address >>>>> and I can ping others on the same network segment. >>>>> But I can=E2=80=99t set a default route. >>>>> route add default 192.168.1.1 >>>>> route: writing to routing socket: Invalid argument >>>>> add net default: gateway 192.168.1.1 fib 0: Invalid argument >>>>> # netstat -rn >>>>> Routing tables >>>>> (0) (0) UH >>>>> (0) (0) U >>>>> (0) (0) UHS >>>>> (0) (0) UH >>>>> (0) (0) U >>>>> (0) (0) UHS >>>>> # ifconfig -a >>>>> lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu = 16384 >>>>> options=3D680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> >>>>> inet6 ::1 prefixlen 128 >>>>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >>>>> inet 127.0.0.1 netmask 0xff000000 >>>>> groups: lo >>>>> nd6 options=3D21<PERFORMNUD,AUTO_LINKLOCAL> >>>>> e0b_websip: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> >>>>> metric 0 mtu 1500 >>>>> options=3D8<VLAN_MTU> >>>>> ether 0e:88:d7:20:99:80 >>>>> hwaddr 02:80:ad:6e:79:0b >>>>> inet 192.168.1.205 netmask 0xffffff00 broadcast 192.168.1.255 >>>>> groups: epair >>>>> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) >>>>> status: active >>>>> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> >>>>> Any idea how to fix this? >>>>> I=E2=80=99m using vnet bridge >>>>> Peter >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-hackers@freebsd.org <mailto:freebsd-hackers@freebsd.org> = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>; > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = <mailto:freebsd-hackers-unsubscribe@freebsd.org>"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5735CD11-0688-4C25-AE32-2D29ECA4ABD8>