HP BL680c XenServer Administrator's Guide 4.1.0 - Page 91

VIF commands

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 91 highlights

Command line interface 5.4.19.5. vdi-forget vdi-forget uuid=UUID of VDI Unconditionally removes a VDI record from the database without touching the storage backend. In normal operation, you should be using vdi-destroy instead. 5.4.19.6. vdi-import vdi-import uuid=UUID of VDI filename=filename of raw VDI Import a raw VDI. 5.4.19.7. vdi-introduce vdi-introduce uuid=UUID of VDI sr-uuid=UUID of SR to import into name-label=name of the new VDI type=system | user | suspend | crashdump location=device location (varies by storage type) [name-description=description of VDI ] [sharable=yes | no ] [read-only=yes | no ] [other-config=map to store misc user-specific data ] [xenstore-data=map to of additional Xenstore keys ] [sm-configstorage-specific configuration data ] Create a VDI object representing an existing storage device, without actually modifying or creating any storage. This command is primarily used internally to automatically introduce hot-plugged storage devices. 5.4.19.8. vdi-resize vdi-resize uuid=VDI UUID disk-size=new size for disk Resize the VDI specified by UUID. 5.4.19.9. vdi-snapshot vdi-snapshot uuid=UUID of the VDI [driver-params= ] Produces a read-write version of a VDI that can be used as a reference for backup and/or templating purposes. You can perform a backup from a snapshot rather than installing and running backup software inside the VM. The VM can continue running while external backup software streams the contents of the snapshot to the backup media. Similarly, a snapshot can be used as a "gold image" on which to base a template. A template can be made using any VDIs. The optional driver-params map parameter can be used for passing extra vendor-specific configuration information to the back end storage driver that the VDI is based on. See the storage vendor's driver documentation for details. A clone of a snapshot should always produce a writable VDI. 5.4.19.10. vdi-unlock vdi-unlock uuid=UUID of VDI to unlock [force=true] Attempts to unlock the specified VDIs. If force=true is passed to the command, it will force the unlocking operation. 5.4.20. VIF commands Commands for working with VIFs (Virtual network interfaces). 85

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 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
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
Command line interface
85
5.4.19.5. vdi-forget
vdi-forget
uuid=
UUID of VDI
Unconditionally removes a VDI record from the database without touching the storage backend. In normal
operation, you should be using
vdi-destroy
instead.
5.4.19.6. vdi-import
vdi-import
uuid=
UUID of VDI
filename=
filename of raw VDI
Import a raw VDI.
5.4.19.7. vdi-introduce
vdi-introduce
uuid=
UUID of VDI
sr-uuid=
UUID of SR to import into
name-label=
name of
the new VDI
type=
system | user | suspend | crashdump
location=
device location (varies
by storage type)
[name-description=
description of VDI
] [sharable=
yes | no
] [read-only=
yes
| no
] [other-config=
map to store misc user-specific data
] [xenstore-data=
map to of
additional Xenstore keys
] [sm-config
storage-specific configuration data
]
Create a VDI object representing an existing storage device, without actually modifying or creating any
storage. This command is primarily used internally to automatically introduce hot-plugged storage devices.
5.4.19.8. vdi-resize
vdi-resize
uuid=
VDI UUID
disk-size=
new size for disk
Resize the VDI specified by UUID.
5.4.19.9. vdi-snapshot
vdi-snapshot
uuid=
UUID of the VDI
[driver-params= ]
Produces a read-write version of a VDI that can be used as a reference for backup and/or templating pur-
poses. You can perform a backup from a snapshot rather than installing and running backup software inside
the VM. The VM can continue running while external backup software streams the contents of the snapshot
to the backup media. Similarly, a snapshot can be used as a "gold image" on which to base a template. A
template can be made using any VDIs.
The optional
driver-params
map parameter can be used for passing extra vendor-specific configuration
information to the back end storage driver that the VDI is based on. See the storage vendor's driver docu-
mentation for details.
A clone of a snapshot should always produce a writable VDI.
5.4.19.10. vdi-unlock
vdi-unlock
uuid=
UUID of VDI to unlock
[force=true]
Attempts to unlock the specified VDIs. If
force=true
is passed to the command, it will force the unlocking
operation.
5.4.20. VIF commands
Commands for working with VIFs (Virtual network interfaces).