On 29/08/14 01:07 PM, Vagrant Cascadian wrote: > On 2014-08-29 08:56:43 -0700, Robert Mavrinac wrote: >> Are you using chroot images? That I can do. The problem with OpenVZ is >> OS-level virtualization, just the same way it might be for VServer. >> Obviously from the output, I'm running this on a Proxmox server. >> >> root@server:/# ltsp-update-image -c / >> modprobe: ERROR: ../libkmod/libkmod.c:507 >> kmod_lookup_alias_from_builtin_file() could not open builtin file >> '/lib/modules/2.6.32-31-pve/modules.builtin.bin' >> modprobe: FATAL: Module overlayfs not found. >> modprobe: ERROR: ../libkmod/libkmod.c:507 >> kmod_lookup_alias_from_builtin_file() could not open builtin file >> '/lib/modules/2.6.32-31-pve/modules.builtin.bin' >> modprobe: FATAL: Module aufs not found. >> No overlayfs or aufs support detected >> >> If you don't have this problem, I need to look at VServer. > Looks like you need to load the overlayfs or aufs modules. It's not > uncommon for container technologies to disallow loading modules by > default, as that can compromise the security of the host machine. If you > manually load overlayfs or aufs from the host server, it might work. > > live well, > vagrant
Well, I'm not going to rebuild the Proxmox VE kernel to include aufs support. I'm going test this with a Linux-VServer KVM. It looks like I can get that to work, so I may be migrating all of my openvz containers very soon. - Rob ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
