tap:aio:/path_to_the_file_image: The file image is
exported as a tap device that can be accessed by the Xen
blktap driver. This is specified as the suggested way in the
Xen documentation for exporting file images to the
guest domain.
phy:device:/name_of_the_device: The specified physical
device is exported to the guest domain. The device can be
specified in the usual /dev/sda1 form or using the hex
major/minor number for the device??”0x301.
??? ???
???
??? ??? ???
?°
?°
?°
Chapter 4
[ 55 ]
The "frontend device" specifies how the exported backend device should
appear to the guest domain. This can be specified in the usual /dev/sda1
form or using the hex major/minor number for the device??”0x301.
The "mode" specifies whether the device is to be exported as read-only or
read-write. The two valid options are:
r??”read-only
rw??”read and write.
vif: Specifies the virtual network interface configuration for the domain. This
is provided in the following format:
vif = [ "key1 = value1", "key2 = value2" ]
The common options used for this configuration directive are:
bridge: Specifies the network bridge that will be used for
this interface.
mac: Specifies the MAC address for this virtual interface. If
you do not provide a MAC address, it is set to a random MAC
address by Xen on boot. The random address is selected from
the range of addresses assigned to Xensource by IEEE in the
XenSource Organizationally Unique Identifier (OUI) range
00-16-3E.
Pages:
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65