| acook | |
| Dec 26 2020, 8:36 PM |
| F6890044: Screenshot from 2020-12-31 09:41:00.png | |
| Dec 31 2020, 2:41 PM |
I was trying to use Qemu to play around with RedoxOS and QEMU wouldn't boot due to two missing files: vgabios-stdvga.bin and kvmvapic.bin.
The issue ended up being that QEMU was looking for its bios files in the wrong spot.
Here it how I was able to fix it:
mkdir /usr/share/seavgabios ln -s /usr/share/qemu/vgabios-stdvga.bin /usr/share/seavgabios/vgabios-stdvga.bin
You may note that I made no change to the kvmvapic.bin file, but once I created the above link, both errors disappeared.
I've dug around in both the package.yml and QEMU 5.0.1's source code and I don't see where that distinctive seavgabios path is being hard coded or set in a variable.
That string doesn't appear in the extracted package either as far as I can tell either.
So it has to be dynamically generating the string from the sea, vga, and bios components in the source code?
Am I just losing my mind?
Not sure how you are trying to run it, but I borrowed this from here
qemu-system-x86_64 -serial mon:stdio -d cpu_reset -d guest_errors -smp 4 -m 1024 -s -machine q35 -device ich9-intel-hda -device hda-duplex -net nic,model=e1000 -net user -device nec-usb-xhci,id=xhci -device usb-tablet,bus=xhci.0 -enable-kvm -cpu host -drive file=harddrive.bin,format=raw
And was able to boot without issue.
Yeah that's the same place I pulled the command from. Sorry about not including it originally, it would have helped.
I'm starting to think this install has ghosts.
On the off chance anyone else encounters the same problem with QEMU, hopefully this will help them at least.
Might we worth running an sudo eopkg check and seeing if you have any Broken packages that aren't helping?
Everything from eokpkg check is ok.
I removed my workaround to test and now I can't replicate it. I checked eopkg history and I don't see any qemu updates. I did install virt-manager in the meantime though, which does have some passing mentions of seabios, but I honestly am at a loss.
If I can track down any more info I'll let you know, but as it stands it looks like the problem vanished just as mysteriously as it appeared.