about grub: To be honest, I usually set explicit kernel name (not id) in /etc/default/grub to be sure what will be loaded.
about sysctl: as I understand, ipv6 module is not loaded within initrd, thats why you get those errors. May be I will do some tests if have some spare time to have look on Wheezy - for now I'm on Squeeze, only one Wheezy box without openvz kernels and it is in production. On Thu, Oct 24, 2013 at 10:42 AM, Johan Wilfer <li...@jttech.se> wrote: > Hi again, > > When we are talking about the new Debian repro this is the thread about my > issues when installing a new HN. (Sent to the list 1,5 weeks ago). > > Any thoughts on these findings? > > I cc Ola and CoolCold as well, hope that's ok. > > /Johan > > 2013-10-14 13:17, Johan Wilfer skrev: > >> Hello again, >> >> I've run my Debian 7 HN for some days now, and it seems to be working >> well. I've some glitches - all are described below. Also are my >> work-arounds described. >> >> Thansk for this new Debian 7 reprository! :-) >> >> -- >> >> When I try to load module xt_tcpudp I get an error. As my iptables-rules >> seems to be working anyway this isn't a big issue for me. This module >> can be loaded with the Debian 3.2-kernel however. >> >> # modprobe xt_tcpudp >> libkmod: ERROR ../libkmod/libkmod.c:505 >> kmod_lookup_alias_from_builtin_file: could not open builtin file >> '/lib/modules/2.6.32-openvz-042stab081.3-amd64/modules.builtin.bin' >> FATAL: Module xt_tcpudp not found. >> >> -- >> >> "df"-utility lists vz-mapped dir, like this: >> >> # df -h >> Filesystem Size Used Avail Use% Mounted on >> udev 10M 0 10M 0% /dev >> tmpfs 786M 612K 785M 1% /run >> /dev/disk/sda1 59G 1.4G 55G 3% / >> tmpfs 5.0M 0 5.0M 0% /run/lock >> tmpfs 1.6G 0 1.6G 0% /run/shm >> /dev/mapper/vg0-vzdata 917G 336G 535G 39% /var/lib/vz >> ( -- cut here? -- ) >> /var/lib/vz/private/221 917G 336G 535G 39% /var/lib/vz/root/221 >> /var/lib/vz/private/222 917G 336G 535G 39% /var/lib/vz/root/222 >> tmpfs 786M 28K 786M 1% /var/lib/vz/root/221/run >> tmpfs 5.0M 0 5.0M 0% >> /var/lib/vz/root/221/run/lock >> tmpfs 1.6G 0 1.6G 0% >> /var/lib/vz/root/221/run/shm >> tmpfs 786M 24K 786M 1% /var/lib/vz/root/222/run >> tmpfs 5.0M 0 5.0M 0% >> /var/lib/vz/root/222/run/lock >> tmpfs 1.6G 0 1.6G 0% >> /var/lib/vz/root/222/run/shm >> >> >> -- >> >> OpenVZ kernel seems to be loading /etc/sysctl.conf before the network on >> boot. The result is that network-params are not applied. This is printed >> on boot: >> >> sysctl: cannot stat /proc/sys/net/ipv6/conf/all/accept_ra: No such file >> or directory >> sysctl: cannot stat /proc/sys/net/ipv6/conf/all/autoconf: No such file >> or directory >> sysctl: cannot stat /proc/sys/net/ipv6/conf/default/accept_ra: No such >> file or directory >> sysctl: cannot stat /proc/sys/net/ipv6/conf/default/autoconf: No such >> file or directory >> . >> . >> >> My quick fix is to run "sysctl -p" in /etc/rc.local as it executes last. >> >> -- >> >> Do you want bugreports at the tracker of these issues? >> (Also, there are two issues in the mail below) >> >> Thanks! >> >> /Johan >> >> >> 2013-10-08 20:25, Johan Wilfer skrev: >>> >>> After installing the kernel the following steps are required: >>> >>> Edit /etc/default/grub and change GRUB_DEFAULT=0 to: >>> GRUB_DEFAULT=2 >>> >>> This is because OpenVZ kernel appear below the normal 3.2-kernel i grub. >>> >>> After that you will have to run: >>> update-grub >>> >>> In Debian Squeeze the openvz-kernel always was inserted above the normal >>> kernels so you didn't have to update grub this way. I also thinking >>> about upgrades - will new kernels apperar below so you'll have to change >>> to GRUB_DEFAULT=4? Maybe these fixes could be imported from the Debian 6 >>> official repro? > > > After upgrading now I see that the new kernel appear above so now I have: > #update-grub > Generating grub.cfg ... > Found linux image: /boot/vmlinuz-3.2.0-4-amd64 > Found initrd image: /boot/initrd.img-3.2.0-4-amd64 > Found linux image: /boot/vmlinuz-2.6.32-openvz-042stab081.5-amd64 > Found initrd image: /boot/initrd.img-2.6.32-openvz-042stab081.5-amd64 > Found linux image: /boot/vmlinuz-2.6.32-openvz-042stab081.3-amd64 > Found initrd image: /boot/initrd.img-2.6.32-openvz-042stab081.3-amd64 > > That means GRUB_DEFAULT=2 doesn't need to be changed to 4 and so on on > "apt-get upgrade". But it still needs to be changed the first time. > > > >>> >>> >>> One more small issue: >>> When I install "linux-headers-2.6.32-openvz-042stab081.3-amd64" I'll >>> have to set KSRC myself to the installed location, like this: >>> >>> export KSRC=/usr/src/linux-headers-2.6.32-openvz-042stab081.3-amd64 >>> >>> If I don't I can't compile kernel-modules (for example DAHDI). >>> This was also done automatically in the Squeeze repro, maybe it could >>> get included in yours as well? >>> >> > -- Best regards, [COOLCOLD-RIPN] _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
