OpenVZ Forum: Support » Dedicating physical NIC ports to each VE without bridging, etc.

Home » General » Support » Dedicating physical NIC ports to each VE without bridging, etc.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Dedicating physical NIC ports to each VE without bridging, etc. [message #15962 is a reply to message #15960]

Fri, 17 August 2007 05:55

den
Messages: 494
Registered: December 2005

Senior Member

Basically, Ethernet device moved inside a VE is a normal Ethernet device visible to a VE. The device should "just work" after the move, i.e. you should assign an address to it and "up" it.

This means that all configuration staff you introduce is not needed. The only thing you need is to say
vzctl set NNN --netdev_add eth2 --save
and appropriately modify network startup scripts inside a VE in a normal way like with the plain Linux.

We do not see any problem if the device will have eth1-eth4 names inside a VE. We believe that this is a normal practice.

Unfortunately, renaming a device inside a VE to eth0 is a bad policy. We should store old device name on interface moving or you'll have a device name conflict on VE stop. So, device renaming interfaces are forbidden inside a VE.

There are some ways to rename an interface inside a VE or before an actual interface moving and we can describe them if you really need them.

Regards,
Den

Report message to a moderator

[Message index]

		Dedicating physical NIC ports to each VE without bridging, etc. By: dranch on Fri, 17 August 2007 02:06
		Re: Dedicating physical NIC ports to each VE without bridging, etc. By: den on Fri, 17 August 2007 05:55
		Re: Dedicating physical NIC ports to each VE without bridging, etc. By: dranch on Fri, 17 August 2007 21:12

Previous Topic:	cman
Next Topic:	Pass environment variable via execve

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Apr 11 21:10:38 GMT 2026

Total time taken to generate the page: 0.60906 seconds