Hacker News Reader

Comment by rwmj | Hacker News Reader

And ironically the latest FreeBSD doesn't boot in QEMU if you're using AMD hardware, as of about a month ago. The bug has been open since 2016: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213333

View on HN

So filing a QEMU bug on FreeBSD's tracker is supposed to help how?

While we can argue about precisely where the blame lies, I'm leaning towards a FreeBSD bug here since it cannot handle the topology that QEMU supplies (yet Windows, Linux, older FreeBSD can). In any case maybe the FreeBSD community could interact with the QEMU community, since virtualization is probably the way most new FreeBSD users come on board.

I couldn't find this issue on the QEMU bug tracker.

https://bugs.launchpad.net/qemu/

Since you encountered it and I don't yet have AMD hardware to test, would you mind reporting it?

No, because (as discussed above):

(1) I do not think it's a QEMU bug. Windows, Linux and older versions of FreeBSD work fine.

(2) I'm one of those people who thought, let's try to compile some software on FreeBSD .. meh can't get it to work.

It's really for FreeBSD to fix this, if they want to on-board new users (and maybe they don't, that's totally fine too).

I use an older version of QEMU with the latest version of FreeBSD and it works fine.

> as of about a month ago

> open since 2016

Which is it?

2016 as you could easily see if you'd opened the link.

Reply on news.ycombinator.com