On 2020-02-22T16:44:18 +0300 Reco <recovery...@enotuniq.net> wrote: > > And yet it is a case of running a wrong kernel. > You see, buster's kernel currently has version 4.19.0-8, but yours > (4.9.0-9) looks like an outdated stretch one. > And you do have a kernel 4.9, but you don't have the modules for it. > You do have a kernel 4.19 (with the modules), but you do not boot it.
Hm, I see. For this VM, I installed from the (slightly outdated) debian-10.0.0-amd64-xfce-CD-1.iso install media, but I allowed the installer to update from a public network mirror during the install, so I should be running 10.3. I'm curious as to how I even got a stretch kernel. > > Is there some special magic I need to do to get the right kernel > > modules? > > I'd start by fixing a bootloader (GRUB, most probably), because whatever > it boots it's not the kernel that Debian gives you in a buster. This is a Debian guest running on the bhyve[0] hypervisor. These are the grub commands I use to boot the VM: linux (hd0,msdos1)/vmlinuz root=/dev/sda1 init=/sbin/init initrd (hd0,msdos1)/initrd.img boot I believe these are pretty standard and I think they, as a result, just end up delegating to whatever configuration is present in the guest. I haven't touched the default configuration in the guest, so it's not clear to me how or why I would be booting something that's misconfigured (unless there's some installer bug that nobody's caught). These are the kernels I appear to have in the guest filesystem: # ls -alF /boot/ total 67460 drwxr-xr-x 3 root root 4096 Feb 22 11:31 ./ drwxr-xr-x 22 root root 4096 Feb 22 12:18 ../ -rw-r--r-- 1 root root 206212 Jun 19 2019 config-4.19.0-5-amd64 -rw-r--r-- 1 root root 206194 Jan 26 20:01 config-4.19.0-8-amd64 drwxr-xr-x 5 root root 4096 Feb 22 11:32 grub/ -rw-r--r-- 1 root root 25561139 Feb 22 11:12 initrd.img-4.19.0-5-amd64 -rw-r--r-- 1 root root 25807344 Feb 22 11:29 initrd.img-4.19.0-8-amd64 -rw-r--r-- 1 root root 3371003 Jun 19 2019 System.map-4.19.0-5-amd64 -rw-r--r-- 1 root root 3408461 Jan 26 20:01 System.map-4.19.0-8-amd64 -rw-r--r-- 1 root root 5221616 Jun 19 2019 vmlinuz-4.19.0-5-amd64 -rw-r--r-- 1 root root 5270768 Jan 26 20:01 vmlinuz-4.19.0-8-amd64 Is there some way I can determine if my setup is "wrong" somehow? I'm not sure what I should be looking for. [0] https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html -- Mark Raynsford | http://www.io7m.com
pgpdTd1htODKa.pgp
Description: OpenPGP digital signature
