bmahmoud
Enthusiast
Enthusiast

ERROR: Task failed on server: Module ‘CPUID’ power on failed.

Jump to solution

Hi vTeam, I hope you’re all doing well.

I’m creating a nested VMware LAB where I have 1 physical server  with 16GB of RAM and 2 Physical Processors.

I’ve installed ESXi on this server and inside I’ve created 2 VMs with ESXi installed on each

(one with 11GB RAM for vCenter and the other with 5GB RAM for DC & DNS + Windows 7 and OpenFiler).

I can easily create VMs on it but when I tried to deploy VCSA 6.5 if fails

when it reaches 80% with this error: “Task failed on server: Module ‘CPUID’ power on failed.”,

any ideas, could you please help me? Thanks a lot in advance and hope to hear from you all as soon as possible guys, cheers

below are error LOGS:

2019-01-19T21:37:48.207Z - info: installerLogFile: C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller\installer-20190120-003748205.log
2019-01-19T21:37:48.229Z - info: networkLogFile: C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller\network-20190120-003748205.log
2019-01-19T21:37:52.562Z - debug: wizardTitle: Install - Stage 1: Deploy appliance
2019-01-19T21:38:12.436Z - debug: wizardTitle: Install - Stage 1: Deploy appliance
2019-01-19T21:38:22.362Z - debug: nodeType: embedded
2019-01-19T21:38:22.363Z - debug: wizardTitle: Install - Stage 1: Deploy vCenter Server Appliance with an Embedded Platform Services Controller
2019-01-19T21:38:35.439Z - info: THUMBPRINT(Target): B1:F5:6A:90:5E:65:CF:13:9B:09:78:79:04:A2:1A:07:5A:76:39:3E
2019-01-19T21:38:40.676Z - info: login() to 192.168.3.151
2019-01-19T21:38:40.678Z - info: initializing vsphere API connection to 192.168.3.151:443
2019-01-19T21:38:41.938Z - info: vimService apiType: HostAgent, version: 6.5.0
2019-01-19T21:38:41.955Z - debug: session does not exist: 192.168.3.151, root
2019-01-19T21:38:41.955Z - debug: Logging in to 192.168.3.151:443 as root
2019-01-19T21:38:42.026Z - info: Logged in to 192.168.3.151:443 as root, session: 528f186e-b221-8874-d6a7-439bdc8ce847
2019-01-19T21:38:42.026Z - debug: After successful login, initiate pingTimer with delay: 300000
2019-01-19T21:38:42.065Z - debug: admin roles:[ { entity: { value: 'ha-folder-root', type: 'Folder' },
    principal: 'vpxuser',
    group: false,
    roleId: -1,
    propagate: true },
  { entity: { value: 'ha-folder-root', type: 'Folder' },
    principal: 'dcui',
    group: false,
    roleId: -1,
    propagate: true },
  { entity: { value: 'ha-folder-root', type: 'Folder' },
    principal: 'root',
    group: false,
    roleId: -1,
    propagate: true } ]
2019-01-19T21:38:42.065Z - debug: user: root, userPrincipal: root
2019-01-19T21:38:42.065Z - debug: userHasAdminRole:root:root: has admin role
2019-01-19T21:38:42.065Z - debug: adminRole: true
2019-01-19T21:38:42.065Z - info: host target precheck
2019-01-19T21:38:42.632Z - info: hostPrecheck: VCSA.smartlink.com.sa, ha-host
2019-01-19T21:38:42.632Z - info: ESXi hostVersion=6.5, minVersion=5.5
2019-01-19T21:38:42.632Z - info: lockdownMode: 'lockdownDisabled'
2019-01-19T21:38:42.632Z - info: inMaintenanceMode: false
2019-01-19T21:38:42.632Z - info: hostPrecheck succeeded: VCSA.smartlink.com.sa
2019-01-19T21:38:42.632Z - info: ESXi hostCheck was successful
2019-01-19T21:38:42.654Z - error: ServerFaultCode: 'VSAN.EnableVsanBootstrap' is invalid or exceeds the maximum number of characters permitted.
2019-01-19T21:39:22.048Z - info: vmName: VMware vCenter Server Appliance
2019-01-19T21:39:22.090Z - debug: token:undefined, length:1, running total:1
2019-01-19T21:39:22.090Z - info: number of vms with name, VMware vCenter Server Appliance: 0
2019-01-19T21:39:22.109Z - debug: Deployment size page description: Select the deployment size for this vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:39:22.110Z - info: ovftoolCmd: I:\vcsa\ovftool\win32\ovftool.exe
2019-01-19T21:39:22.110Z - debug: ovaFileNameRe: /.*_OVF10.ova$/
2019-01-19T21:39:22.110Z - debug: files in I:\vcsa: VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova,ovftool,version.txt
2019-01-19T21:39:22.110Z - info: ovaFile: I:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova
2019-01-19T21:39:22.387Z - info: probeOvf exited with status 0
2019-01-19T21:39:22.388Z - info: probeOvf productName: VMware vCenter Server Appliance
2019-01-19T21:39:22.388Z - info: probeOvf fullVersion: 6.7.0.20000 build 10244745
2019-01-19T21:39:22.390Z - info: probeOvf result: + SUCCESS
2019-01-19T21:39:22.393Z - info: layout file: I:\vcsa-ui-installer\win32\resources\app\resources\layout.json
2019-01-19T21:39:22.393Z - info: nDeploymentOptions: 31
2019-01-19T21:39:22.396Z - warn: checkDiskspace:[tiny-xlstorage]: dfsys was not obtained
2019-01-19T21:39:22.396Z - debug: checkDiskspace:[tiny-xlstorage]: diskSpace, required: undefined, provided: 1700
2019-01-19T21:39:22.396Z - info: checkDiskspace:[tiny-xlstorage]: true
2019-01-19T21:39:22.396Z - warn: checkDiskspace:[tiny-lstorage]: dfsys was not obtained
2019-01-19T21:39:22.396Z - debug: checkDiskspace:[tiny-lstorage]: diskSpace, required: undefined, provided: 825
2019-01-19T21:39:22.396Z - info: checkDiskspace:[tiny-lstorage]: true
2019-01-19T21:39:22.396Z - warn: checkDiskspace:[tiny]: dfsys was not obtained
2019-01-19T21:39:22.396Z - debug: checkDiskspace:[tiny]: diskSpace, required: undefined, provided: 300
2019-01-19T21:39:22.396Z - info: checkDiskspace:[tiny]: true
2019-01-19T21:39:22.396Z - debug: default storage: tiny, 300
2019-01-19T21:39:22.396Z - debug: large storage: tiny-lstorage, 825
2019-01-19T21:39:22.396Z - debug: x-large storage: tiny-xlstorage, 1700
2019-01-19T21:39:22.396Z - debug: pre-defined defIdx found: 0
2019-01-19T21:39:22.396Z - info: defIdx: 0, id: tiny
2019-01-19T21:39:22.397Z - info: { id: 'tiny',
  isDefault: 'true',
  cpu: 2,
  memory: 10240,
  'host-count': 10,
  'vm-count': 100,
  label: 'Tiny',
  description: undefined,
  diskSpace: 300,
  'disk-swap': 25600,
  'disk-core': 25600,
  'disk-log': 10240,
  'disk-db': 10240,
  'disk-dblog': 15360,
  'disk-seat': 10240,
  'disk-netdump': 1024,
  'disk-autodeploy': 10240,
  'disk-imagebuilder': 10240,
  'disk-updatemgr': 102400,
  undefined: 0 }
2019-01-19T21:39:22.398Z - info: { id: 'default', label: 'Default' }
2019-01-19T21:39:24.370Z - info: selectedProfile: id=tiny
2019-01-19T21:39:24.371Z - debug: selectedProfile: { id: 'tiny',
  isDefault: 'true',
  cpu: 2,
  memory: 10240,
  'host-count': 10,
  'vm-count': 100,
  label: 'Tiny',
  description: undefined,
  diskSpace: 300,
  'disk-swap': 25600,
  'disk-core': 25600,
  'disk-log': 10240,
  'disk-db': 10240,
  'disk-dblog': 15360,
  'disk-seat': 10240,
  'disk-netdump': 1024,
  'disk-autodeploy': 10240,
  'disk-imagebuilder': 10240,
  'disk-updatemgr': 102400,
  undefined: 0 }
2019-01-19T21:39:24.371Z - info: tgtHostName: 192.168.3.151, hostName: VCSA.smartlink.com.sa
2019-01-19T21:39:24.371Z - debug: hardware: { vendor: 'VMware, Inc.',
  model: 'VMware Virtual Platform',
  uuid: '17b34d56-e78a-3b62-e519-d7c7cd448654',
  otherIdentifyingInfo: [],
  memorySize: 12884365312,
  cpuModel: 'Intel(R) Xeon(R) CPU E5-2407 0 @ 2.20GHz',
  cpuMhz: 2200,
  numCpuPkgs: 4,
  numCpuCores: 4,
  numCpuThreads: 4,
  numNics: 1,
  numHBAs: 3 }
2019-01-19T21:39:24.396Z - debug: Storage page description: Select the storage location for this vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:39:24.429Z - debug: Got 1 datastores
2019-01-19T21:39:24.456Z - debug: dsName: datastore1, isWritable: true, dsType: VMFS
2019-01-19T21:39:24.456Z - info: datastore: total=1, display=1
2019-01-19T21:39:24.459Z - debug: selectedDatastoreIdx: 0,
2019-01-19T21:39:33.338Z - debug: Selected datastore: { diskMode: 'thin',
  moRef: '5c4383fa-62e87919-5a3d-000c29448654',
  name: 'datastore1',
  type: 'VMFS-5',
  mode: 'existing',
  datastores:
   [ { moid: '5c4383fa-62e87919-5a3d-000c29448654',
       name: 'datastore1',
       type: 'VMFS-5',
       versionNum: 5,
       capacity: '492.5 GB',
       freeSpace: '491.55 GB',
       provisioned: '974 MB',
       thinProvisioning: true,
       displayThinProvising: 'Supported',
       rawCapacity: 528817848320,
       rawFreeSpace: 527796535296,
       rawProvisioned: 1021313024 } ],
  diskModeName: 'thin' }
2019-01-19T21:39:33.340Z - debug: selectedItem: { moid: '5c4383fa-62e87919-5a3d-000c29448654',
  name: 'datastore1',
  type: 'VMFS-5',
  versionNum: 5,
  capacity: '492.5 GB',
  freeSpace: '491.55 GB',
  provisioned: '974 MB',
  thinProvisioning: true,
  displayThinProvising: 'Supported',
  rawCapacity: 528817848320,
  rawFreeSpace: 527796535296,
  rawProvisioned: 1021313024 }
2019-01-19T21:39:33.341Z - debug: selectedDatastoreMoid: 5c4383fa-62e87919-5a3d-000c29448654
2019-01-19T21:39:33.342Z - debug: sizingData: { id: 'tiny',
  isDefault: 'true',
  cpu: 2,
  memory: 10240,
  'host-count': 10,
  'vm-count': 100,
  label: 'Tiny',
  description: undefined,
  diskSpace: 300,
  'disk-swap': 25600,
  'disk-core': 25600,
  'disk-log': 10240,
  'disk-db': 10240,
  'disk-dblog': 15360,
  'disk-seat': 10240,
  'disk-netdump': 1024,
  'disk-autodeploy': 10240,
  'disk-imagebuilder': 10240,
  'disk-updatemgr': 102400,
  undefined: 0 }
2019-01-19T21:39:33.342Z - debug: diskSpaceR: 26843545600
2019-01-19T21:39:33.342Z - debug: selected datastore: datastore1, freeSpaceGb: 491, diskSpaceR=26843545600, diskMode=thin
2019-01-19T21:39:33.342Z - debug: thin diskMode, freeSpace: 527796535296, diskSpaceR: 26843545600
2019-01-19T21:39:33.343Z - debug: validateDiskspace was successful
2019-01-19T21:39:33.391Z - debug: Network setttings page description: Configure network settings for this vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:39:33.392Z - info: networkFamily options IPv4, IPv6
2019-01-19T21:39:33.430Z - debug: Got 1 networks
2019-01-19T21:39:33.452Z - debug: networks retrieved: [ { _type: 'Network',
    _moid: 'HaNetwork-VM Network',
    host: [ [Object] ],
    name: 'VM Network',
    summary:
     { network: [Object],
       name: 'VM Network',
       accessible: true,
       ipPoolName: '' },
    vm: [ [Object] ],
    vimType: 'vim.Network' } ]
2019-01-19T21:39:33.452Z - debug: networks filtered: [ { name: 'VM Network',
    moid: 'HaNetwork-VM Network',
    type: 'vim.Network' } ]
2019-01-19T21:39:33.452Z - info: default network was set to VM Network
2019-01-19T21:39:33.453Z - debug: nwSelected: { name: 'VM Network',
  moid: 'HaNetwork-VM Network',
  type: 'vim.Network' }
2019-01-19T21:40:15.222Z - debug: this.networkData: { moRef: 'vim.Network:HaNetwork-VM Network',
  name: 'VM Network',
  netAddrFamily: 'IPv4',
  netMode: 'static',
  netModeString: 'static',
  netAddr: '192.168.3.203',
  netPrefix: '',
  netGateway: '192.168.3.1',
  hostName: '',
  netConvertedPrefix: '255.255.255.0',
  dnsServerNames: [ '192.168.3.30' ],
  dnsServerString: '192.168.3.30',
  httpPort: '80',
  httpsPort: '443',
  networks:
   [ { name: 'VM Network',
       moid: 'HaNetwork-VM Network',
       type: 'vim.Network' } ] }
2019-01-19T21:40:15.222Z - debug: targetServer: 192.168.3.151, sysName: , ipAddr: 192.168.3.203
2019-01-19T21:40:15.223Z - debug: checking if 192.168.3.203 exists in the network of vimConn: undefined
2019-01-19T21:40:15.224Z - debug: isIp: 192.168.3.203: true
2019-01-19T21:40:15.225Z - debug: getVmWithIPFQDN: hostName 192.168.3.203 is associated with [ '192.168.3.203' ]
2019-01-19T21:40:15.291Z - debug: token:undefined, length:1, running total:1
2019-01-19T21:40:15.292Z - error: No VM found with hostname 192.168.3.203
2019-01-19T21:40:15.292Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 192.168.3.203
2019-01-19T21:40:15.292Z - info: Network Prechecks Succeededundefined
2019-01-19T21:40:15.314Z - debug: scope.networkPrefixLabel: Subnet mask or prefix length
2019-01-19T21:40:15.315Z - debug: Summary page: summaryTargetLabel: Target ESXi host
2019-01-19T21:40:22.914Z - debug: sucMsg: You have successfully deployed the vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:40:22.917Z - info: vcsaFilePath: I:\vcsa
2019-01-19T21:40:22.918Z - debug: network prefix length: 24
2019-01-19T21:40:22.918Z - info: <PERFORMANCE>:DEPLOYMENT_SIZE:tiny
2019-01-19T21:40:22.918Z - debug: ovaFile retrieved: I:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova
2019-01-19T21:40:22.919Z - info: OVF Tool Options: --X:logFile=C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller\ovftool-20190120-003748205-20190120-004022917.log --X:logLevel=trivia --machineOutput --I:morefArgs --targetSSLThumbprint=B1:F5:6A:90:5E:65:CF:13:9B:09:78:79:04:A2:1A:07:5A:76:39:3E --acceptAllEulas --powerOn --X:enableHiddenProperties --allowExtraConfig --X:injectOvfEnv --sourceType=OVA --name=VMware vCenter Server Appliance --deploymentOption=tiny --prop:guestinfo.cis.deployment.node.type=embedded --prop:guestinfo.cis.deployment.autoconfig=False --prop:guestinfo.cis.clientlocale=en --datastore=vim.Datastore:5c4383fa-62e87919-5a3d-000c29448654 --net:Network 1=vim.Network:HaNetwork-VM Network --prop:guestinfo.cis.appliance.net.addr.family=ipv4 --prop:guestinfo.cis.appliance.net.mode=static --diskMode=thin --prop:guestinfo.cis.appliance.net.addr=192.168.3.203 --prop:guestinfo.cis.appliance.net.prefix=24 --prop:guestinfo.cis.appliance.net.dns.servers=192.168.3.30 --prop:guestinfo.cis.appliance.net.gateway=192.168.3.1 --prop:guestinfo.cis.appliance.net.ports={"rhttpproxy.ext.port1":"80","rhttpproxy.ext.port2":"443"} --prop:guestinfo.cis.appliance.root.passwd=CENSORED I:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova vi://root:CENSORED@192.168.3.151:443
2019-01-19T21:40:22.919Z - debug: ovftoolCmd retrieved: I:\vcsa\ovftool\win32\ovftool.exe
2019-01-19T21:40:23.150Z - info: output:MANIFEST
+ <ManifestValidate valid="true"/>


2019-01-19T21:40:42.167Z - info: output:PROGRESS

2019-01-19T21:40:55.720Z - info: output:+ 1

2019-01-19T21:41:03.466Z - info: output:+ 2

2019-01-19T21:41:10.983Z - info: output:+ 3

2019-01-19T21:41:46.869Z - info: output:+ 4

2019-01-19T21:42:01.138Z - info: output:+ 5

2019-01-19T21:42:13.883Z - info: output:+ 6

2019-01-19T21:42:28.560Z - info: output:+ 7

2019-01-19T21:42:46.566Z - info: output:+ 8

2019-01-19T21:43:01.035Z - info: output:+ 9

2019-01-19T21:43:19.507Z - info: output:+ 10

2019-01-19T21:43:41.204Z - info: output:+ 11

2019-01-19T21:43:42.082Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:27:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:44:14.265Z - info: output:+ 12

2019-01-19T21:45:16.316Z - info: output:+ 13

2019-01-19T21:45:59.147Z - info: output:+ 14

2019-01-19T21:46:36.820Z - info: output:+ 15

2019-01-19T21:47:02.052Z - info: output:+ 16

2019-01-19T21:47:40.913Z - info: output:+ 17

2019-01-19T21:48:12.279Z - info: output:+ 18

2019-01-19T21:48:32.127Z - info: output:+ 19

2019-01-19T21:48:42.069Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:32:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:48:56.107Z - info: output:+ 20

2019-01-19T21:49:36.158Z - info: output:+ 21

2019-01-19T21:50:00.955Z - info: output:+ 22

2019-01-19T21:50:41.972Z - info: output:+ 23

2019-01-19T21:51:04.958Z - info: output:+ 24

2019-01-19T21:51:25.658Z - info: output:+ 25

2019-01-19T21:51:34.376Z - info: output:+ 26

2019-01-19T21:51:39.272Z - info: output:+ 27

2019-01-19T21:51:46.169Z - info: output:+ 28

2019-01-19T21:51:52.983Z - info: output:+ 29

2019-01-19T21:52:01.173Z - info: output:+ 30

2019-01-19T21:52:09.272Z - info: output:+ 31

2019-01-19T21:52:15.839Z - info: output:+ 32

2019-01-19T21:52:26.024Z - info: output:+ 33

2019-01-19T21:52:33.956Z - info: output:+ 34

2019-01-19T21:52:42.710Z - info: output:+ 35

2019-01-19T21:52:49.627Z - info: output:+ 36

2019-01-19T21:52:55.976Z - info: output:+ 37

2019-01-19T21:53:05.650Z - info: output:+ 38

2019-01-19T21:53:10.983Z - info: output:+ 39

2019-01-19T21:53:22.031Z - info: output:+ 40

2019-01-19T21:53:28.633Z - info: output:+ 41

2019-01-19T21:53:39.108Z - info: output:+ 42

2019-01-19T21:53:42.072Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:37:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:53:47.119Z - info: output:+ 43

2019-01-19T21:53:53.433Z - info: output:+ 44

2019-01-19T21:54:02.989Z - info: output:+ 45

2019-01-19T21:54:11.319Z - info: output:+ 46

2019-01-19T21:54:20.282Z - info: output:+ 47

2019-01-19T21:54:28.269Z - info: output:+ 48

2019-01-19T21:54:38.472Z - info: output:+ 49

2019-01-19T21:54:46.306Z - info: output:+ 50

2019-01-19T21:54:53.507Z - info: output:+ 51

2019-01-19T21:55:00.856Z - info: output:+ 52

2019-01-19T21:55:11.456Z - info: output:+ 53

2019-01-19T21:55:22.454Z - info: output:+ 54

2019-01-19T21:55:31.484Z - info: output:+ 55

2019-01-19T21:55:42.208Z - info: output:+ 56

2019-01-19T21:55:53.932Z - info: output:+ 57

2019-01-19T21:56:07.765Z - info: output:+ 58

2019-01-19T21:56:17.151Z - info: output:+ 59

2019-01-19T21:56:28.115Z - info: output:+ 60

2019-01-19T21:56:38.330Z - info: output:+ 61

2019-01-19T21:56:50.164Z - info: output:+ 62

2019-01-19T21:57:00.471Z - info: output:+ 63

2019-01-19T21:57:07.317Z - info: output:+ 64

2019-01-19T21:57:15.000Z - info: output:+ 65

2019-01-19T21:57:28.674Z - info: output:+ 66

2019-01-19T21:57:35.512Z - info: output:+ 67

2019-01-19T21:57:47.120Z - info: output:+ 68

2019-01-19T21:57:56.280Z - info: output:+ 69

2019-01-19T21:58:06.546Z - info: output:+ 70

2019-01-19T21:58:12.860Z - info: output:+ 71

2019-01-19T21:58:25.951Z - info: output:+ 72

2019-01-19T21:58:32.925Z - info: output:+ 73

2019-01-19T21:58:42.066Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:42:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:58:47.056Z - info: output:+ 74

2019-01-19T21:58:55.924Z - info: output:+ 75

2019-01-19T21:59:05.127Z - info: output:+ 76

2019-01-19T21:59:14.988Z - info: output:+ 77

2019-01-19T21:59:22.038Z - info: output:+ 78

2019-01-19T21:59:32.464Z - info: output:+ 79

2019-01-19T21:59:42.478Z - info: output:+ 80

2019-01-19T21:59:51.805Z - info: output:+ 81

2019-01-19T22:00:02.357Z - info: output:+ 82

2019-01-19T22:00:12.705Z - info: output:+ 83

2019-01-19T22:00:23.162Z - info: output:+ 84

2019-01-19T22:00:32.409Z - info: output:+ 85

2019-01-19T22:00:40.428Z - info: output:+ 86

2019-01-19T22:00:49.279Z - info: output:+ 87

2019-01-19T22:01:02.468Z - info: output:+ 88

2019-01-19T22:01:15.377Z - info: output:+ 89

2019-01-19T22:01:26.333Z - info: output:+ 90

2019-01-19T22:01:41.500Z - info: output:+ 91

2019-01-19T22:01:56.647Z - info: output:+ 92

2019-01-19T22:02:14.147Z - info: output:+ 93

2019-01-19T22:02:31.479Z - info: output:+ 94

2019-01-19T22:02:44.718Z - info: output:+ 95

2019-01-19T22:03:01.404Z - info: output:+ 96

2019-01-19T22:03:21.631Z - info: output:+ 97

2019-01-19T22:03:35.728Z - info: output:+ 98

2019-01-19T22:03:42.093Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:47:40 GMT+0300 (Arab Standard Time)
2019-01-19T22:03:52.307Z - info: output:+ 99

2019-01-19T22:04:01.402Z - info: output:+ 100


2019-01-19T22:04:01.406Z - info: <PERFORMANCE>:OVA_DEPLOY:1418:seconds
2019-01-19T22:04:07.313Z - info: output:POWERON

2019-01-19T22:04:09.247Z - info: output:+ 0

2019-01-19T22:04:09.478Z - info: output:+ 6

2019-01-19T22:04:10.816Z - info: output:+ 21

2019-01-19T22:04:11.618Z - info: output:+ 22

2019-01-19T22:04:12.021Z - info: output:+ 32

2019-01-19T22:04:12.279Z - info: output:+ 44

2019-01-19T22:04:12.707Z - info: output:+ 45

2019-01-19T22:04:13.577Z - info: output:+ 48

2019-01-19T22:04:14.593Z - info: output:+ 58

2019-01-19T22:04:17.700Z - info: output:+ 70

2019-01-19T22:04:23.082Z - info: output:

2019-01-19T22:04:23.089Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.vi.task</Type>
+ <LocalizedMsg>
+ Task failed on server: Module &apos;CPUID&apos; power on failed.
+ </LocalizedMsg>
+ <Arg>
+ Module &apos;CPUID&apos; power on failed.
+ </Arg>
+ </Error>
+ </Errors>


2019-01-19T22:04:25.114Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.system.error</Type>
+ <LocalizedMsg>
+ Fault cause: vim.fault.InvalidState
+
+ </LocalizedMsg>
+ </Error>
+ </Errors>


2019-01-19T22:04:25.115Z - info: output:RESULT
+ ERROR


2019-01-19T22:04:25.115Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.vi.task</Type><LocalizedMsg>Task failed on server: Module &apos;CPUID&apos; power on failed.</LocalizedMsg><Arg>Module &apos;CPUID&apos; power on failed.</Arg></Error></Errors><Errors><Error><Type>ovftool.system.error</Type><LocalizedMsg>Fault cause: vim.fault.InvalidState</LocalizedMsg></Error></Errors></data>
2019-01-19T22:04:25.118Z - error: Ovf Service:vmrefFlag: false
2019-01-19T22:04:25.118Z - info: Cancelling timeout due to error from progress callback
2019-01-19T22:04:25.118Z - error: Progress Controller: [VCSA ERROR] - Progress callback error
2019-01-19T22:04:25.119Z - error: Progress Controller: [VCSA ERROR] - Details Task failed on server: Module 'CPUID' power on failed.
2019-01-19T22:04:25.119Z - error: Progress Controller: [VCSA ERROR] - Details Fault cause: vim.fault.InvalidState
2019-01-19T22:04:25.125Z - info: Cancelling the ping timer for session mgmt
2019-01-19T22:04:25.126Z - info: Cancelling the ping timer for session mgmt
2019-01-19T22:04:25.146Z - info: ovfProcess child process exited with code 1
2019-01-19T22:12:34.554Z - info: Log file was saved at: C:\Users\bmahmoud\Downloads\logs-installer-20190120-003748205

2019-01-19T21:37:48.207Z - info: installerLogFile: C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller\installer-20190120-003748205.log
2019-01-19T21:37:48.229Z - info: networkLogFile: C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller\network-20190120-003748205.log
2019-01-19T21:37:52.562Z - debug: wizardTitle: Install - Stage 1: Deploy appliance
2019-01-19T21:38:12.436Z - debug: wizardTitle: Install - Stage 1: Deploy appliance
2019-01-19T21:38:22.362Z - debug: nodeType: embedded
2019-01-19T21:38:22.363Z - debug: wizardTitle: Install - Stage 1: Deploy vCenter Server Appliance with an Embedded Platform Services Controller
2019-01-19T21:38:35.439Z - info: THUMBPRINT(Target): B1:F5:6A:90:5E:65:CF:13:9B:09:78:79:04:A2:1A:07:5A:76:39:3E
2019-01-19T21:38:40.676Z - info: login() to 192.168.3.151
2019-01-19T21:38:40.678Z - info: initializing vsphere API connection to 192.168.3.151:443
2019-01-19T21:38:41.938Z - info: vimService apiType: HostAgent, version: 6.5.0
2019-01-19T21:38:41.955Z - debug: session does not exist: 192.168.3.151, root
2019-01-19T21:38:41.955Z - debug: Logging in to 192.168.3.151:443 as root
2019-01-19T21:38:42.026Z - info: Logged in to 192.168.3.151:443 as root, session: 528f186e-b221-8874-d6a7-439bdc8ce847
2019-01-19T21:38:42.026Z - debug: After successful login, initiate pingTimer with delay: 300000
2019-01-19T21:38:42.065Z - debug: admin roles:[ { entity: { value: 'ha-folder-root', type: 'Folder' },
    principal: 'vpxuser',
    group: false,
    roleId: -1,
    propagate: true },
  { entity: { value: 'ha-folder-root', type: 'Folder' },
    principal: 'dcui',
    group: false,
    roleId: -1,
    propagate: true },
  { entity: { value: 'ha-folder-root', type: 'Folder' },
    principal: 'root',
    group: false,
    roleId: -1,
    propagate: true } ]
2019-01-19T21:38:42.065Z - debug: user: root, userPrincipal: root
2019-01-19T21:38:42.065Z - debug: userHasAdminRole:root:root: has admin role
2019-01-19T21:38:42.065Z - debug: adminRole: true
2019-01-19T21:38:42.065Z - info: host target precheck
2019-01-19T21:38:42.632Z - info: hostPrecheck: VCSA.smartlink.com.sa, ha-host
2019-01-19T21:38:42.632Z - info: ESXi hostVersion=6.5, minVersion=5.5
2019-01-19T21:38:42.632Z - info: lockdownMode: 'lockdownDisabled'
2019-01-19T21:38:42.632Z - info: inMaintenanceMode: false
2019-01-19T21:38:42.632Z - info: hostPrecheck succeeded: VCSA.smartlink.com.sa
2019-01-19T21:38:42.632Z - info: ESXi hostCheck was successful
2019-01-19T21:38:42.654Z - error: ServerFaultCode: 'VSAN.EnableVsanBootstrap' is invalid or exceeds the maximum number of characters permitted.
2019-01-19T21:39:22.048Z - info: vmName: VMware vCenter Server Appliance
2019-01-19T21:39:22.090Z - debug: token:undefined, length:1, running total:1
2019-01-19T21:39:22.090Z - info: number of vms with name, VMware vCenter Server Appliance: 0
2019-01-19T21:39:22.109Z - debug: Deployment size page description: Select the deployment size for this vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:39:22.110Z - info: ovftoolCmd: I:\vcsa\ovftool\win32\ovftool.exe
2019-01-19T21:39:22.110Z - debug: ovaFileNameRe: /.*_OVF10.ova$/
2019-01-19T21:39:22.110Z - debug: files in I:\vcsa: VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova,ovftool,version.txt
2019-01-19T21:39:22.110Z - info: ovaFile: I:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova
2019-01-19T21:39:22.387Z - info: probeOvf exited with status 0
2019-01-19T21:39:22.388Z - info: probeOvf productName: VMware vCenter Server Appliance
2019-01-19T21:39:22.388Z - info: probeOvf fullVersion: 6.7.0.20000 build 10244745
2019-01-19T21:39:22.390Z - info: probeOvf result: + SUCCESS
2019-01-19T21:39:22.393Z - info: layout file: I:\vcsa-ui-installer\win32\resources\app\resources\layout.json
2019-01-19T21:39:22.393Z - info: nDeploymentOptions: 31
2019-01-19T21:39:22.396Z - warn: checkDiskspace:[tiny-xlstorage]: dfsys was not obtained
2019-01-19T21:39:22.396Z - debug: checkDiskspace:[tiny-xlstorage]: diskSpace, required: undefined, provided: 1700
2019-01-19T21:39:22.396Z - info: checkDiskspace:[tiny-xlstorage]: true
2019-01-19T21:39:22.396Z - warn: checkDiskspace:[tiny-lstorage]: dfsys was not obtained
2019-01-19T21:39:22.396Z - debug: checkDiskspace:[tiny-lstorage]: diskSpace, required: undefined, provided: 825
2019-01-19T21:39:22.396Z - info: checkDiskspace:[tiny-lstorage]: true
2019-01-19T21:39:22.396Z - warn: checkDiskspace:[tiny]: dfsys was not obtained
2019-01-19T21:39:22.396Z - debug: checkDiskspace:[tiny]: diskSpace, required: undefined, provided: 300
2019-01-19T21:39:22.396Z - info: checkDiskspace:[tiny]: true
2019-01-19T21:39:22.396Z - debug: default storage: tiny, 300
2019-01-19T21:39:22.396Z - debug: large storage: tiny-lstorage, 825
2019-01-19T21:39:22.396Z - debug: x-large storage: tiny-xlstorage, 1700
2019-01-19T21:39:22.396Z - debug: pre-defined defIdx found: 0
2019-01-19T21:39:22.396Z - info: defIdx: 0, id: tiny
2019-01-19T21:39:22.397Z - info: { id: 'tiny',
  isDefault: 'true',
  cpu: 2,
  memory: 10240,
  'host-count': 10,
  'vm-count': 100,
  label: 'Tiny',
  description: undefined,
  diskSpace: 300,
  'disk-swap': 25600,
  'disk-core': 25600,
  'disk-log': 10240,
  'disk-db': 10240,
  'disk-dblog': 15360,
  'disk-seat': 10240,
  'disk-netdump': 1024,
  'disk-autodeploy': 10240,
  'disk-imagebuilder': 10240,
  'disk-updatemgr': 102400,
  undefined: 0 }
2019-01-19T21:39:22.398Z - info: { id: 'default', label: 'Default' }
2019-01-19T21:39:24.370Z - info: selectedProfile: id=tiny
2019-01-19T21:39:24.371Z - debug: selectedProfile: { id: 'tiny',
  isDefault: 'true',
  cpu: 2,
  memory: 10240,
  'host-count': 10,
  'vm-count': 100,
  label: 'Tiny',
  description: undefined,
  diskSpace: 300,
  'disk-swap': 25600,
  'disk-core': 25600,
  'disk-log': 10240,
  'disk-db': 10240,
  'disk-dblog': 15360,
  'disk-seat': 10240,
  'disk-netdump': 1024,
  'disk-autodeploy': 10240,
  'disk-imagebuilder': 10240,
  'disk-updatemgr': 102400,
  undefined: 0 }
2019-01-19T21:39:24.371Z - info: tgtHostName: 192.168.3.151, hostName: VCSA.smartlink.com.sa
2019-01-19T21:39:24.371Z - debug: hardware: { vendor: 'VMware, Inc.',
  model: 'VMware Virtual Platform',
  uuid: '17b34d56-e78a-3b62-e519-d7c7cd448654',
  otherIdentifyingInfo: [],
  memorySize: 12884365312,
  cpuModel: 'Intel(R) Xeon(R) CPU E5-2407 0 @ 2.20GHz',
  cpuMhz: 2200,
  numCpuPkgs: 4,
  numCpuCores: 4,
  numCpuThreads: 4,
  numNics: 1,
  numHBAs: 3 }
2019-01-19T21:39:24.396Z - debug: Storage page description: Select the storage location for this vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:39:24.429Z - debug: Got 1 datastores
2019-01-19T21:39:24.456Z - debug: dsName: datastore1, isWritable: true, dsType: VMFS
2019-01-19T21:39:24.456Z - info: datastore: total=1, display=1
2019-01-19T21:39:24.459Z - debug: selectedDatastoreIdx: 0,
2019-01-19T21:39:33.338Z - debug: Selected datastore: { diskMode: 'thin',
  moRef: '5c4383fa-62e87919-5a3d-000c29448654',
  name: 'datastore1',
  type: 'VMFS-5',
  mode: 'existing',
  datastores:
   [ { moid: '5c4383fa-62e87919-5a3d-000c29448654',
       name: 'datastore1',
       type: 'VMFS-5',
       versionNum: 5,
       capacity: '492.5 GB',
       freeSpace: '491.55 GB',
       provisioned: '974 MB',
       thinProvisioning: true,
       displayThinProvising: 'Supported',
       rawCapacity: 528817848320,
       rawFreeSpace: 527796535296,
       rawProvisioned: 1021313024 } ],
  diskModeName: 'thin' }
2019-01-19T21:39:33.340Z - debug: selectedItem: { moid: '5c4383fa-62e87919-5a3d-000c29448654',
  name: 'datastore1',
  type: 'VMFS-5',
  versionNum: 5,
  capacity: '492.5 GB',
  freeSpace: '491.55 GB',
  provisioned: '974 MB',
  thinProvisioning: true,
  displayThinProvising: 'Supported',
  rawCapacity: 528817848320,
  rawFreeSpace: 527796535296,
  rawProvisioned: 1021313024 }
2019-01-19T21:39:33.341Z - debug: selectedDatastoreMoid: 5c4383fa-62e87919-5a3d-000c29448654
2019-01-19T21:39:33.342Z - debug: sizingData: { id: 'tiny',
  isDefault: 'true',
  cpu: 2,
  memory: 10240,
  'host-count': 10,
  'vm-count': 100,
  label: 'Tiny',
  description: undefined,
  diskSpace: 300,
  'disk-swap': 25600,
  'disk-core': 25600,
  'disk-log': 10240,
  'disk-db': 10240,
  'disk-dblog': 15360,
  'disk-seat': 10240,
  'disk-netdump': 1024,
  'disk-autodeploy': 10240,
  'disk-imagebuilder': 10240,
  'disk-updatemgr': 102400,
  undefined: 0 }
2019-01-19T21:39:33.342Z - debug: diskSpaceR: 26843545600
2019-01-19T21:39:33.342Z - debug: selected datastore: datastore1, freeSpaceGb: 491, diskSpaceR=26843545600, diskMode=thin
2019-01-19T21:39:33.342Z - debug: thin diskMode, freeSpace: 527796535296, diskSpaceR: 26843545600
2019-01-19T21:39:33.343Z - debug: validateDiskspace was successful
2019-01-19T21:39:33.391Z - debug: Network setttings page description: Configure network settings for this vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:39:33.392Z - info: networkFamily options IPv4, IPv6
2019-01-19T21:39:33.430Z - debug: Got 1 networks
2019-01-19T21:39:33.452Z - debug: networks retrieved: [ { _type: 'Network',
    _moid: 'HaNetwork-VM Network',
    host: [ [Object] ],
    name: 'VM Network',
    summary:
     { network: [Object],
       name: 'VM Network',
       accessible: true,
       ipPoolName: '' },
    vm: [ [Object] ],
    vimType: 'vim.Network' } ]
2019-01-19T21:39:33.452Z - debug: networks filtered: [ { name: 'VM Network',
    moid: 'HaNetwork-VM Network',
    type: 'vim.Network' } ]
2019-01-19T21:39:33.452Z - info: default network was set to VM Network
2019-01-19T21:39:33.453Z - debug: nwSelected: { name: 'VM Network',
  moid: 'HaNetwork-VM Network',
  type: 'vim.Network' }
2019-01-19T21:40:15.222Z - debug: this.networkData: { moRef: 'vim.Network:HaNetwork-VM Network',
  name: 'VM Network',
  netAddrFamily: 'IPv4',
  netMode: 'static',
  netModeString: 'static',
  netAddr: '192.168.3.203',
  netPrefix: '',
  netGateway: '192.168.3.1',
  hostName: '',
  netConvertedPrefix: '255.255.255.0',
  dnsServerNames: [ '192.168.3.30' ],
  dnsServerString: '192.168.3.30',
  httpPort: '80',
  httpsPort: '443',
  networks:
   [ { name: 'VM Network',
       moid: 'HaNetwork-VM Network',
       type: 'vim.Network' } ] }
2019-01-19T21:40:15.222Z - debug: targetServer: 192.168.3.151, sysName: , ipAddr: 192.168.3.203
2019-01-19T21:40:15.223Z - debug: checking if 192.168.3.203 exists in the network of vimConn: undefined
2019-01-19T21:40:15.224Z - debug: isIp: 192.168.3.203: true
2019-01-19T21:40:15.225Z - debug: getVmWithIPFQDN: hostName 192.168.3.203 is associated with [ '192.168.3.203' ]
2019-01-19T21:40:15.291Z - debug: token:undefined, length:1, running total:1
2019-01-19T21:40:15.292Z - error: No VM found with hostname 192.168.3.203
2019-01-19T21:40:15.292Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 192.168.3.203
2019-01-19T21:40:15.292Z - info: Network Prechecks Succeededundefined
2019-01-19T21:40:15.314Z - debug: scope.networkPrefixLabel: Subnet mask or prefix length
2019-01-19T21:40:15.315Z - debug: Summary page: summaryTargetLabel: Target ESXi host
2019-01-19T21:40:22.914Z - debug: sucMsg: You have successfully deployed the vCenter Server with an Embedded Platform Services Controller.
2019-01-19T21:40:22.917Z - info: vcsaFilePath: I:\vcsa
2019-01-19T21:40:22.918Z - debug: network prefix length: 24
2019-01-19T21:40:22.918Z - info: <PERFORMANCE>:DEPLOYMENT_SIZE:tiny
2019-01-19T21:40:22.918Z - debug: ovaFile retrieved: I:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova
2019-01-19T21:40:22.919Z - info: OVF Tool Options: --X:logFile=C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller\ovftool-20190120-003748205-20190120-004022917.log --X:logLevel=trivia --machineOutput --I:morefArgs --targetSSLThumbprint=B1:F5:6A:90:5E:65:CF:13:9B:09:78:79:04:A2:1A:07:5A:76:39:3E --acceptAllEulas --powerOn --X:enableHiddenProperties --allowExtraConfig --X:injectOvfEnv --sourceType=OVA --name=VMware vCenter Server Appliance --deploymentOption=tiny --prop:guestinfo.cis.deployment.node.type=embedded --prop:guestinfo.cis.deployment.autoconfig=False --prop:guestinfo.cis.clientlocale=en --datastore=vim.Datastore:5c4383fa-62e87919-5a3d-000c29448654 --net:Network 1=vim.Network:HaNetwork-VM Network --prop:guestinfo.cis.appliance.net.addr.family=ipv4 --prop:guestinfo.cis.appliance.net.mode=static --diskMode=thin --prop:guestinfo.cis.appliance.net.addr=192.168.3.203 --prop:guestinfo.cis.appliance.net.prefix=24 --prop:guestinfo.cis.appliance.net.dns.servers=192.168.3.30 --prop:guestinfo.cis.appliance.net.gateway=192.168.3.1 --prop:guestinfo.cis.appliance.net.ports={"rhttpproxy.ext.port1":"80","rhttpproxy.ext.port2":"443"} --prop:guestinfo.cis.appliance.root.passwd=CENSORED I:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.20000-10244745_OVF10.ova vi://root:CENSORED@192.168.3.151:443
2019-01-19T21:40:22.919Z - debug: ovftoolCmd retrieved: I:\vcsa\ovftool\win32\ovftool.exe
2019-01-19T21:40:23.150Z - info: output:MANIFEST
+ <ManifestValidate valid="true"/>


2019-01-19T21:40:42.167Z - info: output:PROGRESS

2019-01-19T21:40:55.720Z - info: output:+ 1

2019-01-19T21:41:03.466Z - info: output:+ 2

2019-01-19T21:41:10.983Z - info: output:+ 3

2019-01-19T21:41:46.869Z - info: output:+ 4

2019-01-19T21:42:01.138Z - info: output:+ 5

2019-01-19T21:42:13.883Z - info: output:+ 6

2019-01-19T21:42:28.560Z - info: output:+ 7

2019-01-19T21:42:46.566Z - info: output:+ 8

2019-01-19T21:43:01.035Z - info: output:+ 9

2019-01-19T21:43:19.507Z - info: output:+ 10

2019-01-19T21:43:41.204Z - info: output:+ 11

2019-01-19T21:43:42.082Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:27:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:44:14.265Z - info: output:+ 12

2019-01-19T21:45:16.316Z - info: output:+ 13

2019-01-19T21:45:59.147Z - info: output:+ 14

2019-01-19T21:46:36.820Z - info: output:+ 15

2019-01-19T21:47:02.052Z - info: output:+ 16

2019-01-19T21:47:40.913Z - info: output:+ 17

2019-01-19T21:48:12.279Z - info: output:+ 18

2019-01-19T21:48:32.127Z - info: output:+ 19

2019-01-19T21:48:42.069Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:32:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:48:56.107Z - info: output:+ 20

2019-01-19T21:49:36.158Z - info: output:+ 21

2019-01-19T21:50:00.955Z - info: output:+ 22

2019-01-19T21:50:41.972Z - info: output:+ 23

2019-01-19T21:51:04.958Z - info: output:+ 24

2019-01-19T21:51:25.658Z - info: output:+ 25

2019-01-19T21:51:34.376Z - info: output:+ 26

2019-01-19T21:51:39.272Z - info: output:+ 27

2019-01-19T21:51:46.169Z - info: output:+ 28

2019-01-19T21:51:52.983Z - info: output:+ 29

2019-01-19T21:52:01.173Z - info: output:+ 30

2019-01-19T21:52:09.272Z - info: output:+ 31

2019-01-19T21:52:15.839Z - info: output:+ 32

2019-01-19T21:52:26.024Z - info: output:+ 33

2019-01-19T21:52:33.956Z - info: output:+ 34

2019-01-19T21:52:42.710Z - info: output:+ 35

2019-01-19T21:52:49.627Z - info: output:+ 36

2019-01-19T21:52:55.976Z - info: output:+ 37

2019-01-19T21:53:05.650Z - info: output:+ 38

2019-01-19T21:53:10.983Z - info: output:+ 39

2019-01-19T21:53:22.031Z - info: output:+ 40

2019-01-19T21:53:28.633Z - info: output:+ 41

2019-01-19T21:53:39.108Z - info: output:+ 42

2019-01-19T21:53:42.072Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:37:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:53:47.119Z - info: output:+ 43

2019-01-19T21:53:53.433Z - info: output:+ 44

2019-01-19T21:54:02.989Z - info: output:+ 45

2019-01-19T21:54:11.319Z - info: output:+ 46

2019-01-19T21:54:20.282Z - info: output:+ 47

2019-01-19T21:54:28.269Z - info: output:+ 48

2019-01-19T21:54:38.472Z - info: output:+ 49

2019-01-19T21:54:46.306Z - info: output:+ 50

2019-01-19T21:54:53.507Z - info: output:+ 51

2019-01-19T21:55:00.856Z - info: output:+ 52

2019-01-19T21:55:11.456Z - info: output:+ 53

2019-01-19T21:55:22.454Z - info: output:+ 54

2019-01-19T21:55:31.484Z - info: output:+ 55

2019-01-19T21:55:42.208Z - info: output:+ 56

2019-01-19T21:55:53.932Z - info: output:+ 57

2019-01-19T21:56:07.765Z - info: output:+ 58

2019-01-19T21:56:17.151Z - info: output:+ 59

2019-01-19T21:56:28.115Z - info: output:+ 60

2019-01-19T21:56:38.330Z - info: output:+ 61

2019-01-19T21:56:50.164Z - info: output:+ 62

2019-01-19T21:57:00.471Z - info: output:+ 63

2019-01-19T21:57:07.317Z - info: output:+ 64

2019-01-19T21:57:15.000Z - info: output:+ 65

2019-01-19T21:57:28.674Z - info: output:+ 66

2019-01-19T21:57:35.512Z - info: output:+ 67

2019-01-19T21:57:47.120Z - info: output:+ 68

2019-01-19T21:57:56.280Z - info: output:+ 69

2019-01-19T21:58:06.546Z - info: output:+ 70

2019-01-19T21:58:12.860Z - info: output:+ 71

2019-01-19T21:58:25.951Z - info: output:+ 72

2019-01-19T21:58:32.925Z - info: output:+ 73

2019-01-19T21:58:42.066Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:42:40 GMT+0300 (Arab Standard Time)
2019-01-19T21:58:47.056Z - info: output:+ 74

2019-01-19T21:58:55.924Z - info: output:+ 75

2019-01-19T21:59:05.127Z - info: output:+ 76

2019-01-19T21:59:14.988Z - info: output:+ 77

2019-01-19T21:59:22.038Z - info: output:+ 78

2019-01-19T21:59:32.464Z - info: output:+ 79

2019-01-19T21:59:42.478Z - info: output:+ 80

2019-01-19T21:59:51.805Z - info: output:+ 81

2019-01-19T22:00:02.357Z - info: output:+ 82

2019-01-19T22:00:12.705Z - info: output:+ 83

2019-01-19T22:00:23.162Z - info: output:+ 84

2019-01-19T22:00:32.409Z - info: output:+ 85

2019-01-19T22:00:40.428Z - info: output:+ 86

2019-01-19T22:00:49.279Z - info: output:+ 87

2019-01-19T22:01:02.468Z - info: output:+ 88

2019-01-19T22:01:15.377Z - info: output:+ 89

2019-01-19T22:01:26.333Z - info: output:+ 90

2019-01-19T22:01:41.500Z - info: output:+ 91

2019-01-19T22:01:56.647Z - info: output:+ 92

2019-01-19T22:02:14.147Z - info: output:+ 93

2019-01-19T22:02:31.479Z - info: output:+ 94

2019-01-19T22:02:44.718Z - info: output:+ 95

2019-01-19T22:03:01.404Z - info: output:+ 96

2019-01-19T22:03:21.631Z - info: output:+ 97

2019-01-19T22:03:35.728Z - info: output:+ 98

2019-01-19T22:03:42.093Z - debug: Updated current session with lstActTm Sun Jan 20 2019 03:47:40 GMT+0300 (Arab Standard Time)
2019-01-19T22:03:52.307Z - info: output:+ 99

2019-01-19T22:04:01.402Z - info: output:+ 100


2019-01-19T22:04:01.406Z - info: <PERFORMANCE>:OVA_DEPLOY:1418:seconds
2019-01-19T22:04:07.313Z - info: output:POWERON

2019-01-19T22:04:09.247Z - info: output:+ 0

2019-01-19T22:04:09.478Z - info: output:+ 6

2019-01-19T22:04:10.816Z - info: output:+ 21

2019-01-19T22:04:11.618Z - info: output:+ 22

2019-01-19T22:04:12.021Z - info: output:+ 32

2019-01-19T22:04:12.279Z - info: output:+ 44

2019-01-19T22:04:12.707Z - info: output:+ 45

2019-01-19T22:04:13.577Z - info: output:+ 48

2019-01-19T22:04:14.593Z - info: output:+ 58

2019-01-19T22:04:17.700Z - info: output:+ 70

2019-01-19T22:04:23.082Z - info: output:

2019-01-19T22:04:23.089Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.vi.task</Type>
+ <LocalizedMsg>
+ Task failed on server: Module &apos;CPUID&apos; power on failed.
+ </LocalizedMsg>
+ <Arg>
+ Module &apos;CPUID&apos; power on failed.
+ </Arg>
+ </Error>
+ </Errors>


2019-01-19T22:04:25.114Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.system.error</Type>
+ <LocalizedMsg>
+ Fault cause: vim.fault.InvalidState
+
+ </LocalizedMsg>
+ </Error>
+ </Errors>


2019-01-19T22:04:25.115Z - info: output:RESULT
+ ERROR


2019-01-19T22:04:25.115Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.vi.task</Type><LocalizedMsg>Task failed on server: Module &apos;CPUID&apos; power on failed.</LocalizedMsg><Arg>Module &apos;CPUID&apos; power on failed.</Arg></Error></Errors><Errors><Error><Type>ovftool.system.error</Type><LocalizedMsg>Fault cause: vim.fault.InvalidState</LocalizedMsg></Error></Errors></data>
2019-01-19T22:04:25.118Z - error: Ovf Service:vmrefFlag: false
2019-01-19T22:04:25.118Z - info: Cancelling timeout due to error from progress callback
2019-01-19T22:04:25.118Z - error: Progress Controller: [VCSA ERROR] - Progress callback error
2019-01-19T22:04:25.119Z - error: Progress Controller: [VCSA ERROR] - Details Task failed on server: Module 'CPUID' power on failed.
2019-01-19T22:04:25.119Z - error: Progress Controller: [VCSA ERROR] - Details Fault cause: vim.fault.InvalidState
2019-01-19T22:04:25.125Z - info: Cancelling the ping timer for session mgmt
2019-01-19T22:04:25.126Z - info: Cancelling the ping timer for session mgmt
2019-01-19T22:04:25.146Z - info: ovfProcess child process exited with code 1
2019-01-19T22:12:34.554Z - info: Log file was saved at: C:\Users\bmahmoud\Downloads\logs-installer-20190120-003748205

1 Solution

Accepted Solutions
bmahmoud
Enthusiast
Enthusiast

mike ,

i have got all answers. finally  my vcenter is working fine..

ERROR: Task failed on server: Module ‘CPUID’ power on failed    ,,, its beacuse  the resurces  are n...

on vcenter page  y i could not able to login because  the  only platform services were installed properly  and the other services (vcenter) was not fully installed.it seems it installed but actually it was not.

thanks for your support.  Smiley Happy

View solution in original post

0 Kudos
18 Replies
MikeStoica
Expert
Expert

For VCSA you don't need to create a VM, it will be automatically created when running the installer. The other machine that you installed were you able to power it on?

bmahmoud
Enthusiast
Enthusiast

in my scenario  I have one EXSI 6.5 running on Dell hardware and  four vms are already running on it. what I did . For VSCA installation I created another VM inside same EXSI and install eXSI 6.5 on

it and assign a static IP on it . now from my laptop i run the VCSA setup and it ask me destination  IP where i need to install  VCSA i gave  that newly installed VCSA machine ip  and every thing going smooth up to 80%  and after that it gave me error. i have  posted above. i m unable to understand  this error.

Task failed on server: Module 'CPUID' power on failed.

Fault cause: vim.fault.InvalidState

Installer log files are located at C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller

Installer log files are located at C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller

now you mean I must give the original Exsi IP during installation and it will automatically create a machine inside it and install VCSA on it ?

please confirm me

0 Kudos
bmahmoud
Enthusiast
Enthusiast

MIke ,

I have run the setup on the original EXSI Machine and as you told it automatically created new VM   , and on reaching  80% it did not give me error but stucked and showing  "waiting for RPM Installation To start .this may take  several minutes"

till now it being 20 minutes to wait. is it normal ??

0 Kudos
MikeStoica
Expert
Expert

It should not stay that long. Please follow the steps from this post vSphere 6.7 install vCSA 6.7 - pt.1 • Nolabnoparty

0 Kudos
bmahmoud
Enthusiast
Enthusiast

DEar Mike,

I follow the instruction but now it gave me below error

A problem occurred during RPM installation: Timeout

Installer log files are located at C:\Users\bmahmoud\AppData\Local\Temp\vcsaUiInstaller

i did  the following steps.

1-i added the A record with PRT in my DNS . ip which i wanted to give VCSA and name which i gave to VCSA

2 i run the installer.exe from my laptop.

3- it as me for my EXSI machine ip and root password. i supplied the creditional.

4-as me for VCSA VM name. i provide the same name which i  entered in DNS. WITH FDQN . and same IP against this FDQN

5- setup started and reached 80 % and  then hanged  there for long time and give me  above error.

please suggest what should i do or where i m doing mistake.

i have attached the logs if it helpful.

0 Kudos
MikeStoica
Expert
Expert

What license do you have? found this in your logs Current license or ESXi version prohibits execution of the requested operation

0 Kudos
bmahmoud
Enthusiast
Enthusiast

hi mike,

i have installed  VCSA on separate machine instead of nested . and it installed properly. it just finished installation  let me check the  interfaces  everything is ok  and i will get back to you and let you know my experience

0 Kudos
bmahmoud
Enthusiast
Enthusiast

mike

below is the page appearing. I cannot login to vcsa  page by sso.

but I can login appliance page

https://vcsa-6.5.x.x.x:5480/ui/summary

please suggests

You've reached a Platform Services Controller.

The Platform Services Controller web interface is now integrated as a plugin in the vsphere Client (HTML5).
Please go to the Administration section in the vSphere Client (HTML5)
to manage the vCenter Single Sign-On and the certificates.

To access a vCenter Server node, use the URL https://<vc_fqdn_or_ip>

For help, see the

Platform Services Controller documentation

0 Kudos
MikeStoica
Expert
Expert

You should be able to login in vCenter using administrator@vsphere.local (in case you configured the SSO name as vsphere.local)

0 Kudos
bmahmoud
Enthusiast
Enthusiast

mike,

this is my ssol domain name.  :  https://vcsa-6.5.local/

when I open this link  instead of asking any username password prompt  it gave me below  messages

You've reached a Platform Services Controller.

The Platform Services Controller web interface is now integrated as a plugin in the vsphere Client (HTML5).
Please go to the Administration section in the vSphere Client (HTML5)
to manage the vCenter Single Sign-On and the certificates.

To access a vCenter Server node, use the URL https://<vc_fqdn_or_ip>

For help, see the

Platform Services Controller documentation

what does it mean   ..  vc_fdqn or ip…..

I tried mmy vcsa IP and  above mentioned link ..I get same  message  described above

0 Kudos
MikeStoica
Expert
Expert

Can you post some screenshots?

bmahmoud
Enthusiast
Enthusiast

Mike,

Below are screen shots it will be helpful in resolving issues.

pastedImage_0.png

============================================================================================================

pastedImage_1.png

===============================================================================================

pastedImage_3.png

0 Kudos
MikeStoica
Expert
Expert

That's strange. When I'm accessing my vcenter IP I get this:

pastedImage_0.png

MikeStoica
Expert
Expert

You deployed the PSC and vCenter on the same server?

0 Kudos
bmahmoud
Enthusiast
Enthusiast

vcenter is on different machine.

its not nested .because  on nested model it dnt  allow me to install. so choose  the second option tab 1.

what should i do now ?  i was also supposed to have the same page but it failed i tried through different machines.

0 Kudos
bmahmoud
Enthusiast
Enthusiast

can you give me vpshere client  for VCSA  to acess it? if it is available

0 Kudos
bmahmoud
Enthusiast
Enthusiast

mike ,

i have got all answers. finally  my vcenter is working fine..

ERROR: Task failed on server: Module ‘CPUID’ power on failed    ,,, its beacuse  the resurces  are n...

on vcenter page  y i could not able to login because  the  only platform services were installed properly  and the other services (vcenter) was not fully installed.it seems it installed but actually it was not.

thanks for your support.  Smiley Happy

View solution in original post

0 Kudos
tharakal
Contributor
Contributor

Assing license your ESXi host. now are  working fine :smileycool: :smileysilly:

0 Kudos