> > Helpful information would be what vm-builder version are you using. > 0.12.4.r444
> I *think* from reading above that either > a.) either your kernel or your software is looking for modules (possibly > in /proc/modules or otherwise looking for kernel features) of the > *running* kernel. Thats not going to work as the running kernel is not > the chroot'd kernel. Will this be always the case if I do: mount -o bind /proc $chroot/proc in my post installation script? > b.) your software is installing before the kernel that has the modules it > needs. If thats the case, either make 2 apt-get install invocations, or > fix your software to depend on the kernel you need so it gets installed > afterward by apt. I'm installing kernel first and then my s/w > >> >> My Question is how can I create VM which is build for using a >> *specified* kernel and not any random one? >> >> Thanks, >> Amol >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~vmbuilder >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~vmbuilder >> More help : https://help.launchpad.net/ListHelp >> >> > _______________________________________________ Mailing list: https://launchpad.net/~vmbuilder Post to : [email protected] Unsubscribe : https://launchpad.net/~vmbuilder More help : https://help.launchpad.net/ListHelp
