direct-io.hg
changeset 8596:985228c22276
Make xmexaple.vti support network option too and other small modifications for convenient use.
Signed-off-by Zhang xiantao <xiantao.zhang@intel.com>
Signed-off-by Zhang xiantao <xiantao.zhang@intel.com>
author | djm@kirby.fc.hp.com |
---|---|
date | Fri Jan 13 10:25:10 2006 -0600 (2006-01-13) |
parents | ec48a5246f76 |
children | 2869bdd16bd4 |
files | tools/examples/xmexample.vti |
line diff
1.1 --- a/tools/examples/xmexample.vti Fri Jan 13 10:24:19 2006 -0600 1.2 +++ b/tools/examples/xmexample.vti Fri Jan 13 10:25:10 2006 -0600 1.3 @@ -21,7 +21,7 @@ builder='vmx' 1.4 memory = 256 1.5 1.6 # A name for your domain. All domains must have different names. 1.7 -name = "ExampleVMXDomain" 1.8 +name = "ExampleVTIDomain" 1.9 1.10 # List of which CPUS this domain is allowed to use, default Xen picks 1.11 #cpus = "" # leave to Xen to pick 1.12 @@ -30,7 +30,11 @@ name = "ExampleVMXDomain" 1.13 1.14 # Optionally define mac and/or bridge for the network interfaces. 1.15 # Random MACs are assigned if not given. 1.16 -#vif = [ 'mac=00:16:3e:00:00:11, bridge=xen-br0' ] 1.17 +#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ] 1.18 +# type=ioemu specify the NIC is an ioemu device not netfront 1.19 +vif = [ 'type=ioemu, bridge=xenbr0' ] 1.20 +# for multiple NICs in device model, 3 in this example 1.21 +#vif = [ 'type=ioemu, bridge=xenbr0', 'type=ioemu', 'type=ioemu'] 1.22 1.23 #---------------------------------------------------------------------------- 1.24 # Define the disk devices you want the domain to have access to, and 1.25 @@ -53,7 +57,7 @@ disk = [ 'file:/var/images/xenia64.img,i 1.26 #============================================================================ 1.27 1.28 # New stuff 1.29 -device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm.debug' 1.30 +device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' 1.31 1.32 # Advanced users only. Don't touch if you don't know what you're doing 1.33 memmap = '/usr/lib/xen/boot/mem-map.sxp'