gremlin | 4 Jun 2012 11:04
Picon
Favicon

Owl OpenVZ template - strange network configuration

I normally use my own package for init scripts, so... my apologies for
late discovery.

root <at> vzhost01:~ # vzctl create 1000 --ostemplate owl-current-20120508-x86_64 --ipadd 172.31.255.0
--hostname ovz-test.lan
Creating container private area (owl-current-20120508-x86_64)
Performing postcreate actions
Container private area was created

root <at> vzhost01:~ # vzctl start 1000
Starting container ...
Container is mounted
Adding IP address(es): 172.31.255.0
Setting CPU units: 1000
Configure meminfo: 65536
Set hostname: ovz-test.lan
Container start in progress...

root <at> vzhost01:~ # vzctl enter 1000                                              
entered into CT 1000

root <at> ovz-test:/ # ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: gre0: <NOARP> mtu 1476 qdisc noop state DOWN 
    link/gre 0.0.0.0 brd 0.0.0.0
3: ip6tnl0: <NOARP> mtu 1460 qdisc noop state DOWN 
(Continue reading)

Solar Designer | 5 Jun 2012 19:19
Favicon

Re: Error in installworld

On Tue, May 29, 2012 at 03:58:11PM +0400, Malykh Oleg wrote:
> I've tried to install from CD but result the same.

This is not specific.  What exactly did you install from CD?  What did
you try updating it to?

Anyway, a few days ago I tried updating an Owl system installed in 2009
(that is, pre-3.0) to Owl-current (i686).  "make installworld" worked
just fine.  The issue that you reported did not occur.

> I've got one suggestion for install - when I install new Owl my /etc/modules.conf cleared by
installation. Can you keep my version of modules.conf for example as modules.conf.rpmsave?

Thank you for reporting this.  This file will now be preserved (starting
with next Owl-current snapshot).

> I cannot build new kernel. I've used wiki article according how to build own kernel but received error:
> 	  LD      drivers/scsi/built-in.o
> 	  LD      drivers/built-in.o
> 	  GEN     .version
> 	  CHK     include/linux/compile.h
> 	  UPD     include/linux/compile.h
> 	  CC      init/version.o
> 	  LD      init/built-in.o	
> 	  LD      .tmp_vmlinux1
> 	net/built-in.o:(.data+0x7a80): undefined reference to `ipv4_ping_group_range'
> 	net/built-in.o:(.data+0x8060): undefined reference to `ipv4_ping_group_range'
> 	make: *** [.tmp_vmlinux1] Error 1
> May be you know what prevent me to build new kernel

(Continue reading)

Solar Designer | 5 Jun 2012 19:27
Favicon

Re: Owl OpenVZ template - strange network configuration

On Mon, Jun 04, 2012 at 01:04:05PM +0400, gremlin <at> gremlin.ru wrote:
>     inet 127.0.0.1/24 scope host venet0
>     ^^^^^^^^^^^^^^^^^
>     inet 172.31.255.0/32 scope global venet0:0
>                                             ^^
> 
> For me it seems to be an ugly bug...

IIRC, this is vzctl scripts' workaround for some Red Hat distro's
networking startup scripts.  I don't know if our current scripts need
this workaround or not - probably not.  I suggest that we don't waste
time changing this until we've updated to new vzctl.

> And even worse, it looks like
> our init scripts still use /* several kilobytes of curses skipped */
> `ifconfig` instead of `ip` for configuring network devices.

The plan is to get the current/ancient network startup scripts that
we're still using committed directly into our native tree and then to
clean them up.

Alexander

Malykh Oleg | 6 Jun 2012 20:41
Picon

RE: Error in installworld

Dear Alexander,

Thank you for help! Now my kernel have built and I use it perfectly. 
According installworld - it was not critical error because all packets have installed successfully in
spite of this message. 
Thanks a lot!

Oleg Malykh

-----Original Message-----
From: Solar Designer [mailto:solar <at> openwall.com] 
Sent: Tuesday, June 05, 2012 9:19 PM
To: owl-users <at> lists.openwall.com
Subject: Re: [owl-users] Error in installworld

On Tue, May 29, 2012 at 03:58:11PM +0400, Malykh Oleg wrote:
> I've tried to install from CD but result the same.

This is not specific.  What exactly did you install from CD?  What did you try updating it to?

Anyway, a few days ago I tried updating an Owl system installed in 2009 (that is, pre-3.0) to Owl-current
(i686).  "make installworld" worked just fine.  The issue that you reported did not occur.

> I've got one suggestion for install - when I install new Owl my /etc/modules.conf cleared by
installation. Can you keep my version of modules.conf for example as modules.conf.rpmsave?

Thank you for reporting this.  This file will now be preserved (starting with next Owl-current snapshot).

> I cannot build new kernel. I've used wiki article according how to build own kernel but received error:
> 	  LD      drivers/scsi/built-in.o
(Continue reading)

а х | 8 Jun 2012 10:00
Picon

New kernel

Good afternoon!
I`m trying to build new kernel from sources. My is 2.6.18-194.26.1.el5.028stab079.1.owl2 .
I`m using Wiki article:
# xzcat ~/sources/Owl/packages/kernel/patch-308.4.1.el5.028stab100.2-combined.xz | patch -p1 -T
 
As I see it`s last patch? And there isn`t more new one?
 
Anyway I`ve got error when compiling:
 
kernel/sched.c: In function `schedule_vcpu':
kernel/sched.c:860: error: structure has no member named `sched_goidle'
kernel/sched.c: At top level:
kernel/sched.c:5443: warning: `interruptible_sleep_on' is deprecated (declared at kernel/sched.c:5432)
kernel/sched.c:5443: warning: `interruptible_sleep_on' is deprecated (declared at kernel/sched.c:5432)
kernel/sched.c:5477: warning: `sleep_on_timeout' is deprecated (declared at kernel/sched.c:5463)
kernel/sched.c:5477: warning: `sleep_on_timeout' is deprecated (declared at kernel/sched.c:5463)
make[1]: *** [kernel/sched.o] Error 1
make: *** [kernel] Error 2
Can you help me, please with this issue?
Solar Designer | 8 Jun 2012 14:42
Favicon

Re: New kernel

On Fri, Jun 08, 2012 at 12:00:35PM +0400, а х wrote:
> I`m trying to build new kernel from sources.

What is your reason to build from source rather than use our RPMs?
(Building from source is no problem if you prefer.  I am merely asking.)

> ~/sources/Owl/packages/kernel/patch-308.4.1.el5.028stab100.2-combined.xz |
> patch -p1 -T
> 
> As I see it`s last patch? And there isn`t more new one?

This is the version we currently use, yes.  However, please don't forget
that we also apply the Owl patch on top of this.

> Anyway I`ve got error when compiling:

This suggests that you did not apply the Owl patch (from our native
tree).  Please do.  This is mentioned in the instructions on the wiki.

Also, please start with our dot-config-* (the appropriate one) and make
your desired config changes relative to that (keeping most other
settings intact).  (Maybe this is what you were doing already.  I just
thought I'd remind.)

Alexander

а х | 22 Jun 2012 09:27
Picon

Re: New kernel

Thank you, Alexander!
Problem was in case of I did not apply Owl patch. I tried, but have got messages. Thay sayd, that patch already applied. I suposed, that fresh patch is already included in kernel source. But after your post I looked to the version of my native tree. It was old! Than I downloaded fresh one, then applied the Owl patch. And new kernel is working now! My carelessness is guilty...
P.S. I make kernel from sources in case of some non standard options.

2012/6/8 Solar Designer <solar <at> openwall.com>
On Fri, Jun 08, 2012 at 12:00:35PM +0400, а х wrote:
> I`m trying to build new kernel from sources.

What is your reason to build from source rather than use our RPMs?
(Building from source is no problem if you prefer.  I am merely asking.)

> ~/sources/Owl/packages/kernel/patch-308.4.1.el5.028stab100.2-combined.xz |
> patch -p1 -T
>
> As I see it`s last patch? And there isn`t more new one?

This is the version we currently use, yes.  However, please don't forget
that we also apply the Owl patch on top of this.

> Anyway I`ve got error when compiling:

This suggests that you did not apply the Owl patch (from our native
tree).  Please do.  This is mentioned in the instructions on the wiki.

Also, please start with our dot-config-* (the appropriate one) and make
your desired config changes relative to that (keeping most other
settings intact).  (Maybe this is what you were doing already.  I just
thought I'd remind.)

Alexander


Gmane