On Mon, Jan 21, 2008 at 11:52:36AM +, Richard W.M. Jones wrote:
> Daniel P. Berrange wrote:
> >The openvz_driver.c file registers an implementation of the networking
> >driver APIs, which is a no-op.
> >
> >Even though the networking APIs are implemented in the QEMU driver, this
> >one impl is
Daniel P. Berrange wrote:
The openvz_driver.c file registers an implementation of the networking
driver APIs, which is a no-op.
Even though the networking APIs are implemented in the QEMU driver, this
one impl is *shared* and used across all virtualization driver backends.
Thus no other driver
On Sat, Jan 19, 2008 at 06:44:19PM +, Daniel P. Berrange wrote:
> The openvz_driver.c file registers an implementation of the networking
> driver APIs, which is a no-op.
>
> Even though the networking APIs are implemented in the QEMU driver, this
> one impl is *shared* and used across all vir
The openvz_driver.c file registers an implementation of the networking
driver APIs, which is a no-op.
Even though the networking APIs are implemented in the QEMU driver, this
one impl is *shared* and used across all virtualization driver backends.
Thus no other driver such as Xen/OpenVZ/etc shoul
