For these of you affected by software segfaulting after a udev error in
environments where the host kernel doesn't support netlink, you may be
interested at following bug #581527 and testing the attached patch.
--
OpenVZ kernel out of date, karmic requires 2.6.27
This is a long bug repport
For Ubuntu 10.04 OpenVZ templates see:
http://blog.bodhizazen.net/linux/ubuntu-10-04-openvz-templates/
--
OpenVZ kernel out of date, karmic requires 2.6.27
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
@Stéphane Graber: if you are luckiy..
r...@ubuntu104:/# tail /var/log/init.log
starting init logger
init: hwclock main process (20) terminated with status 77
init: ureadahead main process (21) terminated with status 5
init: openvz pre-start process (17) terminated with status 1
libudev:
Karoly, you are running the debian official vz kernel, which should be
2.6.26, right? As far as I know there is the fd_signal stuff, which got
introduced in 2.6.27, I do not know if it's backported to 2.6.26, but I
know it's backported to the latest stable OpenVZ Kernel 2.6.18, you can
use this
@ Raimund
OS or container virtualization is a type of virtualization technique
that serves certain things very well. One can use the available
resources, memory, net, disk, cpu more than with any other techniques.
The footprint of the server is significantly smaller than in any other
case. With
@ Raimund
Thanks for the tip about the 2.6.18 kernel, I'm going to take a look at
it. I guess alternatively one can try the backported 2.6.32 kernel on
Debian as well. I'm sure that one has this feature. I'm going to to give
a try to that one as well.
Anyway, just so I understand when the kernel
Here's a new openvz.conf to put in /etc/init/ to make Lucid work properly in an
OpenVZ environment.
I'm running that in production since today ;)
--
OpenVZ kernel out of date, karmic requires 2.6.27
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a
# OpenVZ - Fix init sequence to have OpenVZ working with upstart
description Fix OpenVZ
start on startup
task
pre-start script
mount -t proc proc /proc|| true
mount -t devpts devpts /dev/pts || true
mount -t sysfs sys /sys || true
mount -t tmpfs
For those interested, there is a python script that can build OpenVZ
templates including the fix made by Stéphane. This script is available
here : http://bazaar.launchpad.net/~ubuntu-openvz-dev/openvz-tools/vz-
utils/annotate/head%3A/scripts/vz-template-creator.py
It can create templates for
Thank you Stéphane Graber
--
OpenVZ kernel out of date, karmic requires 2.6.27
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm running the official debian lenny openvz kernel too and Hardy,
Karmic start fine as guest. Lucid starts too and with the work around
that Stéphane provided the network and file system are OK, but the
system doesn't go into runlevel 2. I know that there's no such thing as
runlevel 2 anymore so
@Karoly: What does your init.log say?
Mine has the following content:
libudev: init: hwclock main process (20) terminated with status 77
init: ureadahead main process (21) terminated with status 5
libudev: udev_monitor_new_from_netlink: error getting socket: Invalid argument
I don't have init.log. How do you tell init to create this log? Where is
this log? /var/log/
--
OpenVZ kernel out of date, karmic requires 2.6.27
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Forcing the rc script start in the hack exec /etc/init.d/rc 2 solves the
problem, but I don't think that this is the right solution. Any other idea?
---
script
start networking
initctl emit filesystem --no-wait
initctl emit local-filesystems --no-wait
initctl emit
The script of Stéphane Graber worked for me comming from ubuntu 9.04
after an upgrade to karmic (9.10) but not for the dist-upgrade to ubuntu
10.04 (lucid)
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade...
this is a serious problem and very easy to reproduce:
on an openvz host try to install one of the ubuntu templates from here:
http://wiki.openvz.org/Download/template/precreated
i tried with ubuntu-9.10-x86.tar.gz and ubuntu-9.04-i386-minimal.tar.gz
when you change the /etc/apt/sources.list to
Hi Stefan,
what kernel are you using? If possible, could you try the latest openvz
2.6.18 kernel, (2.6.18, 028stab068.5 or 028stab068.3, as they are
basically the same).
The point is that in this release the fd_signal function is backported
from the newer kernels (think it was introduced in
On Fri, 2010-03-26 at 10:05 +, Stefan Leitner wrote:
this is a serious problem and very easy to reproduce:
on an openvz host try to install one of the ubuntu templates from here:
http://wiki.openvz.org/Download/template/precreated
i tried with ubuntu-9.10-x86.tar.gz and
@ Raimund Sacherer
I'm running the official debian lenny openvz kernel on the host:
# uname -a
Linux [hostname] 2.6.26-2-openvz-686 #1 SMP Tue Mar 9 18:54:31 UTC 2010 i686
GNU/Linux
@ Stéphane Graber
Thanks! That solved my problem with Ubuntu Lucid!
--
OpenVZ kernel out of date, karmic
I manage to make karmic work with Openvz by using the openvz.conf hack
AND
by removing /etc/network/interface.template file inside VPS
Hope this helps
--
OpenVZ kernel out of date, karmic requires 2.6.27
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are
openvz 2.6.18 is not an old kernel at all, it is the best maintained
*stable* kernel out there, with hundreds of backports fixes, based on
the stable redhat5 kernel.
I had in my beginnings various problems with oopses and panics using 24
and 27 kernels, and all disappeared running 2.6.18.
Heck,
This is weaksauce - the 3 commercially hosted VPSs I just checked were
all running 2.6.18 so it's no wonder karmic (and presumably lucid in a
few months) are not being offered.
I've tried to upgrade 4 times over the last 24 hours and ended in a
thoroughly confusing state which has finally been
FWIW karmic's running on 2.6.26 at ramhost.us
r...@vps8:~# uname -a
Linux vps8.vz17.ramhost.us 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00 UTC
2009 i686 GNU/Linux
r...@vps8:~# cat /proc/self/mountinfo
--
OpenVZ kernel out of date, karmic requires 2.6.27
23 matches
Mail list logo
