Hey folks,

A colleague has been successfully using the bookworm generic amd64
images for some time with vmware 8.0.2. He's using the emulated SATA
controller there for the rootfs. He has some automation that grabs an
images, converts to ova for vmware and then installs some extra
packages and config with ansible.

This has been working just fine for some time, but has stopped
working recently(ish), with the kernel failing to find init. He's gone
back and checked a few older images to see where things broke:

20240717-1811  works
20240901-1857  works
20241004-1890  works

20241110-1927  fails
20241125-1942  fails
20241201-1948  fails
20250112-1990  fails
20250115-1993  fails
20250210-2019  fails

In case this might be a kernel config change or similar, he's just
done a dist-upgrade from the working 20241004-1890 image and
rebooted. The new kernel came up just fine on that system, reporting
6.1.128-1 via uname.

We're struggling to see what might have changed to break things
here. Could anybody advise please?

-- 
Steve McIntyre, Cambridge, UK.                                st...@einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer

Reply via email to