On 10.03.2015 21:32, Solar Designer wrote:
> On Tue, Mar 10, 2015 at 02:35:41PM +0100, lst_ho...@kwsoft.de wrote:
>> Zitat von Benjamin Henrion :
>>> Could this be used to gain HN root access from a container:
>>>
>>> http://googleprojectzero.blogspot.be/2015/03/exploiting-dram-rowhammer-bug-to-gai
Hi,
some time ago there was an OpenVZ kernel rpm for openSUSE 10.1 / SLES 10
but I have read in the mail archives that this kernel is no longer
recommended and one should use a 2.6.18-based kernel instead. That's
fine for me (especially because openSUSE 10.2 also uses 2.6.18), but
I can't find an
Hi,
I just noticed a new linux-2.6.20 git tree on git.openvz.org. Will
this tree eventually become a supported tree or is it just there as
preparation for an upstream merge?
Speaking of an upstream merge, is there any timeline for merging
network virtualization?
Regards,
Carl-Daniel
_
On 22.03.2007 16:59, Kirill Korotaev wrote:
> Speaking about upstream merges:
> there are 2 network virtualization implementations currently exist.
> I'm not sure how much time it will take to merge this work,
> it is very much depends on netdev@ maintainers. Maybe 2-3 month.
OK, so the target is
On 23.03.2007 10:01, Kirill Korotaev wrote:
> This was possible for years in OpenVZ:
>
> man vzctl
> http://openvz.org/documentation/mans/vzctl.8
>
> Network devices control parameters
> --netdev_add name
> move network device from VE0 to a specified VE
> --netdev_del name
> delete netwo
On 24.03.2007 17:01, Kir Kolyshkin wrote:
> Carl-Daniel Hailfinger wrote:
>> On 23.03.2007 10:01, Kirill Korotaev wrote:
>>
>>> This was possible for years in OpenVZ:
>>>
>>> man vzctl
>>> http://openvz.org/documentation/mans/vzctl.8
>>
On 10.12.2007 13:07, Kirill Korotaev wrote:
> Thorsten Schifferdecker wrote:
>
>> Hi Kirill
>>
>>
>>
>>> Also please note that this is a development branch kernel, so it can be
>>> not that stable for production use. Our main target now is 2.6.24 kernel
>>> for coming Ubuntu server (TLS).
>
On 12.02.2008 09:46, Kirill Korotaev wrote:
> the only way I'm aware of is /proc/meminfo
> just patch kernel to print something non-zero there always and your
> application most likely will become happy.
>
Why not
mount --bind fakememinfo /proc/meminfo
inside the VE? Would be easiest, but the
Hi,
the ongoing merge of OpenVZ-based lightweight virtualization into
mainline Linux seems to be progressing nicely and I have a few questions
about it:
- How usable will net namespaces be in 2.6.25? I'm especially interested
in assigning a real hardware ethernet device to a VE.
- Will there be an
On 28.05.2008 16:02, [EMAIL PROTECTED] wrote:
>
> title Ovztry
> root (hd0,1)
> kernel /boot/vmlinuz-2.6.16.43-027test002-24.1-ovzpae root=/dev/sda2
> vga=0x31a acpi=off resume=/dev/sda1 showopts
> initrd /boot/initrd-2.6.16.43-027test002-24.1-ovzpae
>
> The bootprocess didn't find t
On 13.03.2008 14:20, Pavel Emelyanov wrote:
> Kir Kolyshkin wrote:
>
>> Pavel,
>>
>> Please correct/enlarge me if there's anything missing/incorrect.
>>
>> Carl-Daniel Hailfinger wrote:
>>
>>> Hi,
>>>
>>> the ongoin
Hi,
are there any plans to support Linux 2.6.31 (or even 2.6.32)?
I heard that quite a few features provided by OpenVZ (containers, net
namespaces) are now in mainline (well, not the original OpenVZ code, but
stuff developed from scratch) and I'd like to know if vzctl can be used
to control these
Hi,
On 09.11.2009 19:03, Thorsten Schifferdecker wrote:
> Carl-Daniel Hailfinger schrieb:
>
>> are there any plans to support Linux 2.6.31 (or even 2.6.32)?
>> I heard that quite a few features provided by OpenVZ (containers, net
>> namespaces) are now in mainline
Hi,
On 22.04.2010 16:36, JR Richardson wrote:
> I had a terrible time migrating containers from one hardware not to
> another. I ran into the ssh bug with the public key not being
> accepted error:
>
> error: RSA_public_decrypt failed: error:0407006A:lib(4):func(112):reason(106)
>
> It was so ran
Hi,
I'm not an OpenVZ developer or heavy user, so my observations may be
irrelevant.
On 06.07.2010 17:33, Brian Moon wrote:
> We have three physical boxes that use OpenVZ. One is the server that
> is home to our developers' environment. Each developer has his own
> container. We have the occasion
On 06.07.2010 20:00, Brian Moon wrote:
>> You probably already know this but it doesn't hurt to mention,
>> 2.6.27.x is not a "stable" OpenVZ kernel branch.
>
> Yes, we upgraded to that in hopes it would solve our problems. It
> seemed to have no affect either way.
Wait a second. uname said 2.6.18
On 06.07.2010 22:28, Brian Moon wrote:
> Bleh, ok, looks like we installed the new sources but did not reboot
> into the new kernel. So, we are still on 2.6.18. Based on this post
> http://community.livejournal.com/openvz/31703.html we should probably
> go ahead and move to .32.
The optimal way fo
17 matches
Mail list logo
