| venet vs veth [message #8156] |
Thu, 09 November 2006 16:23  |
preeve
Messages: 1
Registered: November 2006
|
Junior Member |
|
|
In my environment I need to use veth devices rather than venet, hence it seemed sensible to eliminate venet entirely and I now have a working server cluster which is solely veth based. Hooray!
Unfortunately, replacing venet means I have now lost the ability to use vzlist (and maybe other things yet to be explored). In short, the venet device driver seem to be functionally overloaded (i.e. it does more than just provide a virtual network interface), or maybe the veth device is impoverished...
Whatever, does anyone know if there is a way of recovering the management features for veth based configurations without the (at least conceptual) bloat of redundant venet interfaces?
|
|
|
|
| Re: venet vs veth [message #8192 is a reply to message #8156] |
Fri, 10 November 2006 06:32  |
Vasily Tarasov
Messages: 1345
Registered: January 2006
|
Senior Member |
|
|
Hello,
I guess, I don't quite undestand you, so correct me, if I'm wrong.
You want to use only veth devices. In this case you don't need any venet devices at all. What do you mean under "management features"? Only vzlist?
In this case you can simply enough write a script that will parse vzlist output and do something like "vzctl exec <veid> ifconfig" to get information about VEs...
Does it suit you?
Thanks,
Vasily.
[Updated on: Fri, 10 November 2006 12:07] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
