You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After messing around with qemu source and enabling qemu tracing, I am convinced that the problem > here is the openbios when it enumerates the PCI devices, it does find the VIRTIO_RNG device in it's
tables.
Currently, the openbios code is not rebuilt, we purely use the upstream binary from the qemu tarball. > An entry would be needed in the pci_database.c code in the rom/openbios code for the Virtio_rng.
I did verify via the tracing, that while the openbios does not know how to handle the virtio-rng PCI > entry, the kernel correctly identifies it and I see correct tracing output when the device is accessed.
I would suggest you report it upstream and then close this bug as reported upstream.
The text was updated successfully, but these errors were encountered:
Looking at this issue, I agree that the analysis from yocto is correct.
The message itself is just a warning that the device can't be found in OpenBIOS's PCI database but it will still generate the device with appropriate vendor/device properties which is enough for OSs to still detect and use the device.
If you can find out what the name in the device tree should be then I can easily add it to the PCI database. Given that the device isn't preset on any Sun hardware then I'm happy to accept the name as used in the FDT representation to keep things consistent.
There is an annoying error message when run qemuppc with option "-device virtio-rng-pci":
We found this in yocto project and the detail logs:
It was reported in Yocto but is suggested to be reported in openbios:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12209
Comments from yocto:
The text was updated successfully, but these errors were encountered: