Hi, Ian, Sorry for the delay - I'm really confused now.
Yes, the vmlinuz and initrd are loaded off the local machine - but these are the same copies that are in the /boot directory on the Debian guest. I would have thought those were updated when I upgraded Debian. In any case - I looked for an armmp package and found linux-image-3.16.0-4-armmp. I installed that package, copied the vmlinuz-3.16.0-4-armmp and initrd.img-3.16.0-4-armmp files to the host and rest the symlinks. Boot only gave me an empty window. No messages, nothing. I had to force close the machine. According to https://wiki.debian.org/DebianKernel/ARMMP#fnref-ab595c5be7b24964461cfb9d5a876e5f0de4d301, it is unknown whether the armmp kernel supports Versatile Express or not. From my tries, it looks like it does not. Is this by any chance a 64bit port? If so, that would explain the problem because I'm using a 32bit chip. Or is there something else I'm doing wrong here? And it looks like I have the same problem on the hardware. Not good... Thanks, Jerry On 11/12/2016 4:41 PM, Ian Campbell wrote: > On Sat, 2016-11-12 at 16:16 -0500, Jerry Stuckle wrote: >> Ian, >> >> That's interesting, because when I do lsb_release-a returns >> >> No LSB modules are available. >> Distribution ID: Debian >> Description: Debian GNU/Linux 8.6 (jessie) >> Release: 8.6 >> Codename: Jessie >> >> /etc/apt/sources.list entries all point at stable, which should be >> jessie, I think. And the system is up to date. > > This is all userspace stuff, which comes from within the VM file > system, but may not correspond to the kernel you are booting. > > Your earlier qemu command line seems to indicate that you are picking > up a kernel from the _host_ filesystem. It seems very likely that you > have not updated the kernel and initrd on the host or you are somehow > picking up the older kernel. > > Maybe you have tripped over the switch from -vexpress to -armmp kernel > flavour naming -- check that you have the linux-image-armmp installed > and not just the (now out of date) linux-image-vexpress one. Those are > both meta packages which depend on the specific versioned packages. > What does "dpkg -l linux-image-\*" say? > > How are you getting the VM filesystem's /boot into your host's > /export/boot where you are booting it from? That process might need > tweaking to pickup the new kernel? > > Ian. > > >
