Xen devel - Nov 2005 - [PATCH] fix vif configuration issue for vmx guest

This patch use same expression as vif for vmx guest but has a distinguish
"type=ioemu"
just like block device.
e.g. vif=[''type=ioemu, mac=01:00:00:00:00:33, bridge=xenbr0'']
type=ioemu to specify for vmx NIC device.
nics=4 can specify 4 vmx NIC now.
bridge is passed to device model now.
With this patch, the error
"Error: Device 0 (vif) could not be connected."
will not happen for creating vmx guest
currently, it happens on some linux distribution.

Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>


 examples/xmexample.vmx          |    6 +++++-
 ioemu/target-i386-dm/qemu-ifup  |    2 +-
 ioemu/vl.c                      |   10 +++++++++-
 python/xen/xend/image.py        |   11 +++++++++++
 python/xen/xend/server/netif.py |    3 +++
 python/xen/xm/create.py         |   15 ++++++++-------
 6 files changed, 37 insertions(+), 10 deletions(-)










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

On Thu, Nov 10, 2005 at 10:14:25PM +0800, Ling, Xiaofeng wrote:
> This patch use same expression as vif for vmx guest but has a distinguish
"type=ioemu"
> just like block device.
> e.g. vif=[''type=ioemu, mac=01:00:00:00:00:33,
bridge=xenbr0'']
> type=ioemu to specify for vmx NIC device.
> nics=4 can specify 4 vmx NIC now.
> bridge is passed to device model now.
> With this patch, the error
> "Error: Device 0 (vif) could not be connected."
> will not happen for creating vmx guest
> currently, it happens on some linux distribution.
> 
> Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>
Applied, thank you.

Ewan.

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