Re: #yocto #dunfell #qemux86-64 #yocto #dunfell #qemux86-64

Khem Raj

On 8/31/22 4:36 AM, Monsees, Steven C (US) via wrote:
Thank you for the quick replay...
The no graphic option does work but the kernel comes up with errors...
Will full wayland support be added to the dunfell release ?
you can use vnc backend which is enabled by default. by using
runqemu publicvnc

I wish runqemu was smart enough to prioritize, interactive UI e.g. sdl/gtk if not available then fall back to vnc, and then use nographic
in order.

and please look at kirkstone if you are evaluating next LTS, dunfell is still supported but is already inching towards its end comparatively you get more modern package versions with kirkstone.

-----Original Message-----
From: yocto@... <yocto@...> On Behalf Of Alexander Kanavin
Sent: Wednesday, August 31, 2022 7:23 AM
To: Monsees, Steven C (US) <steven.monsees@...>
Cc: yocto@...
Subject: Re: [yocto] #yocto #dunfell #qemux86-64
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
You need to run this in a X11 session, or use 'nographic' parameter.
On Wed, 31 Aug 2022 at 13:17, Monsees, Steven C (US) via <> wrote:


I am attempting to evaluate dunfell -23.0.17, on a cetos7 linux box.

When building the default : core-image-minimal or core-image-sato,
clean with no errors/warnings, on execution

I get the following error for both (see below)…

(1) Is this an issue with the release ?, and is there another release I should be using ?

(2) Is there something I need to pre-configure for these builds to run properly ?

(3) How might I resolve this issue ?

06:57 smonsees@yix490016
ll_Min>runqemu qemux86-64

runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e ...

runqemu - INFO - Continuing with the following parameters:


MACHINE: [qemux86-64]

FSTYPE: [ext4]



runqemu - INFO - Setting up tap interface under sudo

[sudo] password for smonsees:

runqemu - INFO - Network configuration:

runqemu - INFO - Running /disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dunfell_Min/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -drive file=/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dunfell_Min/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20220830151817.rootfs.ext4,if=virtio,format=raw -show-cursor -usb -device usb-tablet -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -cpu core2duo -m 256 -serial mon:vc -serial null -kernel /disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dunfell_Min/tmp/deploy/images/qemux86-64/bzImage--5.4.192+gitAUTOINC+3fecb08507_85f0668fea-r0-qemux86-64-20220830151817.bin -append 'root=/dev/vda rw mem=256M ip= oprofile.timer=1 '

runqemu - ERROR - Failed to run qemu: Could not initialize SDL(x11 not
available) - exiting

runqemu - INFO - Cleaning up

Set 'tap0' nonpersistent

Thank you for your help,


Join to automatically receive all group messages.