Created attachment 4332 [details] Booting log file for arm64 arm64 and ppc700 architectures image is not booting on qemu with gui mode. without gui( using this parameter slirp nographic ) mode is booting successfully. I have attached log also.
Created attachment 4333 [details] Booting log file for ppc700
Comment on attachment 4332 [details] Booting log file for arm64 runqemu Image-qemuarm64.bin root core-image-sato-sdk-qemuarm64.qemuboot.conf runqemu - INFO - Setting STAGING_DIR_NATIVE to OECORE_NATIVE_SYSROOT (/home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux) runqemu - INFO - Setting STAGING_BINDIR_NATIVE to /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin runqemu - INFO - Continuing with the following parameters: KERNEL: [/home/shashwat/pravin/bsp_qemu/2.6/Image-qemuarm64.bin] MACHINE: [qemuarm64] FSTYPE: [nfs] NFS_DIR: [/home/shashwat/pravin/bsp_qemu/2.6/root] CONFFILE: [/home/shashwat/pravin/bsp_qemu/2.6/core-image-sato-sdk-qemuarm64.qemuboot.conf] runqemu - INFO - Setting up tap interface under sudo /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/runqemu-ifup: line 115: /usr/local/sbin/iptables: No such file or directory /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/runqemu-ifup: line 116: /usr/local/sbin/iptables: No such file or directory /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/runqemu-ifup: line 119: /usr/local/sbin/iptables: No such file or directory runqemu - INFO - Running runqemu-export-rootfs start /home/shashwat/pravin/bsp_qemu/2.6/root... PSEUDO=/home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/pseudo Creating exports file... Starting User Mode nfsd /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/pseudo -P /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/unfsd -p -N -i /home/shashwat/.runqemu-sdk/nfs6.pid -e /home/shashwat/.runqemu-sdk/exports6 -n 3061 -m 3060 On your target please remember to add the following options for NFS nfsroot=IP_ADDRESS:/home/shashwat/pravin/bsp_qemu/2.6/root,nfsvers=3,port=3061,udp,mountport=3060 runqemu - INFO - Network configuration: 192.168.7.2::192.168.7.1:255.255.255.0 runqemu - INFO - Running /home/shashwat/pravin/bsp_qemu/2.6/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/qemu-system-aarch64 -device virtio-net-device,netdev=net0, mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -show-cursor -device virtio-rng-pci -monitor null -machine virt -cpu cortex-a57 -m 512 -serial mon:vc -serial null -kernel /home/shashwat/pravin/bsp_qemu/2.6/Image-qemuarm64.bin -append 'root=/dev/nfs nfsroot=192.168.7.1:/home/shashwat/pravin/bsp_qemu/2.6/root,nfsvers=3,port=3061, udp,mountport=3060 rw highres=off mem=512M ip=192.168.7.2::192.168.7.1:255.255.255.0 console=ttyAMA0,38400
ARM64 has never had a graphical boot, so that isn't a bug. qemuppc has worked in the past, but it is an aging emulation, so something outside of the kernel may be broken. I can launch a build for qemuppc and see what I get for graphics.
What kernel are you building against ? I just built and booted core-image-sato against master, and 4.14.48 booted with the sato desktop and no issues. As mentioned before, ARM64 is not expected to work.
(In reply to comment #3) > ARM64 has never had a graphical boot, so that isn't a bug. > > qemuppc has worked in the past, but it is an aging emulation, so something > outside of the kernel may be broken. > > I can launch a build for qemuppc and see what I get for graphics. Yes qemuarm64 had never graphical boot, but it was booting whithaout gui also. but now it is completly not booting.
(In reply to comment #4) > What kernel are you building against ? > > I just built and booted core-image-sato against master, and 4.14.48 booted > with the sato desktop and no issues. > > As mentioned before, ARM64 is not expected to work. (In reply to comment #3) > ARM64 has never had a graphical boot, so that isn't a bug. > > qemuppc has worked in the past, but it is an aging emulation, so something > outside of the kernel may be broken. > > I can launch a build for qemuppc and see what I get for graphics. qemuppc is booting here also, but after booting blank screen is coming.
(In reply to comment #4) > What kernel are you building against ? > > I just built and booted core-image-sato against master, and 4.14.48 booted > with the sato desktop and no issues. > > As mentioned before, ARM64 is not expected to work. following is yocto version infomation which i am using. Yocto version - 2.6 M1 rc1 commit id - ddbd7b0cd6580ee26e11aa87e426fb294b372d64 kernel version - 4.14.48-yocto-standard
I have used autobuilder generated images. following is the link form there I downloaded images of arm64 and ppc700. https://autobuilder.yocto.io/pub/releases/yocto-2.6_M1.rc1/machines/qemu/
Following are the steps to arm64 on qemu following is the link form there I downloaded images of arm64 and ppc700. https://autobuilder.yocto.io/pub/releases/yocto-2.6_M1.rc1/machines/qemu/qemuarm64/ 1)downloaded core-image-sato-sdk-qemuarm64.tar.bz2 from above link 2)downloaded core-image-sato-sdk-qemuarm64.qemuboot.conf from above link 3)downloaded Image-qemuarm64.bin from above link 4)downloaded toolchain from following link https://autobuilder.yocto.io/pub/releases/yocto-2.6_M1.rc1/toolchain/x86_64/poky-glibc-x86_64-core-image-sato-aarch64-toolchain-2.5%2Bsnapshot.sh 5) install the toolchain in host system 6) source toolchain-path/environment-setup-aarch64-poky-linux 7) extract the tar.bz rootfs file. used following command runqemu-extract-sdk core-image-sato-sdk-qemuarm64.tar.bz2 rootfs 8) after that we tried runqemu command runqemu nfs Image-qemuarm64.bin rootfs core-image-sato-sdk-qemuarm64.qemuboot.conf after this command should qemu should launch, but nothing comming logs i have already attached. if I run following command with nographics option then it is booting successfully. runqemu-extract-sdk core-image-sato-sdk-qemuarm64.tar.bz2 rootfs slrip nographic
please ignore the last step follow this below step runqemu nfs Image-qemuarm64.bin rootfs core-image-sato-sdk-qemuarm64.qemuboot.conf slrip nographic
I'm still able to build and boot this. No issues here. I need a source based reproducer, not autobuilder issues, since I cannot debug them. As of now, I'm not seeing any issues, and won't do any more on this. root@qemuarm64:~# uname -a Linux qemuarm64 4.14.48-yocto-standard #1 SMP PREEMPT Thu Jun 21 13:13:07 UTC 2018 aarch64 GNU/Linux root@qemuarm64:~#
I believe that the autobuilder already tests non-graphical boot of arm64 and QA have reported that it works in non-graphical for them. There is another bug for ppc so resolving this one as already working.