I couldn't get bochs to run, and it turns out the VGABIOS files aren't included. I see that the other bios files are in bochs-bios, which is Required and was pulled in, etc. I'm working on a build to fix this (provenpackager), but I'm logging this for tracking purposes. Also, any reason we're not on 2.4.2, even in rawhide?
On second look, would this be better placed in bochs-bios? It looks like the bochs spec deliberately removes the VGABIOS.
Oh, or not, it looks like bochs-bios is a dead.package. Ignore that.
Jon, I've not touched bochs in ages, so you're free to do with it what you want from my POV, but bochs now also is used to build the BIOS files for qemu! So please coordinate with Glauber Costa <glommer> before making any changes. Also note that I see a Requires: vgabios inside the spec file, so the vga bios seems to be in a separate package now, so this might just be a configuration problem.
Ah, I see. It appears that way. Maybe bochs should include symlinks from /usr/share/bochs/<each VGABIOS file name> to /usr/share/vgabios/<each VGABIOS file name>. I'll try that.
Works beautifully, I'll push an update for just that, no other changes. I'll experiment with 2.4.2 on my own, and loop in Glauber later. Thanks!
Please note, the only reason I still keep bochs around, is because of the bios, needed for QEMU. For F-13, Qemu is switching to SeaBIOS, which will probably draw bochs unmaintained. So if you have any interest in bochs itself, it would be good if you find someone interested on it enough to maintain the package (like yourself). Otherwise, it will just end up orphaned.
I'll apply for co-maintainer, so in that event, it'll fall to me.
Also, is there any reason we can't --enable-cpu-level=6?
(In reply to comment #7) > I'll apply for co-maintainer, so in that event, it'll fall to me. If you need some help, I can also volunteer to co-maintain bochs with you. I use it from time to time. (In reply to comment #8) > Also, is there any reason we can't --enable-cpu-level=6? Yes, I also think this is a good idea. Otherwise you can't run any modern OS at all. Chris Lalancette
bochs-2.3.8-0.9.git04387139e3b.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/bochs-2.3.8-0.9.git04387139e3b.fc12
bochs-2.3.8-0.9.git04387139e3b.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/bochs-2.3.8-0.9.git04387139e3b.fc11
This build works for me, I'll start tinkering with 2.4.2.
I have a working 2.4.2 build, with no bios changes. Shall I put it in rawhide?
bochs-2.3.8-0.9.git04387139e3b.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bochs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12949
bochs-2.3.8-0.9.git04387139e3b.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bochs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-12985
FYI, the bios tarball generation no longer works as advertised, the git clone step fails.
Ah, it's now kvm.git, not qemu-kvm.git. Unsurprising.
. . .which doesn't have the bios files. They are in the bochs 2.4.2 tarball, however, and seem to work fine for bochs. Can't test kvm, though as it's broken for me anyway. . .https://bugzilla.redhat.com/show_bug.cgi?id=544339 Anyone able to test prior to me putting 2.4.2 in rawhide?
bochs-2.3.8-0.9.git04387139e3b.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
bochs-2.3.8-0.9.git04387139e3b.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.