public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
	kdevops@lists.linux.dev
Subject: Re: [RFT] bootlinux: add bisection support
Date: Thu, 24 Apr 2025 10:12:06 -0700	[thread overview]
Message-ID: <aApw5lWu4FS4FLaP@bombadil.infradead.org> (raw)
In-Reply-To: <aApv-TVqIxhNx3fJ@bombadil.infradead.org>

On Thu, Apr 24, 2025 at 10:08:09AM -0700, Luis Chamberlain wrote:
> On Thu, Apr 24, 2025 at 08:40:52AM +0200, Daniel Gomez wrote:
> > If make linux-deploy installs a "bad" ref kernel with a boot problem, the VM
> > will always boot into the "bad" kernel. How is the script going to boot the new
> > kernel for testing if the new ref is "bad"/"good"?
> 
> Good point.
> 
> On the guest:
> 
> kdevops@bisect ~ $ awk -F\' '/menuentry / {print $2}'
> /boot/grub/grub.cfg | awk '{print NR-1 " ... " $0}'
> 0 ... Debian GNU/Linux, with Linux 6.15.0-rc3-next-20250423
> 1 ... Debian GNU/Linux, with Linux 6.15.0-rc3-next-20250423 (recovery mode)
> 2 ... Debian GNU/Linux, with Linux 6.15.0-rc3-05015-g2ecdc8872668
> 3 ... Debian GNU/Linux, with Linux 6.15.0-rc3-05015-g2ecdc8872668 (recovery mode)
> 4 ... Debian GNU/Linux, with Linux 6.15.0-rc3-04291-g400331cd3ff4
> 5 ... Debian GNU/Linux, with Linux 6.15.0-rc3-04291-g400331cd3ff4 (recovery mode)
> 6 ... Debian GNU/Linux, with Linux 6.15.0-rc3-02800-g3686e26dd260
> 7 ... Debian GNU/Linux, with Linux 6.15.0-rc3-02800-g3686e26dd260 (recovery mode)
> 8 ... Debian GNU/Linux, with Linux 6.12.22-amd64
> 9 ... Debian GNU/Linux, with Linux 6.12.22-amd64 (recovery mode)
> 10 ... Debian GNU/Linux, with Linux 6.12.20-amd64
> 11 ... Debian GNU/Linux, with Linux 6.12.20-amd64 (recovery mode)
> 12 ... Debian GNU/Linux, with Linux 6.12.19-amd64
> 13 ... Debian GNU/Linux, with Linux 6.12.19-amd64 (recovery mode)
> 14 ... UEFI Firmware Settings
> 
> Right now it fails to boot. On the host:
> 
> GUEST=bisect
> sudo virsh destroy $GUEST
> DISK=$(sudo virsh dumpxml $GUEST | xmllint --xpath "string(//devices/disk[@device='disk']/source/@file)" -)
> 
> virt-customize --format raw -a $DISK --run-command 'grub-set-default 8'
> [   0.0] Examining the guest ...
> [   8.7] Setting a random seed
> [   8.7] Running: grub-set-default 8
> [   8.8] SELinux relabelling
> [   8.8] Finishing off

I forgot to mention here I obviously followed up with

sudo virsh start bisect

> ssh bisect uname -r
> 6.12.22-amd64

  Luis

  reply	other threads:[~2025-04-24 17:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24  0:09 [RFT] bootlinux: add bisection support Luis Chamberlain
2025-04-24  5:47 ` Luis Chamberlain
2025-04-24  6:40   ` Daniel Gomez
2025-04-24  7:25     ` Daniel Gomez
2025-04-24 13:36       ` Daniel Gomez
2025-04-24 17:10         ` Luis Chamberlain
2025-04-24 18:37           ` Daniel Gomez
2025-04-24 17:08     ` Luis Chamberlain
2025-04-24 17:12       ` Luis Chamberlain [this message]
2025-04-24 18:41         ` Daniel Gomez
2025-05-01 22:21         ` Daniel Gomez
2025-05-05 19:25           ` Luis Chamberlain
2025-05-07 10:38             ` Daniel Gomez
2025-05-07 18:52               ` Luis Chamberlain

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=aApw5lWu4FS4FLaP@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@kernel.org \
    --cc=da.gomez@kruces.com \
    --cc=kdevops@lists.linux.dev \
    /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