Make xmexaple.vti support network option too and other small
modifications for convenient use by default.
Signed-off-by Zhang xiantao <xiantao.zhang@xxxxxxxxx>
diff -r 1507c5499a92 tools/examples/xmexample.vti
--- a/tools/examples/xmexample.vti Fri Jan 6 18:39:28 2006
+++ b/tools/examples/xmexample.vti Thu Jan 12 12:54:13 2006
@@ -21,7 +21,7 @@
memory = 256
# A name for your domain. All domains must have different names.
-name = "ExampleVMXDomain"
+name = "ExampleVTIDomain"
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
@@ -30,7 +30,11 @@
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
-#vif = [ 'mac=00:16:3e:00:00:11, bridge=xen-br0' ]
+#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ]
+# type=ioemu specify the NIC is an ioemu device not netfront
+vif = [ 'type=ioemu, bridge=xenbr0' ]
+# for multiple NICs in device model, 3 in this example
+#vif = [ 'type=ioemu, bridge=xenbr0', 'type=ioemu', 'type=ioemu']
#-----------------------------------------------------------------------
-----
# Define the disk devices you want the domain to have access to, and
@@ -53,7 +57,7 @@
#=======================================================================
=====
# New stuff
-device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm.debug'
+device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
# Advanced users only. Don't touch if you don't know what you're doing
memmap = '/usr/lib/xen/boot/mem-map.sxp'
Zhang Xiantao
CSD-OTC PRC Virtualization
Intel (China) Limited
add_network_option_in_xmexample.vti.patch
Description: add_network_option_in_xmexample.vti.patch
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home