[Users] OpenVZ on Fedora Core 5 (networking question)

Wed Apr 26 03:42:42 EDT 2006

Aleksandr,

can you please apply workaround for FC5 cp problem as described here:
http://forum.openvz.org/index.php?t=tree&th=405&mid=2355&&rev=&reveal=
and recheck the networking.

Thanks,
Kirill

> Hello Kiril,
> 
> just to mention that I've installed the vz*-3.0.0-7 packages and created 
> the vps with them. I couldn't start the yum update process so I tried to 
> get some help on irc. Someone pointed me to the wrong limits which were 
> for x86_64, I've corrected them and since then I was able to start 
> pretty much everything. Since the *-3.0.0-8 packages were released I've 
> updated to them and I used them to write this email.
> 
> regards,
> Aleksandar
> 
> P.S. Don't forget to scroll down :-)
> 
> Kirill Korotaev wrote:
> 
>> Aleksandr,
>>
>> Can you please, provide the following information:
>> 1. kernel version you use:
>> # uname -a
>>
> Linux somehost.somedomain.net 2.6.16-1.2080_FC5.026test007 #1 Mon Apr 3 
> 18:44:34 MSD 2006 i686 i686 i386 GNU/Linux
> 
>> 2. have you started vz service before VPS start?
>> # /etc/init.d/vz restart
>>
> # service vz status
> OpenVZ is running...
> #service vz restart
> Stopping OpenVZ: [OK]
> Starting OpenVZ: [OK]
> Bringing up interface venet0: [OK]
> Configuring interface venet0: net.ipv4.conf.venet0.send_redirects = 0 [OK]
> 
> I've restarted it a lot of times
> 
>> 3. have you enabled ip forwarding?
>> # cat /proc/sys/net/ipv4/ip_forward
>>
> # cat /proc/sys/net/ipv4/ip_forward
> 1
> I actually don't need forwarding for the moment, because I want to be 
> able to ssh to the vps from the hardware node.
> 
>> 4. which template have you used for your VPS?
>> # cat /etc/sysconfig/vz-scripts/101.conf
>>
> The fedora 5 template and I've updated it with yum through internet, I 
> didn't download the tarball.
> === BEGIN 101.conf ===
> VERSION="2"
> 
> ONBOOT="no"
> CLASSID="2"
> 
> # UBC parameters (in form of barrier:limit)
> # Primary parameters
> AVNUMPROC="40:40"
> NUMPROC="65:65"
> NUMTCPSOCK="80:80"
> NUMOTHERSOCK="80:80"
> VMGUARPAGES="6144:2147483647"
> # Secondary parameters
> KMEMSIZE="3578265:3816816"
> TCPSNDBUF="319488:524288"
> TCPRCVBUF="319488:524288"
> OTHERSOCKBUF="132096:336896"
> DGRAMRCVBUF="132096:132096"
> OOMGUARPAGES="6144:2147483647"
> # Auxiliary parameters
> LOCKEDPAGES="32:32"
> SHMPAGES="8192:8192"
> PRIVVMPAGES="22528:24576"
> NUMFILE="1280:1280"
> NUMFLOCK="100:110"
> NUMPTY="16:16"
> NUMSIGINFO="256:256"
> DCACHESIZE="1048576:1097728"
> 
> PHYSPAGES="0:2147483647"
> NUMIPTENT="128:128"
> 
> # Disk quota parameters (in form of softlimit:hardlimit)
> DISKSPACE="1048576:1153434"
> DISKINODES="200000:220000"
> QUOTATIME="0"
> 
> # CPU fair sheduler parameter
> CPUUNITS="1000"
> OFFLINE_MANAGEMENT="yes"
> VE_ROOT="/vz/root/$VEID"
> VE_PRIVATE="/vz/private/$VEID"
> OSTEMPLATE="fedora-core-5-i386-default"
> ORIGIN_SAMPLE="vps.basic"
> HOSTNAME="www.rousse.org"
> IP_ADDRESS="10.0.0.1"
> NAMESERVER="XX.YY.154.19"
> === END 101.conf ===
> 
>> 5. from host and VPS:
>> # ip a l
>> # ip r l
>>
> Host:
> # ip a l
> 2: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>    inet 127.0.0.1/8 scope host lo
>    inet6 ::1/128 scope host
>       valid_lft forever preferred_lft forever
> 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>    link/ether 00:50:bf:d1:f5:84 brd ff:ff:ff:ff:ff:ff
>    inet XX.YY.154.19/27 brd XX.YY.154.31 scope global eth0
>    inet XX.YY.154.28/27 brd XX.YY.154.31 scope global secondary eth0:0
>    inet6 fe80::250:bfff:fed1:f584/64 scope link
>       valid_lft forever preferred_lft forever
> 6: sit0: <NOARP> mtu 1480 qdisc noop
>    link/sit 0.0.0.0 brd 0.0.0.0
> 5: venet0: <BROADCAST,POINTOPOINT,NOARP,UP> mtu 1500 qdisc noqueue
>    link/void
> # ip r l
> XX.YY.154.0/27 dev eth0  proto kernel  scope link  src XX.YY.154.19
> 169.254.0.0/16 dev eth0  scope link
> default via XX.YY.154.1 dev eth0
> 
> Guest:
> # vzctl start 101
> Starting VPS ...
> VPS is mounted
> Adding IP address(es): 10.0.0.1
> /bin/cp: preserving times for `/etc/sysconfig/network.2701': Function 
> not implemented
> ERROR: Can't copy file /etc/sysconfig/network
> Setting CPU units: 1000
> Set hostname: www.rousse.org
> /bin/cp: preserving times for `/etc/hosts.2710': Function not implemented
> ERROR: Can't copy file /etc/hosts
> VPS start in progress...
> # vzctl exec 101 ip a l
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>    inet 127.0.0.1/8 scope host lo
> 3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP> mtu 1500 qdisc noqueue
>    link/void
>    inet 127.0.0.1/32 scope host venet0
> # vzctl exec 101 ip r l
> 191.255.255.0/24 dev venet0  scope host
> 169.254.0.0/16 dev venet0  scope link
> default via 191.255.255.1 dev venet0
> 
>> Thanks,
>> Kirill
>>
>>> Hello,
>>>
>>> after installing and successfully running one OpenVZ VPS I wasn't 
>>> able to ping or ssh to the VPS. After analyzing a little bit I came 
>>> to the following:
>>> 1) host venet0 isn't configured even after   vzctl start 101
>>> 2) venet0 in the guest (vps) is set to 127.0.0.1
>>>
>>> Is this normal ? I've assigned 10.0.0.1 to the VPS and if I manually 
>>> configure host's venet0 to 10.0.0.2 and guest's venet0 to 10.0.0.1 
>>> (through vzctl exec) I'm being able to ping and ssh to the vps.
>>>
>>> Also, could someone point me to some detailed information about the 
>>> OpenVZ networking concept ? Is it like vmware (separate interfaces) ? 
>>> Is it like jail (ethernet aliases) ? The only thing I found about 
>>> networking was "vzctl set XYZ --ipadd A.B.C.D" :)
>>>
>>> thanks,
>>> Aleksandar
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at openvz.org
>>> https://openvz.org/mailman/listinfo/users
>>>
>>
>>
> 
> 