QEMU - No 'PCI' bus found for device 'virtio-rng-pci'

Ambrozewicz, Adrian adrian.ambrozewicz at linux.intel.com
Tue Nov 17 01:41:02 AEDT 2020


Hello,

In recent poky bump we've inherited introduction of new option related 
to RNG forwarding in poky/scripts/runqemu script.

This unfortunately makes my AST2500 target unable to start with 
following error:
qemu-system-arm: -device virtio-rng-pci,rng=rng0: No 'PCI' bus found for 
device 'virtio-rng-pci'

The naive workaround is to revert this change like so:
diff --git a/poky/scripts/runqemu b/poky/scripts/runqemu
index e5e66f345..e62d869c2 100755
--- a/poky/scripts/runqemu
+++ b/poky/scripts/runqemu
@@ -1336,7 +1336,7 @@ class BaseConfig(object):
          if not os.access(qemu_bin, os.X_OK):
              raise OEPathError("No QEMU binary '%s' could be found" % 
qemu_bin)

-        self.qemu_opt = "%s %s %s %s %s" % (qemu_bin, 
self.get('NETWORK_CMD'), self.get('QB_RNG'), self.get('ROOTFS_OPTIONS'), 
self.get('QB_OPT_APPEND'))
+        self.qemu_opt = "%s %s %s %s" % (qemu_bin, 
self.get('NETWORK_CMD'), self.get('ROOTFS_OPTIONS'), 
self.get('QB_OPT_APPEND'))

          for ovmf in self.ovmf_bios:
              format = ovmf.rsplit('.', 1)[-1]

According to 
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg141309.html 
there is also a 'proper' way to disable that option by machine/config 
files. However, I am curious if there is a proper fix to enable that 
option on my target? Every optimization is always welcome.

Regards,
Adrian


More information about the openbmc mailing list