Xen devel - May 2006 - [PATCH][XM-TEST][RESEND][1/4] New Network Infrastructure for Xm-Test

Hi,

I originally sent these patches April 24th:

http://lists.xensource.com/archives/html/xen-devel/2006-04/msg01060.html

These 4 patches add a new network infrastructure to xm-test. The goal is
to make creating network tests easier. This patch makes it possible to
simply create a domain with a single network device in one call:

domain = XmTestNetDomain()

Or, you can use the XmTestDomain() class and add devices:

domain = XmTestDomain()
domain.newDevice(XenNetDevice, "eth0")

Network environment is configured when xm-test is built. The current
patch set only supports a bridged environment with either a defined IP
range or it defaults to using zeroconf addresses. We have plans to
support DHCP as well as NAT and Routed environments. 

The domain will create the device, get an IP, and configure the domain
on startup for you so you don''t need to do that in your tests. 

The first patch adds a domain type to the XenDomain class. The type is
either PV for para-virtual or HVM for a fully virtual domain. The
XenNetDevice needs to know what type of domain it is for configuration.

Thanks,

Dan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, May 03, 2006 at 12:05:36PM -0700, Daniel Stekloff wrote:
> 
> Hi,
> 
> I originally sent these patches April 24th:
> 
> http://lists.xensource.com/archives/html/xen-devel/2006-04/msg01060.html
> 
> These 4 patches add a new network infrastructure to xm-test. The goal is
> to make creating network tests easier. This patch makes it possible to
> simply create a domain with a single network device in one call:
> 
> domain = XmTestNetDomain()
> 
> Or, you can use the XmTestDomain() class and add devices:
> 
> domain = XmTestDomain()
> domain.newDevice(XenNetDevice, "eth0")
> 
> Network environment is configured when xm-test is built. The current
> patch set only supports a bridged environment with either a defined IP
> range or it defaults to using zeroconf addresses. We have plans to
> support DHCP as well as NAT and Routed environments. 
> 
> The domain will create the device, get an IP, and configure the domain
> on startup for you so you don''t need to do that in your tests. 
> 
> The first patch adds a domain type to the XenDomain class. The type is
> either PV for para-virtual or HVM for a fully virtual domain. The
> XenNetDevice needs to know what type of domain it is for configuration.
Sorry Daniel, I didn''t intend to miss these patches first time around. 
I''ve
applied the whole set.  Thanks for your hard work.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel