could you please tell us previous kernel version, where
NIC worked correctly inside your container?
Thank you,
Vasily Averin
On 07.01.2016 13:49, Johan Wilfer wrote:
Hi!
I upgraded to kernel 2.6.32-openvz-042stab113.11-amd64 on my Debian 7 HN
yesterday. One of the VE's have a physica
Hi!
I upgraded to kernel 2.6.32-openvz-042stab113.11-amd64 on my Debian 7 HN
yesterday. One of the VE's have a physical NIC delegated inside, like this:
NETDEV="eth3"
After reboot, this NIC doesn't work in the VE. After digging around I
noticed this in syslog on the HN:
[ 305.037939] CT:
Den 2015-07-22 15:23, Michael Stauber skrev:
Hi Johan,
I guess containers could be converted, but can the bind mounts be done
without simfs in a simple way as well?
Regardless if you use simfs or ploop, a VPS or a "real" machine: For
things like that I find fuse-sshfs quite useful. With that
Den 2015-07-21 16:48, Scott Dowdle skrev:
Greetings,
- Original Message -
If our users have to choose between no more inode issues or having
direct access to all VPS files and folders from the HN, then ploop
will probably always get the short end of the stick.
Ummm, you can still acce
work for Debian 8 as well. So
this discussion about using an EL6 kernel for this feels kind of moot.
Not to speak of strange edge-cases you can run into then the userland
expects a newer kernel than it got..
--
Johan Wilfer
___
Users mailing list
U
There is a new mainline
kernel release approximately very 3 months and big changes are fairly
common.
TYL,
--
Johan Wilfer
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
10.x-based OpenVZ branch. For more info see:
http://src.openvz.org/
I didn't expect anything really, and your answer clarifies a lot. Thank
you for the update! So to rephrase the question then:
How are the plans for a release of kernel packages to RHEL7?
--
Johan Wilfer
__
org/debian/dists/jessie
Thanks!
--
Johan Wilfer
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
2013-10-24 11:58, Marco d'Itri skrev:
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 ker
Hi again,
When we are talking about the new Debian repro this is the thread about
my issues when installing a new HN. (Sent to the list 1,5 weeks ago).
Any thoughts on these findings?
I cc Ola and CoolCold as well, hope that's ok.
/Johan
2013-10-14 13:17, Johan Wilfer skrev:
Hello
k is that it
needs one more package. This is why you should use dist-upgrade
in these cases. But I guess you already know that.
// Ola
On Wed, Oct 23, 2013 at 10:07 PM, Kir Kolyshkin mailto:k...@openvz.org>> wrote:
On 10/23/2013 11:58 AM, Johan Wilfer wrote:
2013-10-23 18:29, Kir Kolyshkin skrev:
On 10/23/2013 05:30 AM, Johan Wilfer wrote:
Any suggestions?
Unfortunately you have not provided enough information.
What repos are configured? What kernel(s) are installed?
Sorry for that:
/etc/apt/sources.list:
# openvz - stable
deb http
Any suggestions?
/Johan
2013-10-15 21:05, Johan Wilfer skrev:
Hi,
If I try upgrading from the previous kernel (meta-package
linux-image-openvz-amd64) on Debian with the repro at
download.openvz.org/debian I get this:
# apt-get update
# apt-get upgrade
Reading package lists... Done
Hi,
If I try upgrading from the previous kernel (meta-package
linux-image-openvz-amd64) on Debian with the repro at
download.openvz.org/debian I get this:
# apt-get update
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating
reports at the tracker of these issues?
(Also, there are two issues in the mail below)
Thanks!
/Johan
2013-10-08 20:25, Johan Wilfer skrev:
After installing the kernel the following steps are required:
Edit /etc/default/grub and change GRUB_DEFAULT=0 to:
GRUB_DEFAULT=2
This is because OpenV
utomatically in the Squeeze repro, maybe it could
get included in yours as well?
I'll test more tomorrow, but all looks very well now. Thanks again!
--
Johan Wilfer
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
2013-10-08 16:54, Johan Wilfer skrev:
2013-10-06 16:20, Johan Wilfer skrev:
2013-10-04 23:12, Kir Kolyshkin skrev:
On 10/04/2013 01:38 PM, Johan Wilfer wrote:
2013-10-04 20:52, Kir Kolyshkin skrev:
There is a better way now! We have native Debian Wheezy builds
for kernel and tools, available
2013-10-06 16:20, Johan Wilfer skrev:
2013-10-04 23:12, Kir Kolyshkin skrev:
On 10/04/2013 01:38 PM, Johan Wilfer wrote:
2013-10-04 20:52, Kir Kolyshkin skrev:
There is a better way now! We have native Debian Wheezy builds
for kernel and tools, available at http://download.openvz.org/debian
2013-10-04 23:12, Kir Kolyshkin skrev:
On 10/04/2013 01:38 PM, Johan Wilfer wrote:
2013-10-04 20:52, Kir Kolyshkin skrev:
There is a better way now! We have native Debian Wheezy builds
for kernel and tools, available at http://download.openvz.org/debian
(please see that page for more info
2013-10-04 20:52, Kir Kolyshkin skrev:
On 10/04/2013 01:50 AM, Johan Wilfer wrote:
Right now I testing a Debian 7, with a RHEL-kernel:
2.6.32-openvz-042stab081.3-amd64 with vzctl version 4.5.1
I've noticed that when I create a VE with DEVNODES-statement, like this:
DEVNODES="dahdi/
2013-10-04 20:52, Kir Kolyshkin skrev:
On 10/04/2013 01:50 AM, Johan Wilfer wrote:
Hi,
I am evaluating how to migrate my Debian 6 HN's now when support soon
will be dropped for Debian 6 and they also drop official support for
Openvz.
Right now I testing a Debian 7, with a RHEL-kernel:
2
tory.
I can move them myself to /dev/dahdi in the VE, but the reappear in the
/dev-dir after restating the VE.
It seems to be the same with other devices, like /dev/net/* or
/dev/usb/* etc.
Any thoughts?
--
Johan Wilfer
___
Users maili
22 matches
Mail list logo
