Yocto Project Discussions
 help / color / mirror / Atom feed
From: Pavel Zhukov <pavel@zhukoff.net>
To: steven.monsees@baesystems.com
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	"Monsees,
	Steven C (US) via lists.yoctoproject.org"
	<steven.monsees=baesystems.com@lists.yoctoproject.org>,
	yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell #qemux86-64
Date: Wed, 31 Aug 2022 15:15:09 +0200	[thread overview]
Message-ID: <87bks0k0ug.fsf@gentoo.zhukoff.net> (raw)
In-Reply-To: <MADEUP.17106D1DBFB78C47.1777@lists.yoctoproject.org>


"Monsees, Steven C (US) via lists.yoctoproject.org" <steven.monsees=baesystems.com@lists.yoctoproject.org> writes:

> I will have to double check, but the issue did not appear under zeus... 
> so qemu changed sometime after zeus ?
Not qemu but runqemu script has been changed not so long time ago (this
year) to pass `-display sdl` parameter unless nographic option has been 
specified. As it was mentioned you have to pass -nographic to use
runqemu without SDL frontend

>
> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com> 
> Sent: Wednesday, August 31, 2022 8:12 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.
>
>
> The issue is on your side, not on yocto's. By default qemu is
> configured to show graphical output in a X11 window, so you need to
> run it in a X11 session, with correctly set DISPLAY environment
> variable.
>
> Alex
>
> On Wed, 31 Aug 2022 at 14:10, Monsees, Steven C (US) <steven.monsees@baesystems.com> wrote:
>>
>>
>> One final question, does this issue exist in kirkstone-4.0.2 ?
>>
>> Thanks,
>> Steve
>>
>> -----Original Message-----
>> From: Alexander Kanavin <alex.kanavin@gmail.com>
>> Sent: Wednesday, August 31, 2022 7:42 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.
>>
>>
>> I need to see the errors to give a useful answer. If you want wayland, use core-image-weston as the image.
>>
>> Alex
>>
>> On Wed, 31 Aug 2022 at 13:37, Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@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 ?
>> >
>> > 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/d
>> > > un
>> > > fe
>> > > 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/
>> > > du
>> > > nf
>> > > ell_Min/tmp/deploy/images/qemux86-64/bzImage--5.4.192+gitAUTOINC+3
>> > > fe cb 08507_85f0668fea-r0-qemux86-64-20220830151817.bin]
>> > >
>> > > MACHINE: [qemux86-64]
>> > >
>> > > FSTYPE: [ext4]
>> > >
>> > > ROOTFS:
>> > > [/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/
>> > > du
>> > > nf
>> > > ell_Min/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64
>> > > -2
>> > > 02
>> > > 20830151817.rootfs.ext4]
>> > >
>> > > CONFFILE:
>> > > [/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/
>> > > du
>> > > nf
>> > > ell_Min/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64
>> > > -2
>> > > 02
>> > > 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.
> View/Reply Online (#57961): https://lists.yoctoproject.org/g/yocto/message/57961
> Mute This Topic: https://lists.yoctoproject.org/mt/93368526/6390638
> 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/qemux86-64
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [pavel@zhukoff.net]
> -=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2022-08-31 13:19 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 [this message]
2022-08-31 16:37     ` Khem Raj
2022-08-31 16:40       ` Monsees, Steven C (US)

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=87bks0k0ug.fsf@gentoo.zhukoff.net \
    --to=pavel@zhukoff.net \
    --cc=alex.kanavin@gmail.com \
    --cc=steven.monsees=baesystems.com@lists.yoctoproject.org \
    --cc=steven.monsees@baesystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox