Re: [Vserver] Re: about Vserver for ARM

[Wenbin Zhang]

Hi Herbert,

Now I merged Vserver code and OpenEZX code, and compile the kernel with
vserver code successfully. However, according to
http://linux-vserver.org/Installation_on_Linux_2.6,
we still need compile util-vserver, which is user land tool for vserver. I
download the util-vserver code, want to cross-compile it with arm-linux-gcc.
But I tried below command:
# ./configure --target=arm-linux --prefix=/

I expect to generate a ARM version Makefile. However, the generated Makefile
is still for x86 gcc version. What's wrong with my process? Any ideas?

Thank you,
Wenbin


On 3/5/07, Wenbin Zhang <[EMAIL PROTECTED]> wrote:


perfect ... I'll send you my postal address
> in a private mail then ...


:-) I will keep you posted on my progress...

> But before I do that, let me try it firstly :-)
>
> sure ...
>
> > Yes I can switch to 2.6, no problems.
>
> in this case, I'd suggest to do so, for several
> reasons, one being the fact that the 2.0/2.2
> branches are much more performant than the 1.2
> branch, another being that the 2.2 patches provide
> a lot more useful features ...


I see, thanks! Now I have switched to 2.6 already.

> However I checked the arm-ezx patch,
> > http://www.openezx.org/download/,
>
> > all the patches are for linux 2.6.16 kernel.
>
> yeah, folks love the 2.6.16 kernel :)
>
> > However, for Vserver patches,
> > http://ftp.linux-vserver.org/pub/kernel/vs2.0/,
>
> > they are only 2.6.12, 2.6.14, 2.6.17 version.
> > So the two kind of patches are not for the same
> > version of 2.6 kernel.
>
> check out this one:
>
> http://people.linux-vserver.org/~dhozac/p/k/patch-2.6.16.37-vs2.0.3-rc1.diff
>
> 



Thanks!

> Moreover, even they are for the same version, for
> > example, 2.6.16 kernel, I guess there are still
> >  conflicts if we apply the two patches simutaneously.
>
> > We have two ways:
> > 1) apply openezx patch, then Vserver patch
> > 2) apply Vserver patch, then openexz patch
> >
> > But we cannot guarantee the two patch have no i
> > conflicts each other, any ideas?
>
> yes, that's called merging, and that is what you
> have to do when you got more than one patch ...
>
> of course, it helps a lot if you know one or even
> better all of the involved patches :)


Yes, I think I need try merge the two patches. So far I still don't know
how difficult it is :-)

Thanks,
Wenbin


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] java socket connections between guests seem to have the host as a source

[Herbert Poetzl]

On Sun, Mar 11, 2007 at 09:58:06PM +, Konstantinos Pachopoulos wrote:
> Hi,
> before reinstalling the host system (the guests have
> remained exactly the same) there was no problem. Now,

reinstall from what to what? 

> if i create a java socket connection from one guest to
> another, the guests believe that the source of the
> connection is the host! Do i need to change something
> in /etc/vservers/guest-name dir? While creating each
> guest i had used the "hostname" parameter however...

what kernel, patch and tool versions?

> Ideas?

could be anything, but if the ip is not assigned to
the guest, it sounds strange, i.e. the guest should
not be able to use it for anything ...

TIA,
Herbert

> ___ 
> All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard 
> protect you. http://uk.docs.yahoo.com/nowyoucan.html
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] Re: java socket connections between guests seem to have the host as a source

[Konstantinos Pachopoulos]

--- Konstantinos Pachopoulos <[EMAIL PROTECTED]>
wrote:

> Hi,
> before reinstalling the host system (the guests have
> remained exactly the same) there was no problem.
> Now,
> if i create a java socket connection from one guest
> to
> another, the guests believe that the source of the
> connection is the host! Do i need to change
> something
> in /etc/vservers/guest-name dir? While creating each
> guest i had used the "hostname" parameter however...
> 
> Ideas?
> 
> 
>   
I fixed it. I had to set the prefix to "24" for each
guest (instead the default "32"), although i think i
had done this during the
creation of each template. I also used the following
iptable entries:
-A PREROUTING -s ! 192.168.0.0/255.255.255.0 -p tcp -m
tcp --dport 2049 -j DNAT --to-destination
192.168.1.12:2049 
-A POSTROUTING -s 192.168.1.0/255.255.255.0 -d !
192.168.1.0/255.255.255.0 -j SNAT --to-source 192.168.1.5



___ 
Inbox full of unwanted email? Get leading protection and 1GB storage with All 
New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] Re: vserver nfs

[Konstantinos Pachopoulos]

--- Konstantinos Pachopoulos <[EMAIL PROTECTED]>
wrote:

> Hi,
> i haven't found a complete "vserver nfs how-to"
> unfortunately... Here is my situation:
> -host is named "vakhos"
> -guest, where nfs is running is called "nfs"
> 
> I had a working vserver system/network, with
> nfs-user-server running, but i re-installed (because
> of damage) the host-system ("vakhos"). That means,
> that neither the clients of my network nor the
> vserver
> guest ("nfs") are causing problems, probably.
> 
> The main thing i cannot remember is how is it
> possible
> to create NAPT entries if mountd is constantly
> changing port...
> 
> Here is some output:
> 
> vakhos:~# rpcinfo -p  
>program vers proto   port
> 102   tcp111  portmapper
> 102   udp111  portmapper
> 
> 
> nfs:/# rpcinfo -p nfs
>program vers proto   port
> 102   tcp111  portmapper
> 102   udp111  portmapper
> 132   udp   2049  nfs
> 132   tcp   2049  nfs
> 151   udp923  mountd
> 152   udp923  mountd
> 151   tcp926  mountd
> 152   tcp926  mountd
> 
> 
> vakhos:~# cat /var/lib/iptables/active 
> :PREROUTING ACCEPT [3:536]
> :POSTROUTING ACCEPT [3:220]
> :OUTPUT ACCEPT [3:220]
> ...
> -A POSTROUTING -d 192.168.1.0/24 -j SNAT --to-source
> 192.168.1.5
> -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp
> --dport 111 -j DNAT --to-destination
> 192.168.1.12:111 
> -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp
> --dport 111 -j DNAT --to-destination
> 192.168.1.12:111 
> -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp
> --dport 745 -j DNAT --to-destination
> 192.168.1.12:745 
> -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp
> --dport 745 -j DNAT --to-destination
> 192.168.1.12:745 
> -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp
> --dport 747 -j DNAT --to-destination
> 192.168.1.12:747 
> -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp
> --dport 747 -j DNAT --to-destination
> 192.168.1.12:747 
> -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp
> --dport 2049 -j DNAT --to-destination
> 192.168.1.12:2049
> -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp
> --dport 2049 -j DNAT --to-destination
> 192.168.1.12:2049
> #-A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp
> --dport 981 -j DNAT --to-destination
> 192.168.1.12:981
> #-A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp
> --dport 981 -j DNAT --to-destination
> 192.168.1.12:981
> #-A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp
> --dport 984 -j DNAT --to-destination
> 192.168.1.12:984
> #-A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp
> --dport 984 -j DNAT --to-destination
> 192.168.1.12:984
> ...
> COMMIT
> 
> 
> Even another vserver-guest (not a PC outside the
> vserver-network) cannot mount nfs dirs:
> 
> home:/home/kostas# showmount -e
> mount clntudp_create: RPC: Program not registered
> home:/home/kostas# mount -a
> mount: pimp:/shared failed, reason given by server:
> Permission denied
> 
> 
> Can somebody help please? If more info is needed i
> will post them...
> 
> 
I fixed it. I had to set the prefix to "24" for each
guest, although i think i had done this during the
creation of each template. I also used the following
iptable entries:
-A PREROUTING -s ! 192.168.0.0/255.255.255.0 -p tcp -m
tcp --dport 2049 -j DNAT --to-destination
192.168.1.12:2049 
-A POSTROUTING -s 192.168.1.0/255.255.255.0 -d !
192.168.1.0/255.255.255.0 -j SNAT --to-source 192.168.1.5



___ 
What kind of emailer are you? Find out today - get a free analysis of your 
email personality. Take the quiz at the Yahoo! Mail Championship. 
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk 
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] More info

[[EMAIL PROTECTED]]

RE

More info i forgot to give yesterday :



Options in .config for linux-2.6.20.2-vs2.2.0-rc16
#
# Linux VServer
#
# CONFIG_VSERVER_LEGACY is not set
# CONFIG_VSERVER_LEGACYNET is not set
# CONFIG_VSERVER_REMAP_SADDR is not set
CONFIG_VSERVER_COWBL=y
# CONFIG_VSERVER_VTIME is not set
CONFIG_VSERVER_PROC_SECURE=y
# CONFIG_VSERVER_HARDCPU is not set
# CONFIG_TAGGING_NONE is not set
# CONFIG_TAGGING_UID16 is not set
# CONFIG_TAGGING_GID16 is not set
CONFIG_TAGGING_ID24=y
# CONFIG_TAGGING_INTERN is not set
# CONFIG_TAG_NFSD is not set
# CONFIG_PROPAGATE is not set
CONFIG_VSERVER_PRIVACY=y
CONFIG_VSERVER_WARN=y
# CONFIG_VSERVER_DEBUG is not set
CONFIG_VSERVER=y
CONFIG_VSERVER_NGNET=y



srvweb:~# vserver-info
Versions:
   Kernel: 2.6.20-vs2.3.0.9
   VS-API: 0x00020200
 util-vserver: 0.30.212; Dec  9 2006, 18:32:13

Features:
   CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
  CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13)
 CPPFLAGS: ''
   CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W'
 CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W 
-fmessage-length=0'

   build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
 Use dietlibc: yes
   Build C++ programs: yes
   Build C99 programs: yes
   Available APIs: compat,v11,fscompat,v13,net,v21,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
  vserver(2) syscall#: 273/glibc

Paths:
   prefix: /usr/local
sysconf-Directory: ${prefix}/etc
cfg-Directory: ${prefix}/etc/vservers
 initrd-Directory: $(sysconfdir)/init.d
   pkgstate-Directory: ${prefix}/var/run/vservers
  vserver-Rootdir: /opt/vservers


Assumed 'SYSINFO' as no other option given; try '--help' for more 
information.

srvweb:~#

The problem occurs suddenly as i just enter in a vserver. I just type :

#vserver vweb1 enter
then

vweb1#ps ax

and it hangs with the error message in my first post. Then i loose 
keyboard and network link and i had to reboot hard (trying unsuccess 
syskeyreq).


Patrick





___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver