[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>
  • Date: Thu, 10 Nov 2005 22:14:25 +0800
  • Delivery-date: Thu, 10 Nov 2005 14:14:46 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXmAQ4pnD8kIawERAmWpFRyLnGbAA==
  • Thread-topic: [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@xxxxxxxxx>


 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(-)








Attachment: ioemuvif.patch
Description: ioemuvif.patch

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.