Gregor Mosheh | 2 Dec 18:28 2007

Re: I need info

> I want implement server virtualization but i need to know the hardware 
> requirements to install OpenVZ.
> Hard Disc space, RAM memory, processor speed, etc. so all Operating 
> Systems installed run properly.

I don't think that there are hard requirements. I successfully tested 
OpenVZ with several VPSs on a system with 1 GB of RAM and a 160 GB hard 
drive.

The short version:

a) If your hardware is compatible with the kernel (think Fedora or 
RedHat) then it's compatible with the OpenVZ kernel. The performance is 
not surprising at all: DDR2 RAM is faster than DDR, a Athlon X2 4000+ is 
faster than a Pentium-4, RAID rocks, and so on.

b) Just plan for capacity, and remember that too much is always better
than not enough. An extra GB of RAM, enough disk for the host OS plus 
some to spare, and you'll be A-OK.

--

-- 
Gregor Mosheh / Greg Allensworth
System Administrator, HostGIS cartographic development & hosting services
http://www.HostGIS.com/

"Remember that no one cares if you can back up,
  only if you can restore." - AMANDA
Kirill Korotaev | 3 Dec 09:30 2007
Picon

Re: license daemons and MAC adresses in VEs

Thomas Sattler wrote:
>>>Which MAC addresses are used inside the VE's? The real MAC add-
>>>resses or some virtual addresses?
>>
>>you can grant some ethX device exclusively to VE,
>>in this case it will be real MAC.
>>
>>or you can create veth adapter with whatever MAC you want.
> 
> 
> Is it possible to re-use the real MAC on a virtual adapter,
> or does that (read: "can eventually") cause problems?

if you don't put then real adapter and virtual one in the same bridge -
no conflicts will happen.

Thanks,
Kirill
Dariush Pietrzak | 3 Dec 12:51 2007
Picon

Re: Venet's ips disappearing...

> this can happen if some hotplug/udev event has happened and removed the routes
> in host node. check /var/log/messages for any kind of events like eth link DOWN/UP,
> DHCP lease reacquiring etc.
 I can't find anything like that, BUT I can correllate those events ( ie
direct route entries in route table disappearing ) with network problems,
but this shouldn't be visible to the host ( things like upstream provider
loosing link, snow severely slowing down radio uplink etc ).
 This seems strange, and identical routes created by hand, and not by vz
stay in place. This looks very much like vz is doing this, so this mail is
a broadcast - did anyone else see something like this or something
similiar?

 The funny part is that it happens only on freshly installed dev machine
and not on machines I'm actually using;)

--

-- 
Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
 Total Existance Failure
Kirill Korotaev | 3 Dec 13:57 2007
Picon

Re: Venet's ips disappearing...

Dariush Pietrzak wrote:
>>this can happen if some hotplug/udev event has happened and removed the routes
>>in host node. check /var/log/messages for any kind of events like eth link DOWN/UP,
>>DHCP lease reacquiring etc.
> 
>  I can't find anything like that, BUT I can correllate those events ( ie
> direct route entries in route table disappearing ) with network problems,
> but this shouldn't be visible to the host ( things like upstream provider
> loosing link, snow severely slowing down radio uplink etc ).
>  This seems strange, and identical routes created by hand, and not by vz
> stay in place. This looks very much like vz is doing this, so this mail is
> a broadcast - did anyone else see something like this or something
> similiar?
> 
>  The funny part is that it happens only on freshly installed dev machine
> and not on machines I'm actually using;)

Hm... this is quite interesting...

Does it often happens?
I'm aware only of 2 places where routing can be removed:
1. hotplug, which I mentioned already.
   maybe some other "clever" daemon running on your system?
   RIP/OCFS?
2. OVZ crontab sript which should delete dead routes.
   can you check this one as well?

All I can suggest for debugging is to:
1. replace ip and route commands with a wrapper which logs the exact
   commands and when/who called them.
(Continue reading)

Dariush Pietrzak | 3 Dec 14:12 2007
Picon

Re: Venet's ips disappearing...

> BTW... does your host system uses DHCP or static IP assigned?
 aaah, now that you mention it, this is the only dhcp-configured machine
with openvz I've got around... and today I disabled DHCP server and few
hours later noticed the problem with openvz. 
 This might be it, and it would explaing non-immediate connection with
networking problems. Thanks.
--

-- 
Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
 Total Existance Failure
Kirill Korotaev | 3 Dec 15:47 2007
Picon

Re: Venet's ips disappearing...

Dariush Pietrzak wrote:
>>BTW... does your host system uses DHCP or static IP assigned?
> 
>  aaah, now that you mention it, this is the only dhcp-configured machine
> with openvz I've got around... and today I disabled DHCP server and few
> hours later noticed the problem with openvz. 
>  This might be it, and it would explaing non-immediate connection with
> networking problems. Thanks.

Yep. DHCP client tries to be too smart :/
I've added this KB:
http://wiki.openvz.org/Networking:_disappering_routes_in_HN

Thanks,
Kirill
E Frank Ball III | 3 Dec 19:01 2007

Re: I need info

On Wed, Nov 28, 2007 at 04:50:01PM -0500, Andrés Tello wrote:
 > Hi,
 > 
 > I want implement server virtualization but i need to know the hardware
 > requirements to install OpenVZ.
 > 
 > Hard Disc space, RAM memory, processor speed, etc. so all Operating Systems
 > installed run properly.

It all depends on how many virtual environments you want and want you
want to run in them.  

For a demonstration I setup a laptop running OpenVZ.  It's a 333MHz
Pentium II, 128MB RAM, and a 6 GB hard drive.  I have 3 VEs running.  It
works fine.

--

-- 

   E Frank Ball                efball@...
Kir Kolyshkin | 3 Dec 21:30 2007

Re: Venet's ips disappearing...

Kirill Korotaev wrote:
> Dariush Pietrzak wrote:
>   
>>> BTW... does your host system uses DHCP or static IP assigned?
>>>       
>>  aaah, now that you mention it, this is the only dhcp-configured machine
>> with openvz I've got around... and today I disabled DHCP server and few
>> hours later noticed the problem with openvz. 
>>  This might be it, and it would explaing non-immediate connection with
>> networking problems. Thanks.
>>     
>
> Yep. DHCP client tries to be too smart :/
> I've added this KB:
> http://wiki.openvz.org/Networking:_disappering_routes_in_HN
>   
The proper URL now is http://wiki.openvz.org/Disappearing_routes_in_HN
Aravind Gottipati | 3 Dec 22:15 2007
Picon

Unable to talk to outside networks.

Hi,

We have quite a few private networks and need VEs to talk to them.
The openvz HN has one bonded interface (bond0) and a bunch of virtual
interfaces (bond0.60, bond0.81 etc) on each of these networks (setup
as vlans).  I have a bunch of real servers sitting on the 10.2.81/24
and the 10.2.74/24 subnets.  These servers can talk to each other.
The HN itself has an ip of 10.2.81.92 and can talk to servers in the
10.2.74/24 subnets

I have a VE sitting in the 10.2.81/24 network with an ip of
10.2.81.101.  This server can ping and talk to other servers in the
10.2.81/24 network.  However, it is unable to talk to anything in the
10.2.74/24 network.  With tcpdump, I see the requests go out on the HN
and the responses coming in to the virtual interface (bond0.81) on the
HN.  However, it appears that none of these packets make it back to
the VE.  I have verified the the appropriate sysctl parameters are
setup.  Forwarding in enabled and there are no firewall rules (in
iptables).  I looked at some basic debugging (with help from the irc
chanel) and I see that the FORWARD policy packet count doesn't seem to
go up.

What information should I be looking at to figure this out or what can
I provide to help debug this.

Thank you,

Aravind.
Aravind Gottipati | 3 Dec 22:55 2007
Picon

Re: Unable to talk to outside networks.

On Mon, Dec 03, 2007 at 01:15:56PM -0800, Aravind Gottipati wrote:
> What information should I be looking at to figure this out or what can
> I provide to help debug this.

I should have mentioned the specs on the machines.  The HN is running
rhel5 with the 2.6.18-8.1.15.el5.028stab049.1 kernel.  The VEs are
running rhel5 as well.  The network interfaces in the VE are all venet
devices.

Thank you,

Aravind.

Gmane