All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: Khem Raj <raj.khem@gmail.com>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: RE: [yocto] #yocto #dunfell #qemux86-64
Date: Wed, 31 Aug 2022 16:40:51 +0000	[thread overview]
Message-ID: <20220831164157.A1A1AECAAD1@smtp.lore.kernel.org> (raw)
In-Reply-To: <2f55d594-8d68-6011-1159-7be428fac0b7@gmail.com>

Thank you, and I am looking at kirkstone...

-----Original Message-----
From: Khem Raj <raj.khem@gmail.com> 
Sent: Wednesday, August 31, 2022 12:38 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; Alexander Kanavin <alex.kanavin@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell #qemux86-64

On 8/31/22 4:36 AM, Monsees, Steven C (US) via lists.yoctoproject.org 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.

> Steve
> 
> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On 
> Behalf Of Alexander Kanavin
> Sent: Wednesday, August 31, 2022 7:23 AM
> To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
> Cc: yocto@lists.yoctoproject.org
> 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.
> 
> Alex
> 
> On Wed, 31 Aug 2022 at 13:17, Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:
>>
>>
>>
>> Hello:
>>
>>
>>
>> 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
>> /disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dunf
>> e
>> ll_Min>runqemu qemux86-64
>>
>> runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e ...
>>
>> runqemu - INFO - Continuing with the following parameters:
>>
>> KERNEL:
>> [/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dun
>> f 
>> ell_Min/tmp/deploy/images/qemux86-64/bzImage--5.4.192+gitAUTOINC+3fec
>> b 08507_85f0668fea-r0-qemux86-64-20220830151817.bin]
>>
>> MACHINE: [qemux86-64]
>>
>> FSTYPE: [ext4]
>>
>> ROOTFS:
>> [/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dun
>> f
>> ell_Min/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20
>> 2
>> 20830151817.rootfs.ext4]
>>
>> CONFFILE:
>> [/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dun
>> f
>> ell_Min/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20
>> 2
>> 20830151817.qemuboot.conf]
>>
>>
>>
>> runqemu - INFO - Setting up tap interface under sudo
>>
>> [sudo] password for smonsees:
>>
>> runqemu - INFO - Network configuration:
>> ip=192.168.7.2::192.168.7.1:255.255.255.0
>>
>> 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=192.168.7.2::192.168.7.1:255.255.255.0 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,
>>
>> Steve
>>
>>
>>
>>
>>
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> You automatically follow any topics you start or reply to.
>> View/Reply Online (#57957): 
>> https://lists.yoctoproject.org/g/yocto/message/57957
>> Mute This Topic: https://lists.yoctoproject.org/mt/93368526/1997914
>> Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
>> Mute 
>> #dunfell:https://lists.yoctoproject.org/g/yocto/mutehashtag/dunfell
>> Mute 
>> #qemux86-64:https://lists.yoctoproject.org/g/yocto/mutehashtag/qemux8
>> 6-64 Group Owner: yocto+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
>> [raj.khem@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>

      reply	other threads:[~2022-08-31 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MADEUP.171069DA592D7A03.12014@lists.yoctoproject.org>
2022-08-31 11:23 ` [yocto] #yocto #dunfell #qemux86-64 Alexander Kanavin
2022-08-31 11:36   ` Monsees, Steven C (US)
     [not found]   ` <MADEUP.17106AEC120529B5.1777@lists.yoctoproject.org>
2022-08-31 11:41     ` Alexander Kanavin
2022-08-31 12:09       ` Monsees, Steven C (US)
     [not found]       ` <630f4f99.050a0220.a96b.13e4SMTPIN_ADDED_MISSING@mx.google.com>
2022-08-31 12:12         ` Alexander Kanavin
2022-08-31 12:16           ` Monsees, Steven C (US)
     [not found]           ` <MADEUP.17106D1DBFB78C47.1777@lists.yoctoproject.org>
2022-08-31 13:15             ` Pavel Zhukov
2022-08-31 16:37     ` Khem Raj
2022-08-31 16:40       ` Monsees, Steven C (US) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220831164157.A1A1AECAAD1@smtp.lore.kernel.org \
    --to=steven.monsees@baesystems.com \
    --cc=alex.kanavin@gmail.com \
    --cc=raj.khem@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.