search

pgj / freebsd-bhyve-plus-port

Unofficial extensions to BHyVe
8 stars 2 forks source link

Build error on 13.0-STABLE #1

Open thesunexpress opened 2 years ago

thesunexpress commented 2 years ago

Hi, Having an issue building, which I suspect is the #1 reason wifibox hard-locks and crashes on 13.0-STABLE.

cd /usr/ports/sysutils/bhyve+ && make leads to: ===> Building for bhyve+-0.1.0 make[1]: "/usr/ports/sysutils/bhyve+/work/share/mk/src.libnames.mk" line 733: /usr/ports/sysutils/bhyve+/work/lib9p-7ef466772108856ee3e093735033232a6f1a3f04: Missing or incorrect _DP_9p entry in src.libnames.mk. Should match LIBADD for 9p ('sbuf casper cap_pwd cap_grp' vs 'sbuf')

make[1]: stopped in /usr/ports/sysutils/bhyve+/work/lib9p-7ef466772108856ee3e093735033232a6f1a3f04 *** Error code 1

Stop. make: stopped in /usr/ports/sysutils/bhyve+

Not quite sure where to go from here, much of bhyve's internals are way above my head...

pgj commented 2 years ago

How could wifibox crash if you cannot build bhyve+?

The build is not really supported on the STABLE branches as it is being a moving target and it is hard to identify which version of the base system sources available. I am planning to somehow "pin" the version of the contents of /usr/src to compile against so updating it will not break things so easily. (The same strategy should apply for CURRENT.)

thesunexpress commented 2 years ago

I suspect the resultant vmm.ko would be compatible/incompatible somehow; of course it is missing because BHyve+ doesn't build successfully. The behavior started when I built a custom kernel for an otherwise vanilla 13.0-STABLE with a GENERIC kernel. Suddenly wifibox broke things there...which took me by surprise given that with the GENERIC kernel (fresh new install), 13.0-STABLE + wifibox ran perfectly. Thus on 13.0-STABLE: make -j(n) buildkernel && make -j(n) installkernel && reboot == ur box iz b0rked. I've spent a few days digging through core dumps to try and pinpoint where things go wrong, without much result. The kernel dumps & the system reboots so quickly that not much useful info is logged. What has me funfused is that none of this crashing behavior exists on a clean install of 13.0-STABLE simply using pkg install wifibox but as soon as a new kernel is built, even a GENERIC kernel, from slightly newer 13.0-STABLE sources, all hell breaks loose. Reinstalling wifibox from pkgs, while running a custom 13.0-STABLE kernel doesn't work either. The same crash-semi-dump-bits-insta-reboot-loop sequence occurs. Moving the 2 different (custom) built vmm.ko modules around doesn't fix things either. The vmm.ko modules in /boot/kernel/ & /boot/modules/ are different no doubt, explicitly loading one or the other makes no difference.

For what it is worth, the exact same thing happens with 14-CURRENT.

For what it is worth part deux, 13.0-RELEASE is happy with whatever I throw at it, BHyve+ builds cleanly, running wifibox with a custom kernel(s) runs perfectly etc. all with the latest greatest src & ports.

Currently I do not need to run (n)-STABLE for iGPU support or anything else, so I can live with (n)-RELEASE... it might be helpful to make note of this in the manpages, so that other pilgrims don't run into the same wall.

pgj commented 2 years ago

Thanks for the detailed explanation. Yeah, vmm.ko is quite fragile. I will look into the issue.