On Thursday, 21 July 2016 20:04:05 CEST Chen Hanxiao wrote: > > At 2016-07-21 19:52:11, "Pino Toscano" <ptoscano redhat com> wrote: > >On Thursday, 21 July 2016 18:50:52 CEST Chen Hanxiao wrote: > >> > >> At 2016-07-21 18:43:04, "Richard W.M. Jones" <rjones redhat com> wrote: > >> >On Thu, Jul 21, 2016 at 06:36:20PM +0800, Chen Hanxiao wrote: > >> >> the virtio modules in kmods did existed in this machine. > >> >> with -v -v -v, I got: > >> > > >> >Can you attach or pastebin the complete output from this command on > >> >the failing machine please: > >> > > >> >supermin5 --build -f ext2 -v -v -v /usr/lib64/guestfs/supermin.d -o /tmp/appliance.d > >> > > >> > >> Sure. > >> > >> Please check the attachments. > > > >Hm, is the /lib/modules/3.10.0-229.el7.x86_64/modules.dep file correct > >(as in existing and not empty)? If so, what if you run as root > >`depmod -a` and then try again? > > > > Hi, Pino: > > Thanks for your hint. > I think we got the key: > > on the machine fail: > we lack of lines like: > > kernel/drivers/char/hw_random/amd-rng.ko: > kernel/drivers/char/hw_random/via-rng.ko: > kernel/drivers/char/hw_random/virtio-rng.ko: kernel/drivers/virtio/virtio_ring.ko kernel/drivers/virtio/virtio.ko > kernel/drivers/char/hw_random/tpm-rng.ko: > kernel/drivers/char/tpm/tpm_nsc.ko: > kernel/drivers/char/tpm/tpm_atmel.ko: > kernel/drivers/char/tpm/tpm_infineon.ko: > kernel/drivers/char/virtio_console.ko: kernel/drivers/virtio/virtio_ring.ko kernel/drivers/virtio/virtio.ko > ... > > which existed on the machine works fine. > > It works fine now. > > But why we make initrd only depends on modules.dep? supermin copies some needed modules in the initrd, and of course also the dependencies of these modules need to be copied as well. Copying a module without the needed modules for it means it won't even load. -- Pino Toscano
Description: This is a digitally signed message part.