Package: src:linux
Version: 5.10.24-1~bpo10+1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I installed bluealsa with LDAC sink support according to this instruction:
https://github.com/anonymix007/libldacdec/blob/master/README.md
The actual problem is that playback stops af
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 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 03:41:40PM +0
to OpenVZ bug
#1510.
Upstream bug references:
http://bugzilla.openvz.org/show_bug.cgi?id=1509
http://bugzilla.openvz.org/show_bug.cgi?id=1510
--
Thanks,
Kir.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ger to get this into squeeze so if you have the possibility to
test this soon that would be really great.
Best regards,
// Ola
On Mon, Aug 30, 2010 at 08:55:04AM +0200, Christian Hofstaedtler wrote:
Hi Ola, Kir,
the sysv-rc upgrade today migrated my installation to 'dependenc
On 09/06/2010 11:39 AM, Ola Lundqvist wrote:
Hi Kir
We are talking about 2.6.32.
The "kernel guys" you are referring to, do you mean the Debian kernel guys?
yes
If so, we need to contact them so they take the latest version. They
will not do that automatically as Debian is
On 09/04/2010 02:09 AM, Ola Lundqvist wrote:
Hi Kir
I saw that you had fixed the alternative solution to have it in the
kernel. However that will not be available for Debian. Or will it?
What kernel are we talking about? If 2.6.32 than after kernel guys will
suck in
v2.6.32-dobrovolskiy
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 o
Z releases so it doesn't make much sense to fix something
that is not broken and will be gone in the future.
--kir
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 UNSUBSCRI
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 be
ready corrected in
vzctl (3.0.22-9) unstable; urgency=low
* Correction of capability problem on some platforms. Closes: #482974.
-- Ola Lundqvist Sat, 7 Jun 2008 19:26:21 +0200
Do you have any other idéa?
// Ola
On Thu, Jan 29, 2009 at 08:54:13AM +0100, Ola Lundqvist wrote:
Hi Kir
I
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 upgrade
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:
>>
>> * etc/bash_co
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: v
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 occur
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
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
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 2.6.2
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 tha
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 rem
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
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:
http:
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, or
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
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 li
ch to fix that, I will test it and then it will hit the git.
Ola Lundqvist wrote:
Hi Kir
Do you know the answer of this issue? I have modified vzsplit.c so that
it can check for /var/lib/vz as well as /vz, but it do not seem to help.
Regards,
// Ola
On Thu, Mar 22, 2007 at 10:27:13AM -0700,
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 unusa
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
A
above,
kernel-patch-openvz-028test007.1 applies cleanly on top of
linux-source-2.6.18-2.6.18-7.
Thus the question: are you tracking the -stable tree, and how closely do
you follow it?
Regards,
Kir.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
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
. The kernel team have moved
to 2.6.18.3 according to the changelog in
http://packages.qa.debian.org/l/linux-2.6/news/20061123T193153Z.html
Kir, Kiril or Vasily: Can you help me to get a applyable version of the
kernel patch?
Regards,
// Ola
--
To UNSUBSCRIBE, ema
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 see
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 mo
41 matches
Mail list logo
