Citrix XenServer Error: SR_BACKEND_FAILURE_65

I’ve been having issues attaching a VDI to a VM from a NetApp snapshot.  Basically a storage level snapshot that happen while the server was live.  I keep getting the error “The attempt to load the VDI failed” via XenCenter when I try and boot the VM.  I would then look at the log file: /var/log/xensource.log.  I would see that the VM was tossing out the error “SR_BACKEND_FAILURE_65” when it tried to boot.

I have been unable to get the VDI to load on any server.  I even contacted Citrix looking for help and they were unable to get the VDI to load as well.  I’ve seen several others on the internet run into this issue without a resolution.   If someone knows of a trick to get these VDIs to load, please leave a comment!

Hope this helps!

Citrix XenServer Error: The SR failed to complete the operation

Yesterday we started to run out of space on one of our storage repositories.  When we tried to move any VDI on that SR via XenCenter, we got the error “The SR failed to complete the operation”.  Which is a pretty generic error, par for xenserver errors.  I even got the same error when trying to do a ‘Rescan’.

I continued to troubleshoot, looking through logs and command outputs.  I finally found something to look into.

Ran the command:
xe sr-param-list uuid=eb943814-a329-5f84-bd42-af1858d56632

Noticed this parameter:
other-config (MRW): dirty: ; auto-scan: false

I looked into this “dirty” param…  It means xenserver isn’t happen with the file names on the SR.   I listed the files on my SR and saw that someone created a manual copy of a VDI called: Copy of f897ebcf-9365-471b-8a30-e81f564c2536.vhd.

I fixed it by:

* Removing file: Copy of f897ebcf-9365-471b-8a30-e81f564c2536.vhd
* Rescanning the SR
* I was then able to move the VDI from one SR to another with out error.

 

Hope this helps with your day:

XenServer Error I Hates

Sometimes I’ll reboot a linux VM and I can see it went all the way down.  The machine is off far as I can tell but never ends up rebooting.  I then try doing a shutdown via XenCenter and I get error message: “VM didn’t acknowledge the need to shut down”.

I get so angry that the error tells me the VM didn’t ACKNOWLEDGE the NEED to shut down, really?? I, the administrator just told this piece of software to shutdown and it’s telling ME that it doesn’t acknowledge my command?  Reminds of an old error message I saw in Windows 95/98, “Windows will manage these settings”.  I think to myself, am I commanding the computer, or does the computer command me?

Pretty much this GIF explains everything I feel about this error.

Citrix XenServer Error: Detaching SR – General backend error

After a power outage we ran into some errors after bring everything back up.  When trying to reconnect a CIFS share on our NetApp filer, we got the following errors.

Jan 3, 2014 10:40:10 AM Error: Repairing SR CIFS ISO library On Netapp - Unable to mount the directory specified in device configuration request
Jan 3, 2014 10:40:54 AM Error: Detaching SR 'CIFS ISO library On Netapp' from 'SOME POOL' - General backend error

At first I thought the issue was Xenserver not bring joined to the Active Directory domain. But I was wrong, the issue was the NetApp wasn’t joined to the AD domain. So make sure everyone is on the domain and you may get rid of these errors. For us, the issue was the time on the NetApp was off by 6 minutes and was causing errors when trying to join AD (time needs to be with in sync within 5 minutes).

Citrix XenServer SR Backend Failure Error Codes

SRInUse

The SR device is currently in use.
16

VDIInUse
The VDI is currently in use.
24

LockErr
The lock or unlock request failed.
37

Unimplemented
The requested method is not supported or implemented.
38

SRNotEmpty
The Storage Repository is not empty.
39

ConfigLUNMissing
The request is missing the LUNid parameter.
87

ConfigSCSIid
The SCSIid parameter is missing or incorrect.
107

ISODconfMissingLocation
‘Location’ parameter must be specified in Device Configuration.
220

ISOMustHaveISOExtension
ISO name must have .iso extension.
221

ISOMountFailure
Could not mount the directory specified in Device Configuration.
222

ISOUnmountFailure
Could not unmount the directory specified in Device Configuration.
223

ISOSharenameFailure
Could not locate the ISO sharename on the target, or the access permissions might be incorrect.
224

ISOLocationStringError
Incorrect Location string format. String must be in the format SERVER:PATH for NFS targets, or \\SERVER\PATH for CIFS targets.
225

ISOLocalPath
Invalid local path
226

InvalidArg
Invalid argument
1

BadCharacter
A bad character was detected in the dconf string.
2

InvalidDev
No such device
19

InvalidSecret
No such secret
20

SRScan
The Storage Repository scan failed.
40

SRLog
The Storage Repository log operation failed.
41

SRExists
The Storage Repository already exists.
42

VDIExists
The VDI already exists.
43

SRNoSpace
There is insufficient space.
44

VDIUnavailable
The VDI is not available.
46

SRUnavailable
The Storage Repository is not available.
47

SRUnknownType
Unknown repository type
48

SRBadXML
Malformed XML string
49

LVMCreate
Logical Volume creation error
50

LVMDelete
Logical Volume deletion error
51

LVMMount
Logical Volume mount or activate error
52

LVMUnMount
Logical Volume unmounts or deactivate error
53

LVMWrite
Logical Volume write error
54

LVMPartCreate
Logical Volume partition creation error
55

LVMPartInUse
Logical Volume partition in use
56

LVMFilesystem
Logical Volume file system creation error
57

LVMMaster
Logical Volume request must come from master.
58

LVMResize
Logical Volume resize failed.
59

LVMSize
Logical Volume invalid size
60

FileSRCreate
File Storage Repository creation error
61

FileSRRmDir
File Storage Repository failed to remove directory.
62

FileSRDelete
File Storage Repository deletion error
63

VDIRemove
Failed to remove VDI.
64

VDILoad
Failed to load VDI.
65

VDIType
Invalid VDI type
66

ISCSIDevice
ISCSI device failed to appear.
67

ISCSILogin
ISCSI login failed, verify CHAP credentials.
68

ISCSILogout
ISCSI logout failed.
69

ISCSIInitiator
Failed to set ISCSI initiator.
70

ISCSIDaemon
Failed to start ISCSI daemon.
71

NFSVersion
Required NFS server version unsupported.
72

NFSMount
NFS mount error
73

NFSUnMount
NFS unmount error
74

NFSAttached
NFS mount point already attached.
75

NFSDelete
Failed to remove NFS mount point.
76

NFSTarget
Unable to detect an NFS service on this target.
108

LVMGroupCreate
Logical Volume group creation failed.
77

VDICreate
VDI Creation failed.
78

VDISize
VDI Invalid size
79

VDIDelete
Failed to mark VDI hidden.
80

VDIClone
Failed to clone VDI.
81

VDISnapshot
Failed to snapshot VDI.
82

ISCSIDiscovery
ISCSI discovery failed.
83

ISCSIIQN
ISCSI target and received IQNs differ.
84

ISCSIDetach
ISCSI detach failed.
85

ISCSIQueryDaemon
Failed to query the ISCSI daemon.
86

NFSCreate
NFS Storage Repository creation error
88

ConfigLUNIDMissing
The request is missing the LUNid parameter.
89

ConfigDeviceMissing
The request is missing the device parameter.
90

ConfigDeviceInvalid
The device is not a valid path.
91

VolNotFound
The volume cannot be found.
92

PVSfailed
PVS failed
93

ConfigLocationMissing
The request is missing the location parameter.
94

ConfigTargetMissing
The request is missing the target parameter.
95

ConfigTargetIQNMissing
The request is missing or has an incorrect target IQN parameter.
96

ConfigISCSIIQNMissing
Unable to retrieve the host configuration ISCSI IQN parameter.
97

ConfigLUNSerialMissing
The request is missing the LUN serial number.
98

LVMOneLUN
Only 1 LUN may be used with shared LVM.
99

LVMNoVolume
Cannot find volume
100

ConfigServerPathMissing
The request is missing the serverpath parameter.
101

ConfigServerMissing
The request is missing the server parameter.
102

ConfigServerPathBad
The serverpath argument is not valid.
103

LVMRefCount
Unable to open the refcount file
104

Rootdev
Root system device, cannot be used for virtual machine storage.
105

InvalidIQN
The IQN provided is an invalid format.
106

SnapshotChainTooLong
The snapshot chain is too long.
109

VDIResize
VDI resize failed.
110

APISession
Failed to initialize XMLRPC connection.
150

APILocalhost
Failed to query Local Control Domain.
151

APIPBDQuery
A failure occurred querying the PBD entries.
152

APIFailure
A failure occurred accessing an API object.
153

NAPPTarget
Netapp Target parameter is missing in Dconf string.
120

NAPPUsername
Netapp Username parameter is missing in Dconf string.
121

NAPPPassword
Netapp Password parameter is missing in Dconf string.
122

NAPPAggregate
Netapp Aggregate parameter is missing in Dconf string.
123

NAPPTargetFailed
Failed to connect to Netapp target.
124

NAPPAuthFailed
Authentication credentials incorrect
125

NAPPInsufficientPriv
Authentication credentials have insufficient access privileges.
126

NAPPFVolNum
Maximum number of flexvols reached on target. Unable to allocate the requested resource.
127

NAPPSnapLimit
Maximum number of Snapshots reached on target Volume. Unable to create the snapshot.
128

NAPPSnapNoMem
Insufficient space, unable to create the snapshot.
129

NAPPUnsupportedVersion
Netapp Target version unsupported
130

NAPPTargetIQN
Unable to retrieve target IQN
131

NAPPNoISCSIService
ISCSI service is not running on the Netapp target.
132

NAPPAsisLicense
Failed to enable A-SIS for the SR. Requires valid license on the filer.
133

NAPPAsisError
The filer does not support A-SIS on this aggregate. The license is valid however on some filers A-SIS is limited to smaller aggregates, for example, FAS3020 max supported aggregate is 1 TB. Refer to filer support documentation for details on the model. You must either disable A-SIS support, or re-configure the aggregate to the maximum supported size.
134

NAPPExclActivate
Failed to acquire an exclusive lock on the LUN.
135

DNSError
Incorrect DNS name, unable to resolve.
140

ISCSITarget
Unable to connect to ISCSI service on target
141

ISCSIPort
Incorrect value for ISCSI port must be a number between 1 and 65535.
142

BadRequest
Failed to parse the request.
143

VDIMissing
VDI could not be found.
144

EQLTarget
Equallogic Target parameter is missing in Dconf string.
160

EQLUsername
Equallogic Username parameter is missing in Dconf string.
161

EQLPassword
Equallogic Password parameter is missing in Dconf string.
162

EQLStoragePool
Equallogic StoragePool parameter is missing in Dconf string.
163

EQLConnectfail
Failed to connect to Equallogic Array; maximum SSH CLI sessions reached
164

EQLInvalidSnapReserve
Invalid snap-reserver-percentage value must be an integer indicating the amount of space as a percentage of the VDI size, to reserve for snapshots.
165

EQLInvalidSnapDepletionKey
Invalid snap-depletion value must be one of ‘delete-oldest’ or ‘volume-offline’.
166

EQLVolOutofSpace
Volume out of space, probably because to insufficient snapshot reserve allocation.
167

EQLSnapshotOfSnapshot
Cannot create Snapshot of a Snapshot VDI, operation unsupported.
168

EQLPermDenied
Failed to connect to Equallogic Array, Permission denied;username/password invalid
169

EQLUnsupportedVersion
Equallogic Target version unsupported.
170

EQLTargetPort
Unable to logon to Array. Check IP settings.
171

EQLInvalidStoragePool
Equallogic StoragePool parameter specified in Dconf string is Invalid.
172

EQLInvalidTargetIP
Equallogic Target parameter specified in Dconf string is Invalid, specify the correct Group IP address.
173

EQLInvalidSNMPResp
Invalid SNMP response received for a command line interface command.
174

EQLInvalidVolMetaData
Volume metadata stored in the ‘Description’ field is invalid. This field contains encoded data and is not user editable.
175

EQLInvalidEOFRecv
Invalid EOF response received for a CLI command.
176

LVMProvisionAttach
Volume Group out of space. The SR is over-provisioned, and out of space. Unable to grow the underlying volume to accommodate the virtual size of the disk
180

MetadataError
Error in Metadata volume operation for SR.
181

EIO
General IO error
200

EGAIN
Currently unavailable, try again
201

SMGeneral
General backend error
202

FistPoint
An active FIST point was reached that causes the process to exit abnormally.
203

CSLGConfigServerMissing
The CSLG server name or IP address is missing.
400

CSLGConfigSSIDMissing
The Storage System ID is missing.
401

CSLGConfigPoolIDMissing
The Storage Pool ID is missing.
402

CSLGProtocolCheck
The GSSI operation to the CSLG server failed.
410

CSLGLoadSR
The Storage Repository loading operation failed.
411

CSLGInvalidProtocol
An invalid storage protocol was specified
412

CSLGXMLParse
Unable to parse XML
413

CSLGProbe
Failed to probe Storage Repository.
414

CSLGSnapClone
Snapshot/Clone failed.
416

CSLGAssign
Storage assignment failed.
417

CSLGUnassign
Storage un-assignment failed.
418

CSLGAllocate
Storage allocation failed.
419

CSLGDeallocate
Storage deallocation failed.
420

CSLGHBAQuery
HBA Query failed.
421

CSLGISCSIInit
IQN/ISCSI initialization failed.
422

CSLGDeviceScan
SCSI device scan failed.
423

CSLGServer
Failed to connect to CSLG.
424

CSLGConfigSVIDMissing
The Storage Node ID is missing.
425

CSLGIntroduce
The VDI failed to be introduced to the database.
426

CSLGNotInstalled
The CSLG software does not seem to be installed.
427

CSLGPoolCreate
Failed to create multiple sub-pools from parent pool.
428

CSLGOldXML
Current XML definition is newer version.
429

MultipathdCommsFailure
Failed to communicate with the multipath daemon.

430

 

CSL_Integrated

Error in storage adapter communication

431

CSLGConfigAdapterMissing

The adapter id is missing or unknown

432

CSLGConfigUsernameMissing

The username is missing

433

CSLGConfigPasswordMissing

The password is missing

434

CSLGInvalidSSID

An invalid storage system ID was specified

435

CSLGSysInfo

Failed to collect storage system information

436

CSLGPoolInfo

Failed to collect storage pool information

437

CSLGPoolDelete

Failed to delete storage pool

438

CSLGLunInfo

Failed to collect storage volume information

439

CSLGLunList

Failed to list storage volume

440

CSLGResizeLun

Failed to resize storage volume

441

CSLGTargetPorts

Failed to list storage target ports

442

CSLGPoolList

Failed to list storage pool

443

TapdiskFailed

The tapdisk failed

444

TapdiskAlreadyRunning

The tapdisk is already running

445

CIFSExtendedCharsNotSupported

XenServer does not support extended characters in CIFS paths, usernames, passwords, and file names.

446

IllegalXMLChar

Illegal XML character.

447

Citrix XenServer 6.1 Internal error: File “xapi_xenops.ml”, line 1788, characters 3-9: Assertion failed

Today I rebooted a xen host, everything came back up as I would expect, and after trying to live migrate VMs back onto the host I got this error message.

Internal error: File "xapi_xenops.ml", line 1788, characters 3-9: Assertion failed

I thought it was something wrong with xencenter, but then tried via command line and got this error:

Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=VDI SOME-UUID already attached RW]

 

The message “The VDI is not available” I’ve seen many times before and I knew what to do.

 

 

Citrix XenServer dom0 host “random” reboot

The other day I started to get paged around 12:10AM because one of our Xenserver hosts decided it was time to reboot. We have high availability (HA) turned on, so all the VMs running on this host were rebooted on other hosts per our HA config. This was good, that means paging will stop once all the servers are running again.

But what was the cause of this reboot? Of course I go straight to the logs and this is what I found in /var/log/kern.log

Nov 15 00:05:59 xenserverhostname kernel: [2461330.653319] nfs: server 10.0.0.11 not responding, timed out

Looks like issues with NFS timing out to my storage backend, which is a NetApp FAS22xx. We’ve never see performance issue with our NetApp ever, but it looks like we have something going on now. I noticed that we had a lot of volumes scheduled to run deduplication jobs starting off at midnight. I spread those out a bit so they weren’t all trying to run at the same time. I also noticed that our HA Xenserver Heartbeat was getting dedup’d as well. I turned that off because the heartbeat only takes up a few MB’s.

I also noticed that this timeout has been logged happen before, but not enough to cause a host to reboot. I believe HA/Xen will reboot the host once it goes over a timeout threshold, and that is why the server rebooted. I think we are dealing with a couple issues and I hate to use the term “perfect storm”, but it seems fitting. I think because there were a lot of NetApp jobs kicking off at midnight, jobs with lots of I/O getting kicked off on VMs at midnight, and issues with XenServer handling timeouts were at play. I think spreading out jobs on the NetApp, on the VMs, and applying patches will help, but only time will tell if it does.

http://support.citrix.com/article/CTX135623

Citrix XenServer 6.1 – XenServer Tools out of date (version 6.0 installed)

Recently we upgraded our XenServer resource pool to 6.1 because the new feature allowing you to do live migration of VDI’s sounds unreal.  I still get amazed that this stuff works, well most of the time.  Now we are having issues with XenTools reporting to be out of date in XenCenter, I see the message:

XenServer Tools out of date (version 6.0 installed)

Great, I’ll just pop the XenTools CD in, uninstall the old version, and install the new version.  Nope, that does not work.  Instead it makes the issues worst, as you try and reboot the system but XenServer never figures out the server is shutdown and you end up having to do vm-reset-powerstate or even destroy the domain.  Either way this sucks.

Citrix just updated it’s XenServer blog yesterday acknowledging the issues with XenTools is real and they will try and fix their processes.  And they are right, this sort of thing really does hurt your confidence in the system.  And we all know virtualization is built on confidence.

Now here is the real place to get all the info on what needs to happen.  It’s a two part update, first you need to apply hot fix XS61E009 and then XS61E010.  Then you have the fun of updating XenTools.  But lots of work non the less when you have 10s, 100s, 1000s of VMs.

http://support.citrix.com/article/CTX135099
http://support.citrix.com/article/CTX136252
http://support.citrix.com/article/CTX136253

*UPDATE*

If you run in to blue screen on Windows while installing the new XenTools from the XS61E010… I know more issues??  If you can get into safe mode to remove xentools from the machine and reinstall, that may work.  Other wise you can try looking yup your VMs UUID and changing the device ID.  This may work if your VM does not get the correct device ID set during the new xentools install. Use this command:

xe vm-param-set uuid=<vm_uuid> platform:device_id=0001

or

xe vm-param-set uuid=<vm_uuid> platform:device_id=0002

SMSTools GSM Equipment and Network Error Codes

At work I’ve got a Nagios server setup to send text messages to my phone on critical notifications.  Lately something has been happening that causes sms notifications to fail.

In smsd.log I find that I get the follow error message:

+CME ERROR: 515 (device busy)

As root I’m able to reset the modem by doing this:
/bin/echo "AT+CFUN=1" > /dev/ttyUSB0
/etc/init.d/smstools restart

GSM Equipment related codes

Error Description
CME ERROR: 0 Phone failure
CME ERROR: 1 No connection to phone
CME ERROR: 2 Phone adapter link reserved
CME ERROR: 3 Operation not allowed
CME ERROR: 4 Operation not supported
CME ERROR: 5 PH_SIM PIN required
CME ERROR: 6 PH_FSIM PIN required
CME ERROR: 7 PH_FSIM PUK required
CME ERROR: 10 SIM not inserted
CME ERROR: 11 SIM PIN required
CME ERROR: 12 SIM PUK required
CME ERROR: 13 SIM failure
CME ERROR: 14 SIM busy
CME ERROR: 15 SIM wrong
CME ERROR: 16 Incorrect password
CME ERROR: 17 SIM PIN2 required
CME ERROR: 18 SIM PUK2 required
CME ERROR: 20 Memory full
CME ERROR: 21 Invalid index
CME ERROR: 22 Not found
CME ERROR: 23 Memory failure
CME ERROR: 24 Text string too long
CME ERROR: 25 Invalid characters in text string
CME ERROR: 26 Dial string too long
CME ERROR: 27 Invalid characters in dial string
CME ERROR: 30 No network service
CME ERROR: 31 Network timeout
CME ERROR: 32 Network not allowed, emergency calls only
CME ERROR: 40 Network personalization PIN required
CME ERROR: 41 Network personalization PUK required
CME ERROR: 42 Network subset personalization PIN required
CME ERROR: 43 Network subset personalization PUK required
CME ERROR: 44 Service provider personalization PIN required
CME ERROR: 45 Service provider personalization PUK required
CME ERROR: 46 Corporate personalization PIN required
CME ERROR: 47 Corporate personalization PUK required
CME ERROR: 48 PH-SIM PUK required
CME ERROR: 100 Unknown error
CME ERROR: 103 Illegal MS
CME ERROR: 106 Illegal ME
CME ERROR: 107 GPRS services not allowed
CME ERROR: 111 PLMN not allowed
CME ERROR: 112 Location area not allowed
CME ERROR: 113 Roaming not allowed in this location area
CME ERROR: 126 Operation temporary not allowed
CME ERROR: 132 Service operation not supported
CME ERROR: 133 Requested service option not subscribed
CME ERROR: 134 Service option temporary out of order
CME ERROR: 148 Unspecified GPRS error
CME ERROR: 149 PDP authentication failure
CME ERROR: 150 Invalid mobile class
CME ERROR: 256 Operation temporarily not allowed
CME ERROR: 257 Call barred
CME ERROR: 258 Phone is busy
CME ERROR: 259 User abort
CME ERROR: 260 Invalid dial string
CME ERROR: 261 SS not executed
CME ERROR: 262 SIM Blocked
CME ERROR: 263 Invalid block
CME ERROR: 772 SIM powered down

GSM Network related codes:

Error Description
CMS ERROR: 1 Unassigned number
CMS ERROR: 8 Operator determined barring
CMS ERROR: 10 Call bared
CMS ERROR: 21 Short message transfer rejected
CMS ERROR: 27 Destination out of service
CMS ERROR: 28 Unindentified subscriber
CMS ERROR: 29 Facility rejected
CMS ERROR: 30 Unknown subscriber
CMS ERROR: 38 Network out of order
CMS ERROR: 41 Temporary failure
CMS ERROR: 42 Congestion
CMS ERROR: 47 Recources unavailable
CMS ERROR: 50 Requested facility not subscribed
CMS ERROR: 69 Requested facility not implemented
CMS ERROR: 81 Invalid short message transfer reference value
CMS ERROR: 95 Invalid message unspecified
CMS ERROR: 96 Invalid mandatory information
CMS ERROR: 97 Message type non existent or not implemented
CMS ERROR: 98 Message not compatible with short message protocol
CMS ERROR: 99 Information element non-existent or not implemente
CMS ERROR: 111 Protocol error, unspecified
CMS ERROR: 127 Internetworking , unspecified
CMS ERROR: 128 Telematic internetworking not supported
CMS ERROR: 129 Short message type 0 not supported
CMS ERROR: 130 Cannot replace short message
CMS ERROR: 143 Unspecified TP-PID error
CMS ERROR: 144 Data code scheme not supported
CMS ERROR: 145 Message class not supported
CMS ERROR: 159 Unspecified TP-DCS error
CMS ERROR: 160 Command cannot be actioned
CMS ERROR: 161 Command unsupported
CMS ERROR: 175 Unspecified TP-Command error
CMS ERROR: 176 TPDU not supported
CMS ERROR: 192 SC busy
CMS ERROR: 193 No SC subscription
CMS ERROR: 194 SC System failure
CMS ERROR: 195 Invalid SME address
CMS ERROR: 196 Destination SME barred
CMS ERROR: 197 SM Rejected-Duplicate SM
CMS ERROR: 198 TP-VPF not supported
CMS ERROR: 199 TP-VP not supported
CMS ERROR: 208 D0 SIM SMS Storage full
CMS ERROR: 209 No SMS Storage capability in SIM
CMS ERROR: 210 Error in MS
CMS ERROR: 211 Memory capacity exceeded
CMS ERROR: 212 Sim application toolkit busy
CMS ERROR: 213 SIM data download error
CMS ERROR: 255 Unspecified error cause
CMS ERROR: 300 ME Failure
CMS ERROR: 301 SMS service of ME reserved
CMS ERROR: 302 Operation not allowed
CMS ERROR: 303 Operation not supported
CMS ERROR: 304 Invalid PDU mode parameter
CMS ERROR: 305 Invalid Text mode parameter
CMS ERROR: 310 SIM not inserted
CMS ERROR: 311 SIM PIN required
CMS ERROR: 312 PH-SIM PIN required
CMS ERROR: 313 SIM failure
CMS ERROR: 314 SIM busy
CMS ERROR: 315 SIM wrong
CMS ERROR: 316 SIM PUK required
CMS ERROR: 317 SIM PIN2 required
CMS ERROR: 318 SIM PUK2 required
CMS ERROR: 320 Memory failure
CMS ERROR: 321 Invalid memory index
CMS ERROR: 322 Memory full
CMS ERROR: 330 SMSC address unknown
CMS ERROR: 331 No network service
CMS ERROR: 332 Network timeout
CMS ERROR: 340 No +CNMA expected
CMS ERROR: 500 Unknown error
CMS ERROR: 512 User abort
CMS ERROR: 513 Unable to store
CMS ERROR: 514 Invalid Status
CMS ERROR: 515 Device busy or Invalid Character in string
CMS ERROR: 516 Invalid length
CMS ERROR: 517 Invalid character in PDU
CMS ERROR: 518 Invalid parameter
CMS ERROR: 519 Invalid length or character
CMS ERROR: 520 Invalid character in text
CMS ERROR: 521 Timer expired
CMS ERROR: 522 Operation temporary not allowed
CMS ERROR: 532 SIM not ready
CMS ERROR: 534 Cell Broadcast error unknown
CMS ERROR: 535 Protocol stack busy
CMS ERROR: 538 Invalid parameter

Citrix XenServer Error: VDI is not Available

Error: Starting VM ” – The VDI is not available

So you’re now trying to boot a VM in XenServer but you are getting the error “VDI is not Available”. This means that VM crashed, Xen Host crashed, or something just bad happen. Either way you need your server back.

  1. Find the UUID of the VDI in question.
    xe vdi-list
  2. Note exactly what UUID maps to which drive is on your server.  This is going to remove the VDI from the VM so we can reattach it correctly.  So drive order does matter, you don’t want to switch an OS VDI with a data VDI.
    xe vdi-forget uuid=<VDI UUID we found in step 1>
  3. Open XenCenter and navigate to the SR with your VDI.  Hit rescan
  4. Now goto your VM with issues and attach the VDI via the storage tab
  5. Boot your VM