ia64/xen-unstable

view tools/examples/xmexample1 @ 8964:8946b6dcd49e

Fix x86_64 Xen build.

event_callback_cs and failsafe_callback_cs are x86_32 only.

Signed-off-by: Ian Campbell <Ian.Campbell@XenSource.com>
author Ian.Campbell@xensource.com
date Wed Feb 22 17:26:39 2006 +0000 (2006-02-22)
parents 55d464295da3
children bdcc838b9a72
line source
1 # -*- mode: python; -*-
2 #============================================================================
3 # Python configuration setup for 'xm create'.
4 # This script sets the parameters used when a domain is created using 'xm create'.
5 # You use a separate script for each domain you want to create, or
6 # you can set the parameters for the domain on the xm command line.
7 #============================================================================
9 #----------------------------------------------------------------------------
10 # Kernel image file.
11 kernel = "/boot/vmlinuz-2.6.10-xenU"
13 # Optional ramdisk.
14 #ramdisk = "/boot/initrd.gz"
16 # The domain build function. Default is 'linux'.
17 #builder='linux'
19 # Initial memory allocation (in megabytes) for the new domain.
20 memory = 64
22 # A name for your domain. All domains must have different names.
23 name = "ExampleDomain"
25 # List of which CPUS this domain is allowed to use, default Xen picks
26 #cpus = "" # leave to Xen to pick
27 #cpus = "0" # all vcpus run on CPU0
28 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5
30 # Number of Virtual CPUS to use, default is 1
31 #vcpus = 1
33 #----------------------------------------------------------------------------
34 # Define network interfaces.
36 # By default, no network interfaces are configured. You may have one created
37 # with sensible defaults using an empty vif clause:
38 #
39 # vif = [ '' ]
40 #
41 # or optionally override backend, bridge, ip, mac, script, type, or vifname:
42 #
43 # vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ]
44 #
45 # or more than one interface may be configured:
46 #
47 # vif = [ '', 'bridge=xenbr1' ]
49 vif = [ '' ]
51 #----------------------------------------------------------------------------
52 # Define the disk devices you want the domain to have access to, and
53 # what you want them accessible as.
54 # Each disk entry is of the form phy:UNAME,DEV,MODE
55 # where UNAME is the device, DEV is the device name the domain will see,
56 # and MODE is r for read-only, w for read-write.
58 disk = [ 'phy:hda1,hda1,w' ]
60 #----------------------------------------------------------------------------
61 # Define to which TPM instance the user domain should communicate.
62 # The vtpm entry is of the form 'instance=INSTANCE,backend=DOM'
63 # where INSTANCE indicates the instance number of the TPM the VM
64 # should be talking to and DOM provides the domain where the backend
65 # is located.
66 # Note that no two virtual machines should try to connect to the same
67 # TPM instance. The handling of all TPM instances does require
68 # some management effort in so far that VM configration files (and thus
69 # a VM) should be associated with a TPM instance throughout the lifetime
70 # of the VM / VM configuration file. The instance number must be
71 # greater or equal to 1.
72 #vtpm = [ 'instance=1,backend=0' ]
74 #----------------------------------------------------------------------------
75 # Set the kernel command line for the new domain.
76 # You only need to define the IP parameters and hostname if the domain's
77 # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP.
78 # You can use 'extra' to set the runlevel and custom environment
79 # variables used by custom rc scripts (e.g. VMID=, usr= ).
81 # Set if you want dhcp to allocate the IP address.
82 #dhcp="dhcp"
83 # Set netmask.
84 #netmask=
85 # Set default gateway.
86 #gateway=
87 # Set the hostname.
88 #hostname= "vm%d" % vmid
90 # Set root device.
91 root = "/dev/hda1 ro"
93 # Root device for nfs.
94 #root = "/dev/nfs"
95 # The nfs server.
96 #nfs_server = '169.254.1.0'
97 # Root directory on the nfs server.
98 #nfs_root = '/full/path/to/root/directory'
100 # Sets runlevel 4.
101 extra = "4"
103 #----------------------------------------------------------------------------
104 # Configure the behaviour when a domain exits. There are three 'reasons'
105 # for a domain to stop: poweroff, reboot, and crash. For each of these you
106 # may specify:
107 #
108 # "destroy", meaning that the domain is cleaned up as normal;
109 # "restart", meaning that a new domain is started in place of the old
110 # one;
111 # "preserve", meaning that no clean-up is done until the domain is
112 # manually destroyed (using xm destroy, for example); or
113 # "rename-restart", meaning that the old domain is not cleaned up, but is
114 # renamed and a new domain started in its place.
115 #
116 # The default is
117 #
118 # on_poweroff = 'destroy'
119 # on_reboot = 'restart'
120 # on_crash = 'restart'
121 #
122 # For backwards compatibility we also support the deprecated option restart
123 #
124 # restart = 'onreboot' means on_poweroff = 'destroy'
125 # on_reboot = 'restart'
126 # on_crash = 'destroy'
127 #
128 # restart = 'always' means on_poweroff = 'restart'
129 # on_reboot = 'restart'
130 # on_crash = 'restart'
131 #
132 # restart = 'never' means on_poweroff = 'destroy'
133 # on_reboot = 'destroy'
134 # on_crash = 'destroy'
136 #on_poweroff = 'destroy'
137 #on_reboot = 'restart'
138 #on_crash = 'restart'
140 #============================================================================