On 24.03.2007 17:01, Kir Kolyshkin wrote:
Carl-Daniel Hailfinger wrote:
On 23.03.2007 10:01, Kirill Korotaev wrote:
This was possible for years in OpenVZ:
man vzctl
http://openvz.org/documentation/mans/vzctl.8
Network devices control parameters
--netdev_add name
move network
On 23.03.2007 10:01, Kirill Korotaev wrote:
This was possible for years in OpenVZ:
man vzctl
http://openvz.org/documentation/mans/vzctl.8
Network devices control parameters
--netdev_add name
move network device from VE0 to a specified VE
--netdev_del name
delete network device
Carl-Daniel Hailfinger wrote:
On 23.03.2007 10:01, Kirill Korotaev wrote:
This was possible for years in OpenVZ:
man vzctl
http://openvz.org/documentation/mans/vzctl.8
Network devices control parameters
--netdev_add name
move network device from VE0 to a specified VE
--netdev_del name
Carl-Daniel Hailfinger wrote:
On 22.03.2007 16:59, Kirill Korotaev wrote:
Speaking about upstream merges:
there are 2 network virtualization implementations currently exist.
I'm not sure how much time it will take to merge this work,
it is very much depends on netdev@ maintainers. Maybe 2-3
Hi,
I just noticed a new linux-2.6.20 git tree on git.openvz.org. Will
this tree eventually become a supported tree or is it just there as
preparation for an upstream merge?
Speaking of an upstream merge, is there any timeline for merging
network virtualization?
Regards,
Carl-Daniel
On 22.03.2007 16:59, Kirill Korotaev wrote:
Speaking about upstream merges:
there are 2 network virtualization implementations currently exist.
I'm not sure how much time it will take to merge this work,
it is very much depends on netdev@ maintainers. Maybe 2-3 month.
OK, so the target is
