Boot all yes config kernel with QEMU
Hi, I'd like to build and boot an allyesconfig kernel with QEMU. Building is no problem but when I try to boot it I get problems because the host system does not support features requested by the VM. How does one go about testing an allyesconfig kernel? Back story: I'm trying to set up some CI infrastructure to run scripts/leaking_addresses.pl against the various stable kernels. thanks, Tobin. signature.asc Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Boot all yes config kernel with QEMU
On Tue, 23 Oct 2018 13:56:42 +1100, "Tobin C. Harding" said: > I'd like to build and boot an allyesconfig kernel with QEMU. Building > is no problem but when I try to boot it I get problems because the host > system does not support features requested by the VM. > > How does one go about testing an allyesconfig kernel? As you have noticed, there's no guarantee that a allyesconfig kernel will boot in a VM because the VM doesn't support something. Note that you're going to have the exact same issues booting on real hardware - you'll discover that there's configs that won't boot on real hardware either - and even if it boots, you'll probably not have the I/O devices to test even a third of the drivers unless you have a really well stocked test lab. But then, all(yes|mod|no)config aren't intended for actual booting and testing - they're pretty much build testing all the options in one build. Basically, one of two things happen after building an all-something-config: 1) The build completes and you get on with your life 2) The build fails, and you get to send an email telling the maintainer that their driver for the Frobnozz 1300 Widget won't build in =y in kernel 4.21-rc2, or whatever your build died on. pgpGHG445qbUa.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Boot all yes config kernel with QEMU
On Tue, Oct 23, 2018 at 12:22:44AM -0400, valdis.kletni...@vt.edu wrote: > On Tue, 23 Oct 2018 13:56:42 +1100, "Tobin C. Harding" said: > > > I'd like to build and boot an allyesconfig kernel with QEMU. Building > > is no problem but when I try to boot it I get problems because the host > > system does not support features requested by the VM. > > > > How does one go about testing an allyesconfig kernel? > > As you have noticed, there's no guarantee that a allyesconfig kernel will > boot in > a VM because the VM doesn't support something. Note that you're going to have > the exact same issues booting on real hardware - you'll discover that there's > configs > that won't boot on real hardware either - and even if it boots, you'll > probably not have > the I/O devices to test even a third of the drivers unless you have a really > well stocked > test lab. > > But then, all(yes|mod|no)config aren't intended for actual booting and > testing - they're > pretty much build testing all the options in one build. > > Basically, one of two things happen after building an all-something-config: > > 1) The build completes and you get on with your life > > 2) The build fails, and you get to send an email telling the maintainer that > their driver for the Frobnozz 1300 Widget won't build in =y in kernel > 4.21-rc2, > or whatever your build died on. I love this answer :) thanks Valdis. If you are taking a walk and feel like pondering something; any ideas how I could get the most files possible to show up in /proc and /sys? thanks, Tobin. signature.asc Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Boot all yes config kernel with QEMU
On Tue, Oct 23, 2018 at 05:16:42PM +1100, Tobin C. Harding wrote: > On Tue, Oct 23, 2018 at 12:22:44AM -0400, valdis.kletni...@vt.edu wrote: > > On Tue, 23 Oct 2018 13:56:42 +1100, "Tobin C. Harding" said: > > > > > I'd like to build and boot an allyesconfig kernel with QEMU. Building > > > is no problem but when I try to boot it I get problems because the host > > > system does not support features requested by the VM. > > > > > > How does one go about testing an allyesconfig kernel? > > > > As you have noticed, there's no guarantee that a allyesconfig kernel will > > boot in > > a VM because the VM doesn't support something. Note that you're going to > > have > > the exact same issues booting on real hardware - you'll discover that > > there's configs > > that won't boot on real hardware either - and even if it boots, you'll > > probably not have > > the I/O devices to test even a third of the drivers unless you have a > > really well stocked > > test lab. > > > > But then, all(yes|mod|no)config aren't intended for actual booting and > > testing - they're > > pretty much build testing all the options in one build. > > > > Basically, one of two things happen after building an all-something-config: > > > > 1) The build completes and you get on with your life > > > > 2) The build fails, and you get to send an email telling the maintainer that > > their driver for the Frobnozz 1300 Widget won't build in =y in kernel > > 4.21-rc2, > > or whatever your build died on. > > I love this answer :) thanks Valdis. If you are taking a walk and feel > like pondering something; any ideas how I could get the most files > possible to show up in /proc and /sys? It all depends on your hardware/system. /sys reflects the devices in the system at the time, physical and virtual. If you create 2 virtual scsi devices, you will have 2 devices in sysfs along with all of their assorted files and directories. People have used virtual devices to stress-test sysfs since the very beginning. Hope this helps, greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
