Virtual I/O Server errors
Learn about the errors that might occur on the Virtual I/O Server (VIOS).
About this task
The following table lists possible VIOS errors and their definitions.
| Error Code | Definition |
|---|---|
| 1 | The virtual adapter is not ready to be moved. The source virtual Ethernet is not bridged. |
| 2 | The virtual adapter can be moved with less capability. All virtual local area networks (VLAN) are not bridged on the destination. Hence, the virtual Ethernet adapter has less capability on the target system compared to the source system. |
| 3 | The stream ID is still in use. |
| 64 | The migmgr command cannot be started. |
| 65 | The stream ID is invalid. |
| 66 | The virtual adapter type is invalid. |
| 67 | The virtual adapter DLPAR resource connector (DRC) name is not recognized. |
| 68 | The virtual adapter method cannot be started, or it was prematurely terminated. |
| 69 | There is a lack of resources (that is, the ENOMEM error code). |
| 80 | The storage that is being used by the adapter is specific to the VIOS and cannot be accessed by another VIOS. Hence, the virtual adapter cannot complete the mobility operation. |
| 81 | The virtual adapter is not configured. |
| 82 | The virtual adapter cannot be placed in a migration state. |
| 83 | The virtual devices are not found. |
| 84 | The virtual adapter VIOS level is insufficient. |
| 85 | The virtual adapter cannot be configured. |
| 86 | The virtual adapter is busy and cannot be unconfigured. |
| 87 | The virtual adapter or device minimum patch level is insufficient. |
| 88 | The device description is invalid. |
| 89 | The command argument is invalid. |
| 90 | The virtual target device cannot be created because of incompatible backing device attributes. Typically, this is because of a mismatch in the maximum transfer (MTU) size or SCSI reserve attributes of the backing device between the source VIOS and the target VIOS. |
| 91 | The DRC name passed to the migration code is for an adapter that exists. |