On May 17, Hugo Cloez wrote:
> I try to dist upgrade an openvz debian 9 container to buster (debian 10)
> version but i have this error during the container start : vzctl:
> relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol
> __libc_readline_unlocked, version GLIBC_PRIVATE not def
On Jul 20, Narcis Garcia wrote:
> In a Debian 9 installed with all defaults, if you change Systemd by
> SystemV, you loose most of desktop software.
Looks like you forgot to install systemd-shim then.
--
ciao,
Marco
signature.asc
Description: PGP signature
On Jul 19, Alexey Zilber wrote:
>Just came across this, which you may find interesting. Removing systemd
> took Devuan two years.
> http://troubleshooters.com/linux/systemd/bikebrakes.htm
Can you people obsessed by systemd please drop this advocacy/bullshit?
Debian 9 works fine with sysvinit
On Nov 07, CoolCold wrote:
> I guess this task https://bugs.openvz.org/browse/OVZ-6232 should be
> closed as WONTFIX as Sergey wrote:
> "we are not interested in systemd support in 2.6.32 kernel, because
> our experience shows that use of outdated kernel together with more
> modern distributions
On May 10, Pavel Odintsov wrote:
> Unfortunately, we can't run OpenVZ 2/6/32 kernel on top of systemd
> aware system because it lacks kdbus subsystem. But if you changed init
All upstream kernels lack kdbus, and systemd does not depend on it.
--
ciao,
Marco
_
On Oct 24, CoolCold wrote:
> 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.
Deb
On Feb 25, Joseph Hauptmann wrote:
> I agree and thus edited the wiki-article to reflect just that.
> Maybe it's time to also put out a warning, discouraging people from
> using Ubuntu as a platform as there are a few hackish things required
> (rsyslog, dm-mod) in order to get it running?
I can't
On Feb 25, Joseph Hauptmann wrote:
> unfortunately that does not seem to be true for Ubuntu 10.04 as the
> version of libcgroup1 available is 0.34 whereas vzctl apparently needs
> at least version 0.35:
I strongly advise against installing libraries converted by alien.
If you need more recent use
On Jan 18, Dietmar Maurer wrote:
> What else is required for udev?
Major sysfs changes which I do not think can be backported.
--
ciao,
Marco
___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users
On Jan 17, Dietmar Maurer wrote:
> Wow, that is very bad news - I guess there will be a major blocker for
> debian squeeze. What is the suggested workaround for people using older
> kernels?
You lose, there is no workaround.
This is relevant for all distributions.
--
ciao,
Marco
__
On Jan 16, Dietmar Maurer wrote:
> > Not at all until the new RHEL will be released, because modern versions
> > of udev (like the one in Debian testing/unstable) do not support 2.6.18
> > kernels.
> Really, do you have more information on that?
The current version of udev requires a kernel >= 2.
On Jan 16, Scott Dowdle wrote:
> I'm very glad to hear that. Would you recommend that a stock Debian user use
> your kernel for OpenVZ stuff? If so, I have to wonder how well it would work
> on the upcoming distro releases that Suno was talking about.
Not at all until the new RHEL will be re
On Oct 02, "Dmitry E. Oboukhov" wrote:
> I tried use vzctl --netdev_add ppp1
> - ppp1 is mounted pppoe connection
You should use a veth instead, bridge it to eth0 and run the pppoe
daemon in the VE. But I don't know if pppoe properly works in VEs, if
the standard pppd plugin will not work you m
On Jul 29, "Jonathan R. Dundas" wrote:
> Not even the bottom part labelled 'Read-only bind mounts' ?
No. The bind mount I do on /var/lib/vz/private/10001/ is read only,
but /var/lib/vz/root/10001/ is not.
--
ciao,
Marco
___
Users mailing list
Users@op
On Jul 29, Lorenzo Quatrini wrote:
> > How can I mount read-only the root file system of a VE?
> Did you try this?:
>
> http://wiki.openvz.org/Bind_mounts
Yes, it's not relevant. I need the whole root file system to be read
only.
--
ciao,
Marco
___
How can I mount read-only the root file system of a VE?
My VE_PRIVATE is created as a bind mount of / and is actually read-only,
but when it appears in VE_ROOT as simfs it becomes read-write and I have
found no way to change this.
Is this possible at all?
Linux vztest.bofh.it 2.6.26-2-openvz-amd64
How can I mount read-only the root file system of a VE?
My VE_PRIVATE is created as a bind mount of / and is actually read-only,
but when it appears in VE_ROOT as simfs it becomes read-write and I have
found no way to change this.
Is this possible at all?
Linux vztest.bofh.it 2.6.26-2-openvz-amd64
How can I mount read-only the root file system of a VE?
My VE_PRIVATE is created as a bind mount of / and is actually read-only,
but when it appears in VE_ROOT as simfs it becomes read-write and I have
found no way to change this.
Is this possible at all?
Linux vztest.bofh.it 2.6.26-2-openvz-amd64
Can somebody explain the exact roles of setluid() and of the
VZCTL_ENV_CREATE ioctl or point me to documentation?
I am trying to write a replacement of "vzctl enter", but my ultimate
goal is to write a PAM module which can be used by cron/ssh/etc running
in the HN to switch to the VE context. The
Can somebody explain the exact roles of setluid() and of the
VZCTL_ENV_CREATE ioctl or point me to documentation?
I am trying to write a replacement of "vzctl enter", but my ultimate
goal is to write a PAM module which can be used by cron/ssh/etc running
in the HN to switch to the VE context. The
Can somebody explain the exact roles of setluid() and of the
VZCTL_ENV_CREATE ioctl or point me to documentation?
I am trying to write a replacement of "vzctl enter", but my ultimate
goal is to write a PAM module which can be used by cron/ssh/etc running
in the HN to switch to the VE context. The
21 matches
Mail list logo
