https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286875

--- Comment #6 from Warner Losh <[email protected]> ---
So, the current branch based off Qemu 3.2 is getting rather old.
The 'blitz' branch is the latest code. It has all the changes and is rebased to
qemu as of sometime last week. It's likely what you want, but read on.

Though... blitz has a number of experimental things and when I tried it a while
ago, I had trouble making it work with more packages than what the -devel port
was based on so I've not updated that port. If that's changed, or if you can
test it (my local gear isn't beefy enough), then go ahead and update.

But blitz has some pull requests against it that need to be tended to that I've
not gotten around to since I've been busy trying to find the time to get it all
upstreamed into the qemu project. Recently, I discovered that I could get
claude to do 95% of the tedium associated with doing that, so I've restarted my
efforts there.  The b4/* branches (and bsd-user-claude) are related to that
effort: IGNORE THEM THEY DO NOT WORK (well, ok, what's there works, but it's
massively incomplete). Since I'm making changes to blitz to keep it in sync
with the changes the upstreaming is generating, you take your chances with
blitz. Maybe if we update it, we can get more people to help.

So, if you can test it, great!

Looking at the patch, what's qemu-qa-static? And amd64 and aarch64 are likely
the only host targets that work (it may build on ppc, but I'm not aware of any
testing there).  You should bump the version to 10.2.50 since that's the latest
version blitz is sync'd to (but that plus a bit). We should likely try to
converge on a 11.0 sync point. I've not re-tested blitz since I started the
changes for upstreaming more than on trivial stuff. qemu only supports 64-bit
hosts, so the conditional for the targets aren't needed (it's all 64-bit). And
I'd drop ppc-qemu-static because ppc (32-bit) isn't supported 15+ and I'm not
likely to fix bugs in it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to