nyuuzyou/wikis huggingface dataset:
Ptest temp 18oct

< Archive
Ran on a NUC and compared with 2.6.m2.rc1
[<put-here-link-of-the-log> < FULL_LOG]
Failures
% increased
% decreased
Module not executed
Results
Package Name 	Tests ran	Passed	Failed	Passrate	Last Passrate	
acl 	380 	380 	0 	100.0 	100.0 	
attr 	143 	143 	0 	100.0 	100.0 	
bash 	79 	77 	2 	97.47 	97.47 	
bluez5 	25 	25 	0 	100.0 	100.0 	
busybox 	544 	533 	11 	97.98 	97.33 	
bzip2 	6 	6 	0 	100.0 	100.0 	
dbus-test 	21 	19 	2 	90.48 	90.48 	
diffstat 	440 	440 	0 	100.0 	100.0 	
diffutils 	20 	20 	0 	100.0 	100.0 	
e2fsprogs 	152 	117 	35 	76.97 	100.0 	
flex 	114 	114 	0 	100.0 	100.0 	
gawk 	344 	344 	0 	100.0 	100.0 	
gdbm 	30 	26 	4 	86.67 	100.0 	
gdk-pixbuf 	20 	20 	0 	100.0 	100.0 	
glib-2.0 	262 	253 	9 	96.56 	100.0 	
gstreamer1.0 	106 	104 	2 	98.11 	98.11 	
gzip 	21 	21 	0 	100.0 	100.0 	
kbd 	7 	7 	0 	100.0 	100.0 	
libpcre 	3 	3 	0 	100.0 	100.0 	
libusb1 	4 	4 	0 	100.0 	0 	
libxml-parser-perl	15 	15 	0 	100.0 	100.0 	
libxml2 	40 	38 	2 	95.0 	95.0 	
lttng-tools 	2089 	2020 	69 	96.7 	96.7 	
lzo 	5 	5 	0 	100.0 	100.0 	
nettle 	93 	93 	0 	100.0 	100.0 	
openssh 	53 	53 	0 	100.0 	100.0 	
openssl 	0 	0 	0 	0 	100.0 	
pango 	12 	3 	9 	25.0 	100.0 	
perl 	2301 	2300 	1 	99.96 	100.0 	
python 	30696 	30486 	210 	99.32 	99.39 	
quilt 	57 	57 	0 	100.0 	100.0 	
sed 	86 	86 	0 	100.0 	100.0 	
slang 	97 	97 	0 	100.0 	100.0 	
strace 	457 	422 	35 	92.34 	96.4 	
tcl 	148 	148 	0 	100.0 	99.32 	
util-linux 	480 	467 	13 	97.29 	97.29 	
valgrind 	558 	215 	343 	38.53 	49.1 	
zlib 	2 	2 	0 	100.0 	100.0
Ptest temp manish

< Archive
Ran on a NUC and compared with 2.6.m2.rc1
[<put-here-link-of-the-log> < FULL_LOG]
Failures
% increased
% decreased
Module not executed
Results
Package Name 	Tests ran	Passed	Failed	Passrate	Last Passrate	
acl 	380 	380 	0 	100.0 	100.0 	
attr 	143 	143 	0 	100.0 	100.0 	
bash 	79 	77 	2 	97.47 	97.47 	
bluez5 	25 	25 	0 	100.0 	100.0 	
busybox 	511 	502 	9 	98.24 	97.33 	
bzip2 	6 	6 	0 	100.0 	100.0 	
dbus-test 	21 	19 	2 	90.48 	90.48 	
diffstat 	440 	440 	0 	100.0 	100.0 	
diffutils 	20 	20 	0 	100.0 	100.0 	
e2fsprogs 	185 	144 	41 	77.84 	100.0 	
flex 	114 	114 	0 	100.0 	100.0 	
gawk 	344 	344 	0 	100.0 	100.0 	
gdbm 	30 	26 	4 	86.67 	100.0 	
gdk-pixbuf 	20 	20 	0 	100.0 	100.0 	
glib-2.0 	262 	253 	9 	96.56 	100.0 	
gstreamer1.0 	106 	104 	2 	98.11 	98.11 	
gzip 	21 	21 	0 	100.0 	100.0 	
kbd 	7 	7 	0 	100.0 	100.0 	
libpcre 	3 	3 	0 	100.0 	100.0 	
libusb1 	4 	4 	0 	100.0 	0 	
libxml-parser-perl	15 	15 	0 	100.0 	100.0 	
libxml2 	40 	38 	2 	95.0 	95.0 	
lttng-tools 	2089 	2020 	69 	96.7 	96.7 	
lzo 	5 	5 	0 	100.0 	100.0 	
nettle 	93 	93 	0 	100.0 	100.0 	
openssh 	53 	53 	0 	100.0 	100.0 	
openssl 	0 	0 	0 	0 	100.0 	
pango 	12 	3 	9 	25.0 	100.0 	
perl 	2301 	2300 	1 	99.96 	100.0 	
python 	30686 	30490 	196 	99.36 	99.39 	
quilt 	57 	57 	0 	100.0 	100.0 	
sed 	86 	86 	0 	100.0 	100.0 	
slang 	97 	97 	0 	100.0 	100.0 	
strace 	457 	422 	35 	92.34 	96.4 	
tcl 	148 	148 	0 	100.0 	99.32 	
util-linux 	480 	467 	13 	97.29 	97.29 	
valgrind 	558 	215 	343 	38.53 	49.1 	
zlib 	2 	2 	0 	100.0 	100.0
Ptest testing

< Archive
Ran on a NUC and compared with 2.3.2_rc1
[<put-here-link-of-the-log> < FULL_LOG]
Failures
% increased
% decreased
Module not executed
Results
Package Name	Tests ran	Passed	Failed	Passrate	Last Passrate	
acl 	380 	380 	0 	100.0 	100.0 	
attr 	143 	143 	0 	100.0 	100.0 	
bash 	76 	72 	4 	94.74 	94.74 	
bluez5 	25 	25 	0 	100.0 	100.0 	
busybox 	518 	508 	10 	98.07 	98.26 	
bzip2 	6 	6 	0 	100.0 	100.0 	
dbus-test 	15 	4 	11 	26.67 	26.67 	
diffstat 	440 	440 	0 	100.0 	100.0 	
diffutils 	17 	17 	0 	100.0 	100.0 	
e2fsprogs 	1 	0 	1 	0.0 	0.0 	
flex 	114 	114 	0 	100.0 	100.0 	
gawk 	298 	297 	1 	99.66 	99.66 	
gdbm 	22 	22 	0 	100.0 	100.0 	
gdk-pixbuf 	20 	20 	0 	100.0 	100.0 	
glib-2.0 	252 	251 	1 	99.6 	99.6 	
kbd 	7 	7 	0 	100.0 	100.0 	
libpcre 	3 	3 	0 	100.0 	100.0 	
libxml2 	39 	36 	3 	92.31 	92.31 	
lttng-tools 	2057 	1988 	69 	96.65 	96.65 	
nettle 	88 	87 	1 	98.86 	98.86 	
openssh 	34 	33 	1 	97.06 	97.06 	
openssl 	52 	52 	0 	100.0 	100.0 	
pango 	12 	12 	0 	100.0 	100.0 	
perl 	2286 	2285 	1 	99.96 	99.96 	
perl5 	2286 	2285 	1 	99.96 	99.96 	
python 	32230 	32104 	126 	99.61 	99.61 	
quilt 	57 	57 	0 	100.0 	100.0 	
strace 	335 	334 	1 	99.7 	99.7 	
tcl 	148 	146 	2 	98.65 	98.65 	
util-linux 	108 	106 	2 	98.15 	98.15 	
valgrind 	553 	296 	257 	53.53 	53.53 	
zlib 	2 	2 	0 	100.0 	100.0
QA/Test Report Tool

==General Expectations==
(add link share-ability of results to the list of requirements when it fits somewhere)
Here's a list of initial expectations of the Test Reporting Tool.
# The TRT must be able to receive test reports via a remote communication protocol.
## From expected sources of results (Auth)
## To existing test buckets (logical test belonging separation, could be by test component) through report sessions with:
##* ability to resume
##* ability to update existing results
##* ability to abort/discard
## Using existing test report protocols like XML 
# The TRT should present an interface with views organized towards the following objectives:
## Test Buckets (browsing a component's test results history)
## Test Collections (The type of Milestone/Release or another defined collection)
# The TRT should be able to identify the type of result it is consuming.
## Boolean test results Passed/Failed
## Numeric test results (measurements)
==QA Data Sources==
There are several sources of quality data we'd like to be able to track in a QA dashboard:
* oe-selftest results
* bitbake-selftest results
* build performance metrics
* buildhistory trends
* ???
==Prior Art==
* QA maintains QA_sanity_history reports which list sanity test results and compares them to the previous run (anyone know how these are generated?).
* Someone (?) generates graphs of the performance data.
* CustomReports includes visualisation for test run pass rates and graphs changes to success rates.
* Jenkins parses and displays JUnit XML output out of the box, a break down of How Jenkins Displays JUnit output.
* OpenQA from openSUSE has a visual status overview for the tests run vs an installed OS. Code is on github: https://github.com/os-autoinst/openQA and initial release announcement provides an overview: openSUSE Announces First Public Release of openQA.
QA/sandbox

=Testing data=
This is a live status report. The information contained is relevant to the latest test suite performed for Yocto 2.4.x .
=Summary Report=
COMMIT UNDER TEST
poky : f7b90ab3eaf832bd81f3efc1dab4dcf6863ac284
meta-intel: d68dda959b5bf6f90aa8e5c2f027be324bb68e14
meta-qt4 : f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-tlk : f737ffa2f607f61a6f9f5490758797c923f4ee44
	
=Detailed Report=
QA Automated Status template

=Testing data=
 
 Test type: Full Pass Release Test
 Branch: master
 Build name: 1.8_M4.rc1
 poky commit: 8b3d3e7c957ad06c390886487f69aeb8e145da6a 
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8_M4.rc1/
 Distributions tested: Ubuntu 14.04 64bit, Fedora 21 64bit, Opensuse 13.2 64bit, CentOS 7 64 bit 
=Test Run Summary Report=
= Build Performance Test =
Detailed description on how performance test are run can be found on Performance Test wiki.
The below charts are displaying the build performance trend for 1.8 by milestone starting 1.6 on Master. The charts by Milestone can be accessed at this link where you can view more detailed information or by clicking on the images which will open a new window with the interactive chart.
=Detailed Report=
{{#if: |
==ADT==
QA BKM sharing

This page is to show the BKMs, which could help QA or development work with Yocto.
* How to Watch Yocto Bugs
* Test Report Format
* Enabling Automation Test in Poky
* How to setup environment for Yocto with 1.1 on Fedora 16
* How to setup environment for ADT with 1.1 on Fedora 16
QA Status (Demo)

=Testing data=
This is a live status report. The information contained is relevant to the latest test suite performed for Yocto 2.4.x .
=Summary Report=
COMMIT UNDER TEST
poky : f7b90ab3eaf832bd81f3efc1dab4dcf6863ac284
meta-intel: d68dda959b5bf6f90aa8e5c2f027be324bb68e14
meta-qt4 : f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-tlk : f737ffa2f607f61a6f9f5490758797c923f4ee44
	
=Detailed Report=
QA Status TEMPLATE

=Testing data=
 
 Test type: Full Pass Release
 Branch: master
 Milestone: M1
 Build name: 1.6_M1
 poky commit: 215dab864e7cf74394840621ad0754db593708f1
 Eclipse Plugin commit Kepler: 84c1361ee96b781666a23f068244d4f1252be712
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20131119-7
 Distributions tested: Ubuntu 13.04 64bit, Ubuntu 13.10 64bit, Fedora 19 64bit, Fedora 19 32bit 
=Summary Report=
	
=Detailed Report=
QA run history

Full Pass for 2.0.2 (2016-05-24)Full Pass for 2.1 (2016-04-20)Full Pass for 2.0.1 (2016-01-18)Full Pass for 2.2 (2015-12-21)Full Pass for 2.1 (2015-12-10)Full Pass for 2.0 (2015-11-02)Full Pass for 2.0 (2015-10-22)Full Pass for 2.0 (2015-10-02)Full Pass for 1.8.1 (2015-09-30)Full Pass for 1.8 (2015-09-15)Full Pass for 1.9_M2.rc2 (2015-08-10)Full Pass for 1.9_M2.rc1 (2015-08-02)Full Pass for 1.9_M1.rc2 (2015-07-10)Full Pass for 1.9_M1.rc1 (2015-06-25)WW26 - 2015-06-25 - Full Pass 1.9 M1.rc1Full Pass for 1.6.3.rc4 (2015-05-14)Full Pass for 1.7.2_rc3 (2015-05-01)
QA Automated Status template
Qemuppc Boot Hangs

qemuppc is randomly hanging at boot during sanity testing. For example:
* https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/581
* https://autobuilder.yocto.io/builders/nightly-ppc/builds/592
Despite initial suspicions this was not due to entropy problems.
It is *not*:
* Specific to a host OS (observed on centos7, debian8, ubuntu1710)
* Specific to image recipe (happens sato, sato-sdk, lsb, lsb-sdk, minimal, full-cmdline)
* Specific to DISTRO (poky and poky-lsb)
The hang usually occurs after:
 [ 6.667445] udevd[104]: starting version 3.2.2
 [ 6.743262] udevd[105]: starting eudev-3.2.2
and is hanging in the poll() call in udevadm-settle.c:adm_settle(), it doesn't seem to return from the syscall. Further tracing confirms that it goes into poll_schedule_timeout() in fs/select.c:do_poll() and doesn't come out again. The time parameters all look sane so its likely the kernel locking up or sleeping and failing to wake.
In some cases the boot proceeds further and hangs in the dropbear key creation.
The timing of the usb-tablet device does vary in the boot logs however the hang has been observed with the usb-tablet device removed.
It seems that running a build in parallel with testimage does help the issue occur more frequently.
I wondered about a connection with host cpufreq changes. In order to test, I booted with "intel_pstate=disable" on the kernel commandline and tried:
while true; do cpupower frequency-set -f 1200000 > /dev/null; sleep 0.25; cpupower frequency-set -f 2200000 > /dev/null; done
along with setting to max cpu freq and also setting just to min cpu freq.
I've observed hangs in all combinations although the likelyhood of a hang seemed higher with the alternating frequency.
I also tried the script:
 import time
 import random
 import subprocess 
 
 cpus = range(0,87)
 freqs = range(1200000, 2200000, 100000)
 
 while True:
 for cpunum in cpus:
 f = random.choice(freqs)
 with open("/sys/devices/system/cpu/cpu%d/cpufreq/scaling_setspeed" % cpunum, 'w') as speed:
 speed.write("%d\n" % f)
 
 time.sleep(0.05)
which also seems to make hangs more likely somehow.
The powersave=off commandline option does not help.
RPM5-Uprev

The following is a summary of the RPM5 Uprev and related. This will be expanded to include a future roadmap as possible.
The RPM5 work includes both rpm5.org and Zypper related sources and dependencies.
* RPM5
 * Uprev RPM5 to latest version (5.4.0)
 * Include package separation based on upstream SPEC file
 * Consider also supporting previous stable release (5.3.7)
* Zypper
 * Dependent upon the RPM5 uprev
 * Sync up API usage with current RPM5 work
 * Change Zypper to support variable arch as implemented by RPM5
* Rootfs creation
 * Sync to latest RPM5 as necessary
 * Create install repository for Zypper
 * Create rootfs using Zypper, if possible
Goal in the end is to be able to have a more modern version of RPM5. A newer and/or better integrated version of Zypper. This newer version needs to hopefully use Poky's understanding of "arch" instead of it's own. A simple mechanism to construct a Zypper package repository structure. And to use that structure to generate a filesystem.
----
Roadmap:
Jan 6:
 * Uprev RPM5 to 5.4.0 (in Poky Contrib)
Jan 7
 * Rootfs creation with RPM5 5.4.0
Jan 13
 * Final RPM5 uprev and integration, including package seperation
 * Initial Zypper API integration and sync to RPM5
Jan 17-21
 * RPM5 arch enhancement
 * Zypper repository (createrepo) support
?
 * Zypper used to create rootfs (may not happen for 1.0)
Raspberry Pi

This page is a central repository for information about using the Yocto Project tools and metadata with the Raspberry Pi ARM-based single-board computer.
== OpenEmbedded Layer ==
There is a meta-raspberrypi OpenEmbedded layer listed on the OpenEmbedded layer index, hosted on github. It is maintained by DJWillis, who provides more information about it in a blog post.
== QtonPi ==
The following individuals have expressed an interest in getting Qt working on the Raspberry Pi. IRC nicks shown are for freenode.net channel #qtonpi, #oe, or #yocto. Please add yourself to this list as necessary.
* Leon Woestenberg
* Brian Hutchinson
* Quim Gil
* timo@linux.com
* Paul Eggleton
* Peter Mui
For more details, see the wiki page.
Recipe Versions

This page lists the expected versions of major packages that will be in the Yocto Project 5.0 "Scarthgap" release (at the time of writing).
For further details, please contact the relevant maintainer.
Recipe 	Version	Maintainer 	Notes
binutils 	2.42 	Khem Raj <raj.khem@gmail.com> 	
gcc 	13.2 	Khem Raj <raj.khem@gmail.com> 	GCC 14 scheduled after YP
glibc 	2.39 	Khem Raj <raj.khem@gmail.com> 	Due 2024-02-01
linux-yocto	6.6.x 	Bruce Ashfield <bruce.ashfield@gmail.com>	LTS until December 2026
python3 	3.12 	Trevor Gamblin <tgamblin@baylibre.com> 	3.13 scheduled 2024-10-01
Key recipe versions by release
Release 	linux-yocto (kernel)	gcc 	binutils	glibc	python3
scarthgap (5.0)	6.6.x 	13.2	2.42 	2.39 	3.12.x
kirkstone (4.0)	5.10.x / 5.15.x 	11.4	2.38 	2.35 	3.10.x
dunfell (3.1) 	5.4.x 	9.5 	2.34 	2.31 	3.8.x
Release Branch Tag Matrix

== Introduction ==
This is a list of all repositories utilized by the main yocto-autobuilder at http://autobuilder.yoctoproject.org:8011
Please utilize this matrix for generation of releases/release candidates
== Release Branch/Tag Matrix ==
This table gives guidance for each repositories branching and tagging policy. For example, to generate a release candidate for 1.5_M1:
poky: Utilize the 1.5_M1.rc1 tag.
meta-intel: Utilize the 1.5_M1.rc1 tag.
oecore: Utilize HEAD
meta-fsl-ppc: ??
meta-fsl-arm: ??
bitbake: Utilize HEAD of master
eclipse-poky: Utilize the 1.5_M1.rc1 tag
repository 	Tag or HEAD for releases	Milestone Branches?	Poky release branch names?	Notes
poky 	Tag 	Yes 	Yes 	
eclipse-poky	Tag 	No 	Yes 	
meta-intel 	Tag 	No 	Yes 	
oecore 	Currently HEAD 	No 	Yes 	
meta-fsl-ppc	? 	? 	? 	
meta-fsl-arm	? 	? 	? 	
bitbake 	HEAD 	No 	No 	1.16 for danny, 1.18 for dylan, master for yocto-1.5
Results ptest ptest busybox 2015-05-06

Results for ptest b2b59b14ecfe13ba794d92f97d1403d6503c7407
Package Name	Tests ran	Passed	Failed	Passrate	Last Passrate	Run difference
busybox 	471 	454 	17 	96.0 	94.0 	Yes
Results for ptest ptest busybox 2015-05-06:********************************Tests that failed now and worked last time: 0Tests that passed now and and failed last time: 13tar writing into read-only dirtar-extracts-filetar-handles-exclude-and-extract-liststar hardlinks and repeated filestar hardlinks modetar-handles-multiple-X-optionstar symlinks modetar-extracts-all-subdirstar-handles-nested-excludetar-handles-empty-include-and-non-empty-exclude-listtar-extracts-multiple-filestar-archives-multiple-filestar strips /../ on extractTests that were skipped now and worked last time: 1uniq input outfile (two files)Tests that were skipped last time and worked now: 1uniq inp/usr/lib/busybox/ptest/testsuite/unzip.tests
RossBurton/Cove

= Cove (or CoVE, or The New CVE Tool) =
Django webapp
Cron job to pull new data from mitre and populate the database. 
Database contains every CVE. New CVEs in pending state to start with. If not relevant to yocto, mark NA and disappears. On review, each release is independently handled. Mark as vulnerable, or mitigated with a reference (update, backport, whatever).
Rpm's Repository Setup for QA

== Requirements ==
To setting up a repository to have different version of rpm packages to be used in smart tests for BSP you will need:
* Apache 2 installed and configured (may not need too much configuration).
* createrepo installed
== Steps - Host ==
1. Create a folder and upload inside the *.rpm files with different versions
 mkdir /var/www/html/rpm
2. Create the repo using createrepo tool
 createrepo /var/www/html/rpm/
3. Ensure repodata/ directory was created with below files inside: 
 rpm/repodata/filelists.xml.gz
 rpm/repodata/other.xml.gz
 rpm/repodata/primary.xml.gz
 rpm/repodata/repomd.xml
== Steps - DUT (Device Under Test) ==
1. Inform smart of package database you want to use, server.name = host_ip 
 smart channel --add all type=rpm-md baseurl=http://server.name/rpm 
2. Fetch the repository information using below command 
 
 smart update
3. Now follow the steps indicated on smart test cases for BSP
Running an x86 Yocto Linux image under QEMU KVM

== Host OS preparation (VM manager host OS) ==
Steps:
 
1.Enable KVM on the host machine
 
2. Enable on host OS vhost-net virtio networking accelerator to mitigate overhead on QEMU virtualization environment.
Load vhost_net module on KVM Host.
 ubik@sentry:~$ sudo modprobe vhost_net
 ubik@sentry:~$ lsmod | grep vhost
The result of running the commands should be similar to the following:
 vhost_net 32359 0 
 macvtap 18528 1 vhost_net
In order for an user to use vhost-net module enter the following commands:
 sudo addgroup --system vhost-net
 sudo adduser $USER vhost-net
 sudo chown root:vhost-net /dev/vhost-net
 sudo chmod 0660 /dev/vhost-net
Modify /etc/modules so that vhost_net module is automatically loaded at boot time:
 sudo vim /etc/modules
For example:
File: /etc/modules
Content:
 # /etc/modules: kernel modules to load at boot time.
 #
 # This file contains the names of kernel modules that should be loaded
 # at boot time, one per line. Lines beginning with "#" are ignored.
 
 lp
 rtc
 vhost_net
On a system that runs udev, you will probably need to add the following line somewhere in your udev configuration so it will automatically give the right group to the newly created device.
For example:
File: /etc/udev/rules.d/40-permissions.rules
Content:
 KERNEL=="vhost-net", GROUP="vhost-net", MODE="0660"
Restart udev:
 ubik@sentry:~$ sudo restart udev
 [sudo] password for ubik: 
 udev start/running, process 28404
Note
* You need log out then log in the non-root user to take the effect
 
3. Start the VM using the line below:
 
 ubik@sentry:~/yoctoproject/build$ sudo kvm -kernel /home/ubik/yoctoproject/build/tmp/deploy/images/bzImage-qemux86.bin -net nic,model=virtio -net \
 tap,vlan=0,ifname=tap0,script=no,downscript=no,vhost=on -drive file=/home/ubik/yoctoproject/build/tmp/deploy/images/core-image-core-qemux86.ext3,if=virtio \
 -show-cursor -usb - usbdevice wacom-tablet -vga vmware -no-reboot -enable-kvm -cpu host -m 128 --append "vga=0 root=/dev/vda rw mem=128M \
 ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 " 
 
This is an example of running a virtualized Yocto image, with KVM active, cpu host features exported in the Yocto VM, paravirtualization enabled, and using virtio interfaces for disk access and networking.
On a machine equipped with a Core i7 2600 (3.4GHz, 4 cores, 8 threads)/8 GB RAM/Intel SSD G3 120GB qemux86 Yocto Linux boots in around 7 seconds for a core-image-x11. The same image boots in 20 seconds without virtualization optimizations and feels slower in usage.
== Guest OS preparation ==
 
The following kernel configs needs to be enabled for Yocto Linux guest OS:
 [...]
 CONFIG_PARAVIRT_GUEST=y
 CONFIG_KVM_CLOCK=y
 CONFIG_KVM_GUEST=y
 CONFIG_PARAVIRT=y
 CONFIG_PARAVIRT_CLOCK=y
 CONFIG_VIRTIO_MMIO=y
 [..]
Screenshots example:
SDK Toolchain on WSL

Windows user can now do development using yocto project SDK toolchain through Windows Subsystem for Linux (WSL). You may look for WSL Documentation for more information about WSL
= Install and setup WSL on Windows =
Refer to Windows Subsystem for Linux Installation Guide for Windows 10 for WSL installation Guide.
WSL comes with very minimal packages,so after you install and start up WSL, You need to install essential packages on your WSL. 
The following command installs the packages based on 
WSL Debian GNU/Linux:
 $apt install xz-utils python make
WSL Ubuntu 16.04 LTS and 18.04 LTS. 
 $apt install make 
you might want to refer to Using the Standard SDK for SDK Setup.
SecondTime

< Archive
Ran on a NUC and compared with 2.6.M2.rc1
[<put-here-link-of-the-log> < FULL_LOG]
Failures
% increased
% decreased
Module not executed
Results
Package Name 	Tests ran	Passed	Failed	Passrate	Last Passrate	
acl 	380 	380 	0 	100.0 	100.0 	
attr 	143 	143 	0 	100.0 	100.0 	
bash 	79 	76 	3 	96.2 	97.47 	
bluez5 	7 	7 	0 	100.0 	100.0 	
busybox 	524 	510 	14 	97.33 	97.33 	
bzip2 	6 	6 	0 	100.0 	100.0 	
dbus-test 	21 	19 	2 	90.48 	90.48 	
diffstat 	440 	440 	0 	100.0 	100.0 	
diffutils 	20 	20 	0 	100.0 	100.0 	
e2fsprogs 	309 	309 	0 	100.0 	100.0 	
flex 	114 	114 	0 	100.0 	100.0 	
gawk 	339 	339 	0 	100.0 	100.0 	
gdbm 	25 	25 	0 	100.0 	100.0 	
gdk-pixbuf 	20 	20 	0 	100.0 	100.0 	
glib-2.0 	253 	253 	0 	100.0 	100.0 	
gstreamer1.0 	106 	104 	2 	0 	98.11 	
gzip 	21 	21 	0 	100.0 	100.0 	
kbd 	7 	7 	0 	100.0 	100.0 	
libpcre 	3 	2 	1 	66.67 	100.0 	
libxml-parser-perl	15 	15 	0 	100.0 	100.0 	
libxml2 	134 	134 	0 	100.0 	95.0 	
lttng-tools 	2089 	2020 	69 	96.7 	96.7 	
lzo 	5 	5 	0 	100.0 	100.0 	
nettle 	93 	93 	0 	100.0 	100.0 	
openssh 	60 	60 	0 	100.0 	100.0 	
openssl 	53 	53 	0 	100.0 	100.0 	
pango 	12 	12 	0 	100.0 	100.0 	
perl 	2287 	2287 	0 	100.0 	100.0 	
python 	30548 	30362 	186 	99.39 	99.39 	
quilt 	57 	57 	0 	100.0 	100.0 	
sed 	86 	86 	0 	100.0 	100.0 	
slang 	97 	97 	0 	100.0 	100.0 	
strace 	374 	344 	30 	91.98 	96.4 	
tcl 	148 	147 	1 	99.32 	99.32 	
util-linux 	376 	364 	12 	96.81 	97.29 	
valgrind 	559 	300 	259 	53.67 	49.1 	
zlib 	2 	2 	0 	100.0 	100.0