On Tue, 2021-02-02 at 18:18 +0530, Vinay Kumar wrote: > Hi, > > Could not run oe-selftest for gcc using qemu image using below command, > $oe-selftest -r gcc.GccCrossSelfTestSystemEmulated.test_cross_gcc > > getting qemu boot errors as follows, > ERROR: Qemu pid didn't appear in 120 seconds (02/01/21 19:23:28) > ERROR: Status information, poll status: None, pidfile exists: False, > pidfile contents None, proc pid exists False > > The boot uses the tap0 interface. And also observed that the pid file > is not generating when the qemu boot command is triggered. > > The launchcmd for qemu boot is, > runqemu snapshot nographic qemuarm > /extra/build-master-2/tmp/deploy/images/qemuarm/core-image-minimal-qemuarm.ext4 > tcpserial=51301:51487 bootparams="console=tty1 console=ttyS0,115200n8 > printk.time=1" qemuparams="-pidfile pidfile_8153" > > Also attached GccCrossSelfTestSystemEmulated.log > (build-dir/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/testimage/qemurunner_log) > for reference. > > Additional info : > The oe-selftest execution is tried using latest poky-master.
Looking at the logs, I think its sitting trying to execute: sudo /home/vinay/reference-poky/poky-master/scripts/runqemu-ifup 1000 1000 /extra/build-master-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin to setup the networking device, perhaps waiting on a password. You could try running runqemu-gen-tapdevs instead to setup those devices in advance, or give it permission to run that command without a password. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#147581): https://lists.openembedded.org/g/openembedded-core/message/147581 Mute This Topic: https://lists.openembedded.org/mt/80313425/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
