A fix has been committed to ploop repo:
https://src.openvz.org/projects/OVZL/repos/ploop/commits/d4298fb98245be22ebe9f576e455c7bf9b26
As gcc-7 is still experimental/unreleased, no new ploop release
is currently planned.
On 10/29/2013 10:21 AM, Ola Lundqvist wrote:
severity 728173 important
thanks
Hi Kir
I have a question about ploop and vzctl.
The question is regarding architecture support in the kernel. What
architectures have working ploop and/or vzctl support in the openvz
patched kernel?
Currently we
Pavel,
Please port these things to 2.6.32 if possible.
--
sent from mobile
Ola Lundqvist o...@debian.org wrote:
Hi Kir
Do you know if those patches will appear in the openvz git soon?
// Ola
On Sun, Feb 13, 2011 at 05:27:54PM +, maximilian attems wrote:
On Sun, Feb 13, 2011 at
Ext4 does not work with delayed allocation in this kernel,
this is known mainstream bug.
Can you please try to reproduce it with 'nodelalloc' mount
option set in /etc/fstab?
If you will able to reproduce the bug with 'nodelalloc'
turned on, please report the kernel oops to OpenVZ bug
#1510.
On 09/09/2010 12:33 PM, Christian Hofstaedtler wrote:
Ola,
Do I need to have a kernel with vzevent support for this to test?
Chris, this is correct.
If so then I must wait until such a kernel appears in Debian...
Right. Max Attems informed me yesterday that the kernel will be
.1 the required stuff will be there.
Best regards,
// Ola
On Mon, Aug 30, 2010 at 02:41:12PM +0400, Kir Kolyshkin wrote:
On 08/30/2010 11:57 AM, Ola Lundqvist wrote:
Hi Kir, Christian
Should we simply remove this file? Or should we simply add something
dummy to it?
I do
. Or will it?
What kernel are we talking about? If 2.6.32 than after kernel guys
will suck in
v2.6.32-dobrovolskiy.1 the required stuff will be there.
Best regards,
// Ola
On Mon, Aug 30, 2010 at 02:41:12PM +0400, Kir Kolyshkin wrote:
On 08/30/2010 11:57 AM, Ola Lundqvist wrote:
Hi
On 08/30/2010 11:57 AM, Ola Lundqvist wrote:
Hi Kir, Christian
Should we simply remove this file? Or should we simply add something
dummy to it?
I do not see where do we create this file -- anywhere in vzctl sources.
We create S00vzreboot in rc6.d, this is needed for reboot mark
(/reboot
# VE address:
ip route add 2002:d5ef:d6ab::2/128
Do you mean you run it in VE context? What is the output of
ip route show before and after running this?
# HN address
ip route add 2002:d5ef:d6ab::1/0 dev venet0
vzctl is supposed to add this route itself. Again, can you
please provide the
On 04/03/2010 04:04 PM, Ola Lundqvist wrote:
Hi Christian
On Sat, Apr 03, 2010 at 11:13:38AM +0200, Christian Hofstaedtler wrote:
Hi Ola,
* Ola Lundqvisto...@debian.org [100402 00:49]:
I have never used insserv myself. Can you send me your
S00vzreboot file? I need to determine why
Ignace, thanks for the patch!
Ola, thanks for filing the bug upstream!
(http://bugzilla.openvz.org/1388)
This is now fixed in vzctl git (will be
available in vzctl = 3.0.24) by this commit:
http://git.openvz.org/?p=vzctl;a=commit;h=34d8d8947cf6400312a859ebbb95ba0e3fe29c91
--
To
Hi Ivan, Ola,
Thanks for the suggestion and the patch, makes sense.
Committed to git (with the appropriate change in comment). Will appear
in vzctl-3.0.24.
http://git.openvz.org/?p=vzctl;a=commit;h=4059ec910609421087bb9143d1de8424a81ad4d0
Ola Lundqvist wrote:
Hi Ivan
This would probably
I will backport this fix. I thought I already did that. Thanks!
// Ola
Quoting Kir Kolyshkin k...@openvz.org:
This is caused by newer kernel headers (in this case on a build system
that was used to build this vzctl package), and is fixed in
vzctl-3.0.23. See the following git commit:
http
This is caused by newer kernel headers (in this case on a build system
that was used to build this vzctl package), and is fixed in
vzctl-3.0.23. See the following git commit:
http://git.openvz.org/?p=vzctl;a=commit;h=0d6bfad92c7cb6a193801ce8dac3a0dc64396ca8
So the solution is either to
I have created openvz bug http://bugzilla.openvz.org/show_bug.cgi?id=1037 now.
Ola, thanks!
Looks like we already have a (long standing) bug for this:
http://bugzilla.openvz.org/show_bug.cgi?id=556
I am working to have a proper solution. Possible workarounds are:
1. Not to use DHCP for eth0.
Ola Lundqvist wrote:
Hi Nathan
Nice to hear from you. Yes this looks like a good patch.
Some comments/questions below.
On Mon, Nov 03, 2008 at 05:29:18PM -0600, Nathan Handler wrote:
...
In Ubuntu, we've applied the attached patch to achieve the following:
*
This is a DUP of OpenVZ bug #894 (http://bugzilla.openvz.org/894).
Fixed in GIT (back in June), will be available in vzctl-3.0.23.
Ola Lundqvist wrote:
Hi Viktar
Thank you for the report.
Best regards,
// Ola
On Wed, Sep 17, 2008 at 12:33:13PM +0300, Viktar Vauchkevich wrote:
Package:
Vitaliy Gusev wrote:
Sorry, I didn't understand this notes:
I upgraded from 2.6.25-2 to 2.6.26-1-openvz-686.
After reboot, the nfsd module fails to load with this error message:
nfsd loads without error if I boot the 2.6.26-1-686 kernel instead.
That was loaded and then error occurs?
Igor, can you comment on that?
Ola, runlevel 4 does not have any special meaning in Red Hat. To me this
is just a bug.
Ola Lundqvist wrote:
Hi Kir and others
I have got this bug report for Debian. However I need to know the details
why this is so. I can understand that runlevel 4 have some
. This is a problem on all other platforms than i386. The reason
is that they are automatically built. If the kernel information is wrong
on the build machine it will get this problem.
When is the next release?
Best regards,
// Ola
On Tue, May 27, 2008 at 12:47:50PM +0400, Kir Kolyshkin wrote:
It's just
Hi Peter,
Please see my replies below.
Peter Gervai wrote:
Hello Everyone,
On Thu, Apr 24, 2008 at 1:01 PM, Ola Lundqvist [EMAIL PROTECTED] wrote:
Hi Christian
Thanks for the clarification. I have marked this bugreport as wontfix
because of the vzmigrate issue, and because that this
As for mainstream integration, I can say OpenVZ is committed to merging
containers functionality to mainstream. I have just checked the number
of changesets submitted by OpenVZ and Linux-VServer guys, using
up-to-date Linus' kernel git tree. For the last 365 days (i.e. a year)
there were 818
Alexey, Pavel,
Can you help Ola with 2.6.24-based OpenVZ patch.
Ola,
We did that for Ubuntu 8.04 already... not sure how Ubuntu kernel
differs from Debian.
Ola Lundqvist wrote:
Hi Christian
Thanks for the information. I was not aware that 2.6.18 had been removed.
I'll try to port the
Apparently it was fixed in newer OpenVZ kernel (028stab019, to be
precise). Are you using Debian stable?
test konto wrote:
i keep getting the same messages except i havent rebooted anything
Architecture: amd64
kernel-patch-openvz 028.18.1etch5
linux-source-2.6.18
Joachim,
I see two problems here -- first is vzctl not detecting it is running
inside a VE, and second is crash. First problem is clear, we will fix
it in vzctl.
As for the second one -- can you please be more specific and describe
what does crash means? Is that the deinstallation process that
I'd like to add that OpenVZ kernel also supports ppc (powerpc64) and
sparc64.
Support for other arches is almost trivial to add, given the hardware to
test the stuff.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
This is already fixed in vzctl git, see this commit:
http://git.openvz.org/?p=vzctl;a=commitdiff;h=7870499cbc38d8fcc12be95cd3187b963a158545
Will appear in vzctl-3.0.17
Ola Lundqvist wrote:
Hi
Thanks, I'll change that on next upload.
The interpreter will either be bash (hard) or the function
Dusty Wilson wrote:
Thanks to both of you for working on this, I appreciate it greatly.
PS to the original reporter of Debian bug #415645 -- vzsplit was not
failing, it just printed a (false) warning.
Is the only problem with it a false warning and it is properly giving
the correct output,
I see two distinct problems described in this bug report:
1. simfs not loaded
2. (enhancement) check running kernel config
Both are fixed in vzctl git.
Check for kernel config options:
http://git.openvz.org/?p=vzctl;a=commit;h=8adf5dcc9dda2f621d6df7cec88ad6ab16bb5041
Loading simfs module:
Ola Lundqvist wrote:
Hi Kir
On Fri, Apr 13, 2007 at 06:16:25PM +0400, Kir Kolyshkin wrote:
I see two distinct problems described in this bug report:
1. simfs not loaded
2. (enhancement) check running kernel config
Both are fixed in vzctl git.
Check for kernel config options:
http
, it just printed a (false) warning.
Ola Lundqvist wrote:
Hi Kir
On Fri, Mar 23, 2007 at 05:36:51PM +0300, Kir Kolyshkin wrote:
That's quite easy -- the actual checking routine in vzsplit checks for
both free space and free inodes (and reports the same error when one of
space/inodes is limited
I guess in a week or two, not earlier.
Ola Lundqvist wrote:
Privet Kir
Do you know when vzctl-3.0.17 is planned?
Regards,
// Ola
On Thu, Apr 12, 2007 at 05:43:19PM +0400, Kir Kolyshkin wrote:
Ola, all,
Both problems in vzsplit are now (hopefully) fixed with this commit:
http
That's quite easy -- the actual checking routine in vzsplit checks for
both free space and free inodes (and reports the same error when one of
space/inodes is limited). Now, reiserfs reports zero total inodes
(because it does not use inodes), and vzsplit stumbles on that.
I made a patch to
It looks like you have not enabled CONFIG_VE (perhaps because of enabled
CONFIG_SECURITY).
So the way to solve this is disable CONFIG_SECURITY and then enable
CONFIG_VE.
Konstantin Seiler wrote:
Package: kernel-patch-openvz
Version: 028.18.1
Severity: grave
Justification: renders package
You have to enable CONFIG_VE (otherwise having OpenVZ kernel makes no
sense) and disable CONFIG_SECURITY (conflicts with CONFIG_VE since
OpenVZ has a security model of its own).
leo wrote:
Package: kernel-patch-openvz
Version: 028.18.1
Debian Etch (up to date)
Kernel sources: vanilla 2.6.18
Hi Steve,
See my comments below.
Steve Langasek wrote:
If so I need to be prepared as that will probably break this patch.
Why is this patch so fragile? If it breaks that easily, it hardly seems
releasable -- how do we protect against it being broken by security updates?
I suggest
1. Not debian-specific so better to be filed mainstream (i.e. to
http://bugzilla.openvz.org/)
2. We need exact messages, and perhaps your kernel .config file.
David Baron wrote:
Package: kernel-patch-openvz
Version: 028test007.1
Severity: normal
Near end of shutdown sequence, get a series of
Could we set up some machinery in order to be notified ASAP about the
kernel-patch-openvz rejects?
Ola Lundqvist wrote:
Hi
On Mon, Dec 04, 2006 at 02:40:21PM +0300, Vasily Tarasov wrote:
Hi,
When I was preparing previous patch only 2.6.18-5 was available from
I see. I forgot about
Petter, we could probably provide you an access to an OpenVZ VPS with a
Debian distro installed so you can check the issue exists and is fixable
by the patch. Send me your SSH public key and I will try to arrange it.
Petter Reinholdtsen wrote:
I use version 2.86.ds1-1 in sarge, and do not
Package: sysvinit
Version: 2.86.ds1-1
Tags: patch
SysVinit version 2.86 have a problem in its code that leads to
incorrectly displaying init name in process list (and in
/proc/1/cmdline) -- it is shown as 'ini'. This was observed inside an
OpenVZ's VPS. See http://bugzilla.openvz.org/60 for
40 matches
Mail list logo
