ESXi 4.0 and VMs extremely slow
Hey there.
I installed an ESXi 4.0.0 Build 208167 with German-000 just a few months, there is and he worked there with a normal return (please).
Well, last week, the virtual machines have become performance issues. As an example, windows Explorer takes only a few moments to appear like other tasks such as closing windows systems, or create on SLES11 xterm windows.
I tried to restart my system, but with this, I got new problems: some virtual machines cannot start or became disabled (appears under the name VM and (invalid) appended to the virtual machine).
I try to start other systems, press play and the machine seems to have started, but it remains on 95% for a minute and then, it appears a message called: "the attempted operation is not in the current state (off) happen."
My diary in the var (last lines)
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:15 vmkernel: 0:15:19:26.677 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:15 vmkernel: 0:15:19:26.677 cpu6:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:15 vmkernel: 0:15:19:26.815 cpu6:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu14:4334) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu14:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:17 vmkernel: 0:15:19:28.790 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:17 vmkernel: 0:15:19:28.790 cpu6:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:17 vmkernel: 0:15:19:28.945 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:18 vmkernel: 0:15:19:29.069 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.319 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.319 cpu2:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:26 vmkernel: 0:15:19:37.456 cpu2:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu2:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu2:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu1:4363) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu11:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu11:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:28 vmkernel: 0:15:19:39.437 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:28 vmkernel: 0:15:19:39.437 cpu14:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:28 vmkernel: 0:15:19:39.581 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:28 vmkernel: 0:15:19:39.704 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:35 vmkernel: 0:15:19:46.078 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:35 vmkernel: 0:15:19:46.078 cpu14:4328) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:35 vmkernel: 0:15:19:46.078 cpu14:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:36 vmkernel: 0:15:19:47.936 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:36 vmkernel: 0:15:19:47.936 cpu14:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:37 vmkernel: 0:15:19:48.085 cpu14:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:37 vmkernel: 0:15:19:48.208 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:37 vmkernel: 0:15:19:48.208 cpu2:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu2:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu14:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:39 vmkernel: 0:15:19:50.066 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:39 vmkernel: 0:15:19:50.066 cpu4:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:39 vmkernel: 0:15:19:50.216 cpu4:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:39 vmkernel: 0:15:19:50.339 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.547 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.547 cpu4:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:47 vmkernel: 0:15:19:58.739 cpu4:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu4:4337) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu4:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu1:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:47 vmkernel: 0:15:19:58.863 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:49 vmkernel: 0:15:20:00.719 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:49 vmkernel: 0:15:20:00.720 cpu0:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:49 vmkernel: 0:15:20:00.869 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:49 vmkernel: 0:15:20:00.992 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.242 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.242 cpu4:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:58 vmkernel: 0:15:20:09.385 cpu4:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu2:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu2:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23 vmkernel: 0:15:20:11.367 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23 vmkernel: 0:15:20:11.367 cpu8:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23 vmkernel: 0:15:20:11.516 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23 vmkernel: 0:15:20:11.639 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:08 vmkernel: 0:15:20:19.877 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:08 vmkernel: 0:15:20:19.877 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:09 vmkernel: 0:15:20:20.026 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu8:4332) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu4:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu4:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:11 vmkernel: 0:15:20:22.008 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:11 vmkernel: 0:15:20:22.008 cpu2:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:11 vmkernel: 0:15:20:22.157 cpu2:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:11 vmkernel: 0:15:20:22.281 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.512 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.512 cpu2:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:19 vmkernel: 0:15:20:30.650 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:19 vmkernel: 0:15:20:30.773 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.773 cpu0:4325) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:19 vmkernel: 0:15:20:30.773 cpu0:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:19 vmkernel: 0:15:20:30.774 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.774 cpu6:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:19 vmkernel: 0:15:20:30.774 cpu6:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:21 vmkernel: 0:15:20:32.625 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:21 vmkernel: 0:15:20:32.625 cpu2:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:21 vmkernel: 0:15:20:32.780 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:21 vmkernel: 0:15:20:32.904 cpu14:5140) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.148 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.148 cpu1:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:30 vmkernel: 0:15:20:41.285 cpu1:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu0:4329) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:32 vmkernel: 0:15:20:43.260 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:32 vmkernel: 0:15:20:43.260 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:32 vmkernel: 0:15:20:43.410 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:32 vmkernel: 0:15:20:43.533 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:40 vmkernel: 0:15:20:51.759 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:40 vmkernel: 0:15:20:51.759 cpu1:4325) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:40 vmkernel: 0:15:20:51.908 cpu1:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu6:4326) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu6:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:42 vmkernel: 0:15:20:53.883 cpu14:5040) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:42 vmkernel: 0:15:20:53.883 cpu6:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:43 vmkernel: 0:15:20:54.027 cpu6:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:43 vmkernel: 0:15:20:54.150 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.370 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.370 cpu4:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:51 vmkernel: 0:15:21:02.513 cpu4:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4331) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4324) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:53 vmkernel: 0:15:21:04.489 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:53 vmkernel: 0:15:21:04.489 cpu12:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:53 vmkernel: 0:15:21:04.638 cpu12:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:53 vmkernel: 0:15:21:04.762 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:12.999 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:12.999 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:02 vmkernel: 0:15:21:13.131 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:02 vmkernel: 0:15:21:13.254 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:13.254 cpu12:4332) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:02 vmkernel: 0:15:21:13.254 cpu12:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:02 vmkernel: 0:15:21:13.255 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:13.255 cpu8:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:02 vmkernel: 0:15:21:13.255 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:04 vmkernel: 0:15:21:15.112 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:04 vmkernel: 0:15:21:15.112 cpu6:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:04 vmkernel: 0:15:21:15.249 cpu6:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:04 vmkernel: 0:15:21:15.373 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:11 pass: Activation N5Vmomi10ActivationE:0x5b3c7ea8 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
23 Feb 07:24:11 pass: Arg version: '111 '.
23 Feb 07:24:11 pass: throw vmodl.fault.RequestCanceled
23 Feb 07:24:11 pass: result: (vmodl.fault.RequestCanceled) {dynamicType = < unset >, faultCause = (vmodl. {MethodFault) null, msg = "",}
23 Feb 07:24:11 pass: PendingRequest: HTTP Transaction failed, closes the connection: N7Vmacore15SystemExceptionE (connection reset by peer)
23 Feb 07:24:12 vmkernel: 0:15:21:23.622 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:12 vmkernel: 0:15:21:23.622 cpu0:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:12 vmkernel: 0:15:21:23.820 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:12 vmkernel: 0:15:21:23.943 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:12 vmkernel: 0:15:21:23.944 cpu8:4334) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:21 vmkernel: 0:15:21:32.199 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:21 vmkernel: 0:15:21:32.199 cpu8:4338) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:21 vmkernel: 0:15:21:32.342 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu6:4324) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu6:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu2:4331) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu2:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:23 vmkernel: 0:15:21:34.323 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:23 vmkernel: 0:15:21:34.323 cpu8:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:23 vmkernel: 0:15:21:34.467 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:23 vmkernel: 0:15:21:34.590 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:31 vmkernel: 0:15:21:42.822 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:31 vmkernel: 0:15:21:42.822 cpu8:4328) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:31 vmkernel: 0:15:21:42.971 cpu8:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu8:4332) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu2:4327) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:32 vmkernel: 0:15:21:43.096 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:33 vmkernel: 0:15:21:44.953 cpu14:6103) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:33 vmkernel: 0:15:21:44.953 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:34 vmkernel: 0:15:21:45.078 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:34 vmkernel: 0:15:21:45.202 cpu14:6103) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.433 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.433 cpu2:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:42 vmkernel: 0:15:21:53.583 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:42 vmkernel: 0:15:21:53.706 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.706 cpu0:4331) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:44 vmkernel: 0:15:21:55.558 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:44 vmkernel: 0:15:21:55.558 cpu2:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:44 vmkernel: 0:15:21:55.695 cpu2:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:44 vmkernel: 0:15:21:55.819 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.128 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.128 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:53 vmkernel: 0:15:22:04.284 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:53 vmkernel: 0:15:22:04.407 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.407 cpu2:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:55 vmkernel: 0:15:22:06.265 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:55 vmkernel: 0:15:22:06.265 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:55 vmkernel: 0:15:22:06.414 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:55 vmkernel: 0:15:22:06.538 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.645 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.645 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:01 vmkernel: 0:15:22:12.794 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu14:5192) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu2:4327) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu14:5192) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:03 vmkernel: 0:15:22:14.769 cpu14:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:03 vmkernel: 0:15:22:14.770 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:03 vmkernel: 0:15:22:14.907 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:04 vmkernel: 0:15:22:15.031 cpu14:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.268 cpu14:5138) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.268 cpu3:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:12 vmkernel: 0:15:22:23.411 cpu3:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:12 vmkernel: 0:15:22:23.535 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.535 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu4:4325) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu4:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:14 vmkernel: 0:15:22:25.387 cpu14:5040) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:14 vmkernel: 0:15:22:25.387 cpu3:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:14 vmkernel: 0:15:22:25.536 cpu3:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:14 vmkernel: 0:15:22:25.660 cpu14:5040) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:22 vmkernel: 0:15:22:33.873 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:22 vmkernel: 0:15:22:33.873 cpu1:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:23 vmkernel: 0:15:22:34.023 cpu1:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu3:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu3:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu0:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:23 vmkernel: 0:15:22:34.148 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:24 vmkernel: 0:15:22:35.998 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:24 vmkernel: 0:15:22:35.998 cpu8:4328) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:25 vmkernel: 0:15:22:36.154 cpu8:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:25 vmkernel: 0:15:22:36.278 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.402 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.402 cpu1:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:31 vmkernel: 0:15:22:42.545 cpu1:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:31 vmkernel: 0:15:22:42.669 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.669 cpu8:4333) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:31 vmkernel: 0:15:22:42.669 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:31 vmkernel: 0:15:22:42.670 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.670 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:31 vmkernel: 0:15:22:42.670 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:33 vmkernel: 0:15:22:44.520 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:33 vmkernel: 0:15:22:44.520 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:33 vmkernel: 0:15:22:44.670 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:33 vmkernel: 0:15:22:44.794 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.037 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.037 cpu0:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:42 vmkernel: 0:15:22:53.180 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:42 vmkernel: 0:15:22:53.304 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.304 cpu2:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu2:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu2:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu2:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:44 vmkernel: 0:15:22:55.156 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:44 vmkernel: 0:15:22:55.156 cpu2:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:44 vmkernel: 0:15:22:55.305 cpu2:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:44 vmkernel: 0:15:22:55.429 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.660 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.660 cpu1:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:52 vmkernel: 0:15:23:03.804 cpu1:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu2:4336) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu2:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:54 vmkernel: 0:15:23:05.779 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:54 vmkernel: 0:15:23:05.779 cpu8:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:54 vmkernel: 0:15:23:05.928 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:55 vmkernel: 0:15:23:06.052 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.117 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.117 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:01 vmkernel: 0:15:23:12.254 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu1:4327) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu1:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:03 vmkernel: 0:15:23:14.229 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:03 vmkernel: 0:15:23:14.230 cpu0:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:03 vmkernel: 0:15:23:14.409 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:03 vmkernel: 0:15:23:14.533 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:11 vmkernel: 0:15:23:22.776 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:11 vmkernel: 0:15:23:22.776 cpu2:4325) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:11 vmkernel: 0:15:23:22.931 cpu2:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:13 vmkernel: 0:15:23:24.913 cpu5:185904) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:13 vmkernel: 0:15:23:24.913 cpu8:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:14 vmkernel: 0:15:23:25.062 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:14 vmkernel: 0:15:23:25.186 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.423 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.423 cpu6:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:22 vmkernel: 0:15:23:33.560 cpu6:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu5:6088) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu5:6088) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:24 vmkernel: 0:15:23:35.542 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:24 vmkernel: 0:15:23:35.542 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:24 vmkernel: 0:15:23:35.685 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:24 vmkernel: 0:15:23:35.809 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:30 vmkernel: 0:15:23:41.922 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:30 vmkernel: 0:15:23:41.922 cpu6:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:31 vmkernel: 0:15:23:42.059 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:31 vmkernel: 0:15:23:42.183 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:31 vmkernel: 0:15:23:42.183 cpu0:4327) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:31 vmkernel: 0:15:23:42.183 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:31 vmkernel: 0:15:23:42.184 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:31 vmkernel: 0:15:23:42.184 cpu0:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:31 vmkernel: 0:15:23:42.184 cpu4:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:33 vmkernel: 0:15:23:44.040 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:33 vmkernel: 0:15:23:44.040 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:33 vmkernel: 0:15:23:44.190 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:33 vmkernel: 0:15:23:44.314 cpu5:6087) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.569 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.569 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:41 vmkernel: 0:15:23:52.718 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu0:4325) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu0:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu2:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:41 vmkernel: 0:15:23:52.844 cpu2:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:43 vmkernel: 0:15:23:54.699 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:43 vmkernel: 0:15:23:54.699 cpu10:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:43 vmkernel: 0:15:23:54.903 cpu10:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:44 vmkernel: 0:15:23:55.027 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.258 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.258 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:52 vmkernel: 0:15:24:03.395 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu14:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu14:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:54 vmkernel: 0:15:24:05.377 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:54 vmkernel: 0:15:24:05.377 cpu10:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:54 vmkernel: 0:15:24:05.514 cpu10:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:54 vmkernel: 0:15:24:05.638 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27 vmkernel: 0:15:24:11.733 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27 vmkernel: 0:15:24:11.733 cpu0:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27 vmkernel: 0:15:24:11.888 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu5:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4327) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu5:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4331) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:02 vmkernel: 0:15:24:13.869 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:02 vmkernel: 0:15:24:13.869 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:03 vmkernel: 0:15:24:14.013 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:03 vmkernel: 0:15:24:14.137 cpu5:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.392 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.392 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:11 vmkernel: 0:15:24:22.541 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4326) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:13 vmkernel: 0:15:24:24.516 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:13 vmkernel: 0:15:24:24.516 cpu10:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:13 vmkernel: 0:15:24:24.660 cpu10:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:13 vmkernel: 0:15:24:24.784 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.015 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.015 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:22 vmkernel: 0:15:24:33.158 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu10:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu10:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu2:4324) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu2:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:24 vmkernel: 0:15:24:35.134 cpu5:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:24 vmkernel: 0:15:24:35.134 cpu1:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:24 vmkernel: 0:15:24:35.295 cpu1:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:24 vmkernel: 0:15:24:35.419 cpu5:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.507 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.507 cpu0:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:30 vmkernel: 0:15:24:41.675 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:30 vmkernel: 0:15:24:41.799 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.799 cpu6:4331) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:30 vmkernel: 0:15:24:41.799 cpu6:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:30 vmkernel: 0:15:24:41.800 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.800 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:30 vmkernel: 0:15:24:41.800 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:32 vmkernel: 0:15:24:43.650 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:32 vmkernel: 0:15:24:43.650 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:32 vmkernel: 0:15:24:43.793 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:32 vmkernel: 0:15:24:43.918 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.137 cpu11:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.137 cpu6:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:41 vmkernel: 0:15:24:52.280 cpu6:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu11:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu6:4326) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu6:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu11:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu14:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:42 pass: created task: haTask-304 - vim.VirtualMachine.powerOn - 306
23 Feb 07:27:42 pass: 2010-02-23 07:27:42.209 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' power on request received
23 Feb 07:27:51 vmkernel: 0:15:25:02.742 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:51 vmkernel: 0:15:25:02.742 cpu0:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:51 vmkernel: 0:15:25:02.891 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:52 vmkernel: 0:15:25:03.016 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:52 vmkernel: 0:15:25:03.016 cpu6:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:52 vmkernel: 0:15:25:03.016 cpu6:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:52 vmkernel: 0:15:25:03.017 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:52 vmkernel: 0:15:25:03.017 cpu0:4326) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:52 vmkernel: 0:15:25:03.017 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:53 vmkernel: 0:15:25:04.873 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:53 vmkernel: 0:15:25:04.873 cpu0:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:54 vmkernel: 0:15:25:05.022 cpu0:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:54 vmkernel: 0:15:25:05.147 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.246 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.246 cpu0:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28 vmkernel: 0:15:25:11.390 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu2:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu2:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu6:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu6:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:02 vmkernel: 0:15:25:13.365 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:02 vmkernel: 0:15:25:13.365 cpu8:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:02 vmkernel: 0:15:25:13.556 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:02 vmkernel: 0:15:25:13.681 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:10 vmkernel: 0:15:25:21.924 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:10 vmkernel: 0:15:25:21.924 cpu0:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:11 vmkernel: 0:15:25:22.067 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu14:4328) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu14:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:13 vmkernel: 0:15:25:24.042 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:13 vmkernel: 0:15:25:24.042 cpu0:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:13 vmkernel: 0:15:25:24.186 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:13 vmkernel: 0:15:25:24.310 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:20 pass: HostCtl Exception when the collection of statistics: SysinfoException: node (VSI_NODE_sched_cpuClients_numVcpus); (Bad0001) status = failure; Message = Instance (1): 0 Input (0)
23 Feb 07:28:21 vmkernel: 0:15:25:32.529 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:21 vmkernel: 0:15:25:32.529 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:21 vmkernel: 0:15:25:32.672 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu0:4326) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu14:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:23 vmkernel: 0:15:25:34.653 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:23 vmkernel: 0:15:25:34.653 cpu2:4325) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:23 vmkernel: 0:15:25:34.815 cpu2:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:30 vmkernel: 0:15:25:41.045 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:30 vmkernel: 0:15:25:41.045 cpu0:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:30 vmkernel: 0:15:25:41.195 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:30 vmkernel: 0:15:25:41.319 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:30 vmkernel: 0:15:25:41.319 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu6:4326) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu6:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:32 vmkernel: 0:15:25:43.176 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:32 vmkernel: 0:15:25:43.176 cpu9:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:32 vmkernel: 0:15:25:43.325 cpu9:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:32 vmkernel: 0:15:25:43.450 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu2:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:40 vmkernel: 0:15:25:51.710 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:40 vmkernel: 0:15:25:51.711 cpu6:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:40 vmkernel: 0:15:25:51.848 cpu6:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu9:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu9:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu6:4325) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu6:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:42 vmkernel: 0:15:25:53.829 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:42 vmkernel: 0:15:25:53.829 cpu6:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:43 vmkernel: 0:15:25:54.044 cpu6:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:43 vmkernel: 0:15:25:54.169 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.400 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.400 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:51 vmkernel: 0:15:26:02.531 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu9:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu9:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu6:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu6:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:52 vmkernel: 0:15:26:03.467 cpu4:68711) megasas: sn 352358 cmd = 0 x 28 attempts ABORT = tmo 0 = 0
23 Feb 07:28:52 vmkernel: 0:15:26:03.467 cpu4:68711) < 5 > 0: megasas: RESET 352358 cmd = 28 attempts sn = 0
23 Feb 07:28:53 vmkernel: 0:15:26:04.512 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:54 vmkernel: 0:15:26:05.491 cpu0:68711) megasas < 5 >: successful reset
23 Feb 07:29:02 vmkernel: 0:15:26:12.999 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:02 vmkernel: 0:15:26:12.999 cpu14:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:02 vmkernel: 0:15:26:13.136 cpu14:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu12:4334) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu12:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:04 vmkernel: 0:15:26:15.117 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:04 vmkernel: 0:15:26:15.117 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:04 vmkernel: 0:15:26:15.261 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:04 vmkernel: 0:15:26:15.386 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.616 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.616 cpu0:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:12 vmkernel: 0:15:26:23.754 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu0:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu8:4332) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:12 vmkernel: 0:15:26:23.995 cpu0:190779) megasas: ABORT sn 352531 cmd = attempts 0x2a = tmo 0 = 0
23 Feb 07:29:12 vmkernel: 0:15:26:23.995 cpu0:190779) < 5 > 0: megasas: RESET sn 352531 cmd = attempts 2 a = 0
23 Feb 07:29:14 vmkernel: 0:15:26:25.735 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.293 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.293 cpu12:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:23 vmkernel: 0:15:26:34.442 cpu12:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:23 vmkernel: 0:15:26:34.567 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.567 cpu1:4337) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu1:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu4:4363) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu8:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:25 vmkernel: 0:15:26:36.424 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:25 vmkernel: 0:15:26:36.424 cpu2:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:25 vmkernel: 0:15:26:36.574 cpu2:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:25 vmkernel: 0:15:26:36.699 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:32 pass: 2010-02-23 07:29:32.555 verbose 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas03/petas03.vmx" unknown unexpected toolsVersionStatus, use status offline guestToolsCurrent
23 Feb 07:29:32 pass: 2010-02-23 07:29:32.562 verbose 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" unknown unexpected toolsVersionStatus, use status offline guestToolsCurrent
23 Feb 07:29:32 pass: 2010-02-23 07:29:32.568 verbose 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx" unknown unexpected toolsVersionStatus, use status offline guestToolsCurrent
23 Feb 07:29:34 vmkernel: 0:15:26:45.030 cpu4:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:34 vmkernel: 0:15:26:45.030 cpu12:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:34 vmkernel: 0:15:26:45.161 cpu12:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:34 pass: created task: haTask-80 - vim.VirtualMachine.powerOn - 315
23 Feb 07:29:34 spend: 2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' power on request received
23 Feb 07:29:34 spend: 2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' ethernet reconfigures protective is required
23 Feb 07:29:34 pass: 257 of the event: petas01 on the RTHUS7002.rintra.ruag.com ha-Data Center host begins
23 Feb 07:29:34 spend: 2010-02-23 07:29:34.173 1680BB90 info 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
23 Feb 07:29:34 vmkernel: 0:15:26:45.286 cpu4:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.635 cpu4:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.635 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:44 vmkernel: 0:15:26:55.785 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu4:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu4:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu6:4329) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:46 vmkernel: 0:15:26:57.766 cpu4:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:46 vmkernel: 0:15:26:57.766 cpu0:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:46 vmkernel: 0:15:26:57.915 cpu0:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:47 vmkernel: 0:15:26:58.040 cpu4:4363) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.276 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.276 cpu6:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:55 vmkernel: 0:15:27:06.414 cpu6:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:55 vmkernel: 0:15:27:06.539 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.539 cpu2:4324) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:55 vmkernel: 0:15:27:06.539 cpu2:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:55 vmkernel: 0:15:27:06.540 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.540 cpu4:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:55 vmkernel: 0:15:27:06.540 cpu4:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:57 vmkernel: 0:15:27:08.395 cpu1:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:57 vmkernel: 0:15:27:08.395 cpu3:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:57 vmkernel: 0:15:27:08.538 cpu3:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:57 vmkernel: 0:15:27:08.664 cpu1:190710) megasas_service_aen < 6 > [6]: NEA received
And then there is my hostd.log
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': open with success (21) size = 53687091200, hd = 0. Type 3
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': closed.
Reminder of Foundry recorded on 4
Reminder of Foundry recorded on 17
Reminder of Foundry recorded on 5
Reminder of Foundry recorded on 11
Reminder of Foundry recorded on 12
Reminder of Foundry recorded 13
Reminder of Foundry recorded on 14
Reminder of Foundry recorded on 15
Reminder of Foundry recorded 26
Reminder of Foundry saved on 16
2010-02-23 06:52:24.922 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Lack of recall tolerance status received
2010-02-23 06:52:24.922 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Record/replay reminder of the State received
2010-02-23 06:52:24.922 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 5, 2
2010-02-23 06:52:24.922 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" The State of Transition (VM_STATE_INITIALIZING-> VM_STATE_OFF)
Cannot find the content reflected in extended config xml.
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': open with success (21) size = 53687091200, hd = 0. Type 3
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': closed.
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': open success (23) size = 53687091200, hd = 0. Type 3
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': closed.
2010-02-23 06:52:35.532 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Version initial tools: 3:guestToolsNotInstalled
2010-02-23 06:52:35.532 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Overhead VM predicted: 118587392 bytes
2010-02-23 06:52:35.532 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Initialized virtual machine.
ModeMgr::End: op = current, normal = normal, count = 2
Task completed: success of haTask-ha-folder-vm-vim.Folder.createVm-243 status
Event 244: Created the virtual machine on RTHUS7002.rintra.ruag.com ha-data center
2010-02-23 06:52:35.533 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Create worker thread successfully completed
2010-02-23 06:52:35.539 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
The task was created: haTask-320 - vim.VirtualMachine.powerOn - 246
2010-02-23 06:52:53.868 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Power on request received
2010-02-23 06:52:53.868 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Reconfigure the ethernet support if necessary
Event 245: app-back-05-neu on host RTHUS7002.rintra.ruag.com ha-data center begins
2010-02-23 06:52:53.868 info 5B168B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 1
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 06:52:53.899 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' PowerOn request queue
2010-02-23 06:52:53.913 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 7, 6
/VM/ #1dea389a74a8b231 /: VMHSVMCbPower: status of the VM powerOn with option soft
2010-02-23 06:52:53.913 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 190710
2010-02-23 06:52:53.965 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" An established connection.
Airfare to CIMOM version 1.0, root user
2010-02-23 06:53:20.200 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Paths on the virtual machine of mounting connection: /db/connection / #14bc.
2010-02-23 06:53:20.248 5B1EAB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' No upgrade required
2010-02-23 06:53:20.253 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Completion of Mount VM for vm.
2010-02-23 06:53:20.254 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Mount VM Complete: OK
Airfare to CIMOM version 1.0, root user
2010-02-23 06:54:45.556 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' MKS ready for connections: true
2010-02-23 06:54:45.556 info 1688CB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Information request: insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1176 x 885 to 16 bits per pixel. To use the configured maximum resolution of 2360 x 1770 to 16 bits per pixel, increase the amount of video memory allocated to this virtual machine by setting svga.vramSize = "16708800" in the virtual machine configuration file.
Id: 0: Type: 2, default: 0, number of options: 1
2010-02-23 06:54:45.556 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:54:45.556 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' No upgrade required
2010-02-23 06:54:45.556 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 7, 6
VixVM_AnswerMessage returned 0
2010-02-23 06:54:45.562 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:54:45.562 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 7, 6
Event 246: Message on app-back-05-neu on RTHUS7002.rintra.ruag.com ha-Datacenter: insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1176 x 885 to 16 bits per pixel. To use the configured maximum resolution of 2360 x 1770 to 16 bits per pixel, increase the amount of video memory allocated to this virtual machine by setting svga.vramSize = "16708800" in the virtual machine configuration file.
2010-02-23 06:54:45.562 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Auto-répondu insufficient video RAM issue. The maximum resolution of the virtual machine will be limited to 1176 x 885 to 16 bits per pixel. To use the configured maximum resolution of 2360 x 1770 to 16 bits per pixel, increase the amount of video memory allocated to this virtual machine by setting svga.vramSize = "16708800" in the virtual machine configuration file.
2010-02-23 06:55:26.096 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' State of the Tools version: noTools
2010-02-23 06:55:26.096 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" VMX status has been defined.
2010-02-23 06:55:26.097 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:55:26.097 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' The event of Imgcust read vmdb tree values State = 0, errorCode = 0, errorMsgSize = 0
2010-02-23 06:55:26.097 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:55:26.097 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Tools running status changed to: keep
2010-02-23 06:55:41.030 info 1698FB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Connected to testAutomation-fd, sent remotely end pid: 190710
2010-02-23 06:55:41.032 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 4, 8
2010-02-23 06:55:41.034 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' No upgrade required
247 event: app-back-05-neu on RTHUS7002.rintra.ruag.com ha-data center power is on
2010-02-23 06:55:41.036 info 5B0E6B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" The State of Transition (VM_STATE_POWERING_ON-> VM_STATE_ON)
Change of State received for VM ' 320'
2010-02-23 06:55:41.065 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Actual VM overhead: 88780800 bytes
2010-02-23 06:55:41.139 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Time to pick up some config: 73 (MS)
Task completed: success of status haTask-320 - vim.VirtualMachine.powerOn - 246
2010-02-23 06:55:43.211 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Time to pick up some config: 67 (MS)
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. Using English.
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. With the help of C.
Event 248: [email protected] user
2010-02-23 06:55:47.873 info 5B0E6B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 06:55:55.843 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 1
2010-02-23 06:56:00.279 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Actual VM overhead: 89305088 bytes
RefreshVms overhead to 1 VM update
Airfare to CIMOM version 1.0, root user
2010-02-23 06:56:40.293 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Actual VM overhead: 88829952 bytes
RefreshVms overhead to 1 VM update
Ability to root pool changed 18302 MHz / 43910MB at 18302 MHz / 43909MB
Airfare to CIMOM version 1.0, root user
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 224" failed.
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 224" failed.
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 240" failed.
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 240" failed.
Airfare to CIMOM version 1.0, root user
FetchDVPortgroups: added 0 items
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43909MB at 18302 MHz / 43908MB
2010-02-23 07:01:46.927 168CDB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:47.586 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petaw02/petaw02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:47.593 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petaw01/petaw01.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:48.412 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas03/petas03.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:48.418 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:48.425 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:50.707 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 0
The task was created: haTask-304 - vim.VirtualMachine.powerOn - 268
2010-02-23 07:01:52.340 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Power on request received
2010-02-23 07:01:52.340 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Reconfigure the ethernet support if necessary
Event 249: PETA-route on the RTHUS7002.rintra.ruag.com ha-Data Center host starts
2010-02-23 07:01:52.341 info 1680BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 2
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 07:01:59.118 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' PowerOn request queue
2010-02-23 07:02:00.513 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
Airfare to CIMOM version 1.0, root user
2010-02-23 07:02:07.643 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 7, 6
/VM/ #c27a9ee2a691ac1a /: VMHSVMCbPower: status of the VM powerOn with option soft
CloseSession called for the session id = 5206e96f - 88-2e3f-9187-60932847859f 0c
Rising with name = "haTask-304 - vim.VirtualMachine.powerOn - 129 ' failed.
GetPropertyProvider failed for haTask-304 - vim.VirtualMachine.powerOn - 129
Rising with name = "haTask-256 - vim.VirtualMachine.reset - 124 ' failed.
GetPropertyProvider failed for haTask-256 - vim.VirtualMachine.reset - 124
Event 250: Rzhmi_ope disconnected user
2010-02-23 07:02:24.668 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 192683
Rising with name = "haTask-ha-folder-vm-vim.Folder.createVm-243" failed.
Rising with name = "haTask-ha-folder-vm-vim.Folder.createVm-243" failed.
2010-02-23 07:02:58.683 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" An established connection.
Ability to root pool changed 18302 MHz / 43908MB at 18302 MHz / 43907MB
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43907MB in 18302 MHz / 43909MB
Airfare to CIMOM version 1.0, root user
Rising with name = "haTask-320 - vim.VirtualMachine.powerOn - 246" failed.
Rising with name = "haTask-320 - vim.VirtualMachine.powerOn - 246" failed.
FoundryVMDBPowerOpCallback: Op to VMDB reports power failed for VM /vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx with error msg = "the operation has timed out" and error code-41.
2010-02-23 07:06:02.208 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 5, 2
Have not power Op: error: (3006) the virtual machine must be turned on
2010-02-23 07:06:02.209 5B22BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" Failed operation
Event 251: Cannot power on PETA-router on RTHUS7002.rintra.ruag.com ha-data center. A general error occurred:
2010-02-23 07:06:02.209 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_POWERING_ON-> VM_STATE_OFF)
ModeMgr::End: op = current, normal = normal, count = 3
Task completed: error status haTask-304 - vim.VirtualMachine.powerOn - 268
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43909MB at 18302 MHz / 43906MB
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43906MB at 18302 MHz / 43908MB
Activation N5Vmomi10ActivationE:0x5b68a8b0 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
'93.
Launch vmodl.fault.RequestCanceled
{(vmodl.fault.RequestCanceled)
dynamicType = < unset >
faultCause = (vmodl. NULL in MethodFault),
MSG = ""
}
PendingRequest: HTTP Transaction failed, closes the connection: N7Vmacore15SystemExceptionE (connection reset by peer)
Ability to root pool changed 18302 MHz / 43908MB at 18302 MHz / 43909MB
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. Using English.
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. With the help of C.
Event 252: [email protected] user
2010-02-23 07:13:13.852 info 5B1EAB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 07:13:19.794 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 1
2010-02-23 07:14:18.185 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 0
Activation N5Vmomi10ActivationE:0x5c0f4dc0 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
« 3 »
CloseSession called for the session id = 528c7c0f-5bce-6ea5-CE22-e4927fab2c89
Launch vmodl.fault.RequestCanceled
{(vmodl.fault.RequestCanceled)
dynamicType = < unset >
faultCause = (vmodl. NULL in MethodFault),
MSG = ""
}
Event 253: Rzhmi_ope disconnected user
Error reading the client while you wait header: N7Vmacore15SystemExceptionE (connection reset by peer)
Error reading the client while you wait header: N7Vmacore15SystemExceptionE (connection reset by peer)
Error reading the client while you wait header: N7Vmacore15SystemExceptionE (connection reset by peer)
2010-02-23 07:14:20.843 info 1680BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 07:14:26.122 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 1
Airfare to CIMOM version 1.0, root user
Rising with name = "haTask-304 - vim.VirtualMachine.powerOn - 268 ' failed.
Rising with name = "haTask-304 - vim.VirtualMachine.powerOn - 268 ' failed.
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
CloseSession called for the session id = 520edca0-62aa - 19 c 8-8c9d-bd710bd6c882
Event in 254: Rzhmi_ope disconnected user
2010-02-23 07:19:01.520 5B0A5B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 0
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. Using English.
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. With the help of C.
Event 255: [email protected] user
2010-02-23 07:19:05.616 info 5B0E6B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Airfare for mks to user connections: rzhmi_ope
Airfare to CIMOM version 1.0, root user
2010-02-23 07:19:11.260 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 1
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
Activation N5Vmomi10ActivationE:0x5b3c7ea8 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
"111".
Launch vmodl.fault.RequestCanceled
{(vmodl.fault.RequestCanceled)
dynamicType = < unset >
faultCause = (vmodl. NULL in MethodFault),
MSG = ""
}
PendingRequest: HTTP Transaction failed, closes the connection: N7Vmacore15SystemExceptionE (connection reset by peer)
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
The task was created: haTask-304 - vim.VirtualMachine.powerOn - 306
2010-02-23 07:27:42.209 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Power on request received
2010-02-23 07:27:42.209 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Reconfigure the ethernet support if necessary
Event 256: PETA-route on the RTHUS7002.rintra.ruag.com ha-Data Center host starts
2010-02-23 07:27:42.210 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 2
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 07:27:49.686 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' PowerOn request queue
2010-02-23 07:27:58.217 1690EB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 7, 6
/VM/ #c27a9ee2a691ac1a /: VMHSVMCbPower: status of the VM powerOn with option soft
Airfare to CIMOM version 1.0, root user
2010-02-23 07:28:15.230 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 191945
HostCtl Exception while collecting statistics: SysinfoException: node (VSI_NODE_sched_cpuClients_numVcpus); (Bad0001) status = failure; Message = Instance (1): 0 Input (0)
2010-02-23 07:28:34.614 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' The Tools version state: ok
2010-02-23 07:28:34.616 168CDB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' MKS ready for connections: false
2010-02-23 07:28:34.660 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 0
2010-02-23 07:28:34.782 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 07:28:49.390 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" An established connection.
2010-02-23 07:29:04.550 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Overhead VM predicted: 143904768 bytes
RefreshVms overhead to 1 VM update
2010-02-23 07:29:29.573 verbose 1690EB90 ' vm: / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_Radius + Jg - CA/Test_Radius + Jg - CA.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:29:32.555 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas03/petas03.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:29:32.562 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:29:32.568 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
The task was created: haTask-80 - vim.VirtualMachine.powerOn - 315
2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Power on request received
2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Reconfigure the ethernet support if necessary
Event 257: petas01 on the RTHUS7002.rintra.ruag.com ha-Data Center host begins
2010-02-23 07:29:34.173 1680BB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 3
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 07:29:34.327 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' PowerOn request queue
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43909MB at 18302 MHz / 43910MB
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43910MB at 18302 MHz / 43909MB
HostCtl Exception while collecting statistics of network for vm 256: SysinfoException: node (VSI_NODE_net_openPorts_type); (Bad0001) status = failure; Message = cannot get Int
2010-02-23 07:31:52.964 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Current state recovered VM Foundry 7, 6
/VM/ #dd20eb79a599aa61 /: VMHSVMCbPower: status of the VM powerOn with option soft
2010-02-23 07:31:52.984 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 200813
FoundryVMDBPowerOpCallback: Op to VMDB reports power failed for VM /vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx with error msg = "the operation has timed out" and error code-41.
2010-02-23 07:31:52.985 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 5, 2
Have not power Op: error: (3006) the virtual machine must be turned on
2010-02-23 07:31:52.985 5B22BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" Failed operation
Event 258: Cannot power on PETA-router on RTHUS7002.rintra.ruag.com ha-data center. A general error occurred:
2010-02-23 07:31:52.986 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_POWERING_ON-> VM_STATE_OFF)
ModeMgr::End: op = current, normal = normal, count = 4
Task completed: error status haTask-304 - vim.VirtualMachine.powerOn - 306
vmdbPipe_Streams could not read: OVL_STATUS_EOF
2010-02-23 07:31:52.988 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' No upgrade required
2010-02-23 07:31:52.989 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Disconnect the current control.
2010-02-23 07:31:52.989 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Disassembly of the virtual machine.
2010-02-23 07:31:52.990 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" VMDB disassemble insiders.
2010-02-23 07:31:52.990 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" VM complete disassembly.
2010-02-23 07:31:53.000 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Mt. state values have changed.
2010-02-23 07:31:53.000 1680BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Failed to get resource for a motor home on VM settings
There is no worldId 4294967295 world
2010-02-23 07:31:53.001 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Mt. state values have changed.
2010-02-23 07:31:53.002 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Reloading configuration state.
2010-02-23 07:31:53.106 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" An established connection.
2010-02-23 07:32:24.650 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" Paths on the virtual machine of mounting connection: /db/connection/#158 d.
client closed connection detected recv
Intake automation detected ready for VM (/ vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx)
2010-02-23 07:32:24.709 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' No upgrade required
2010-02-23 07:32:24.720 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" Completion of Mount VM for vm.
2010-02-23 07:32:24.721 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" Mount VM Complete: OK
2010-02-23 07:32:24.777 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 31779 (MS)
2010-02-23 07:32:24.782 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Current state recovered VM Foundry 5, 2
2010-02-23 07:32:24.782 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Current state recovered VM Foundry 5, 2
2010-02-23 07:32:24.849 1690EB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:24.850 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Receipt Foundry power state update 5
2010-02-23 07:32:24.850 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" The State of Transition (VM_STATE_ON-> VM_STATE_OFF)
ModeMgr::End: op = current, normal = normal, count = 3
Change of State received for VM ' 256'
2010-02-23 07:32:24.850 5B22BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Could not find activation record, user unknown event.
Event 259: Std-Server on RTHUS7002.rintra.ruag.com ha-data center is turned off
2010-02-23 07:32:24.851 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Lack of recall tolerance status received
2010-02-23 07:32:24.851 5B0E6B90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Received a double transition of Foundry: 2, 0
2010-02-23 07:32:24.919 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 66 (MS)
Remove the vm 256 poweredOnVms list
2010-02-23 07:32:24.990 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 65 (MS)
2010-02-23 07:32:25.061 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 65 (MS)
2010-02-23 07:32:25.065 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' The event of Imgcust read vmdb tree values State = 0, errorCode = 0, errorMsgSize = 0
2010-02-23 07:32:25.066 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Tools running status changed to: keep
2010-02-23 07:32:25.066 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' State of the Tools version: unknown
2010-02-23 07:32:25.066 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' No upgrade required
2010-02-23 07:32:25.081 16A11B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:25.088 1698FB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:25.090 16A11B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:25.090 1698FB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
Airfare to CIMOM version 1.0, root user
My Server includes:
2 x Intel Xeon X 5550, 4 c/8 t 2.66 GHz, 8 MB
48 GB DDR3 RAM
12 HD SAS 3 g 146 GB 10 k HOT PLUG
-11 HD than RAID 5
-1 global hot spare
Anyone know more about these symptoms?
If it is a server supported (Dell, HP, IBM, etc.) the State of health of the host will be visible from the vSphere client (hardware status tab if managed vCentre, or the tab configuration, health if not).
Otherwise, you will need to get a diagnostic utility currently out of the manufacturer and use it.
Please give points for any helpful answer.
Tags: VMware
Similar Questions
-
HP 22-3160na touch screen: My AllinOne is new and its extremely slow and a lot of questions
Link to the product:http://store.HP.com/UKStore/merch/product.aspx?ID=P1K28EA&opt=Abu&SEL=DTP
I bought this PC on April 25, 2016 and so far, it's the worst PC I've owned in my life!
I made 3-4 comments on this trash and its still not on the UK site!
I don't know if its the terrible material or mine is just a faulty PC.
Questions:
1. my USB ports stop usually work (when I connect a device)
2. not a problem just a stupid thing made HP the HDMI is an output, which means that I can't connect to an output!
3. my PC often just freezes or gal
4. you could say "Your PC is riddled with virus" is not only 6 GB of storage was used and the only things I installed was autodesk, and google sketchup and steam and remote play and unity. I've done MANY anti virus scans using McAfee and AVG and there wasn't anything I uninstalled steam and everything and there is no difference my PC has been extremely slow.
5.i have the feeling that my ram is not working properly; I have 4 GB of ram but 3 GB usable but my PC normally stops when opening microsoft edge it stops just work and shifts.
6. When you exit an application on during a time and back to her he says just "not responding" every time!
7 Dissconectivty questions: I always disconnect from the internet when my wifi does not work. Not my wifi is fast so it should work, I checked my other device and it showed my wifi working this problem also applies to my HP printer all in one that still has a paper jam!
8 bad Proccesor: Please tell me I can replace it with a processor intel I5 - I7 skylake cause this Proccesor is a cheap AMD from £20 to 40 HP Proccesor please tell me if I can replace with this Proccesor:
9. useless graphics card: joke not but my brother can't play ROBLOX on smaller settings it is isn't a maximum of 16fps horribld? Well please tell me if I can replace it with a graphics card from Nvidia. These graphics cards will work? :
GTX - 660
770TI - GTX
-GTX 980 M (Fits in laptop computers do not see why not?)
AMD - 270 X
GTX - 1060
Or something better than that!
10. not a problem too, but a reccomendation: do not use a mirror as a screen, the screen is really bad its ok its TOO BRILLIANT just brilliant.
11. not a problem but a praise (only thing that I love) the sound quality is excellent but with the speakers to the front, but the caches are really ugly.
On UPGRADES:
Can I change the graphics cards above? If I can PLEASE tell me if I need to replace the power supply or not (of course that's a Yes)
Question: I have the warranty will be voided if I upgrade the RAM? Also is there only 1 slot for a 4 GB of ram? Because I want to pass this to 8 (or 16 if possible) of RAM also I am disappointed that it is a 800 MHZ RAM! If I update to a 8-16 GB 2133 Mhz RAM would it work or need a power supply higher?
Yes, you might think I want this for the games, but no, I have this PC for a long time so I don't want it to be obsolete in a few months and I use game engines so I need this upgrade due to the more advanced over time.
Sorry to be negative in some areas, but these are the options that I wish to have
1st choice:
-Intel I5 (in link above)
GTX - 750TI 4-6 GB
-8 GB 2133 MHZ RAM
-Tell me food if I need to change it.
2nd choice:
-Intel I5
-GTX 980M 4-6 GB
-16 GB 2133 MHz or 8 gb 2133 Mhz
-Tell me feeding please!
3rd choice:
the least possible but I can;
Intel I5 processor
GTX 1060 4-6 GB
-Tell me power!
Thank you very much for reading this! I could change mind about how the bad HP is. Please tell me recommendations how to
know if my PC is faulty or not or if it does not tell me how to acctually works.
Oh also can I change it for one SSD or SSHD?
Please tell me if these upgrades will work or not, or tell me another choice which can run top games settings regular 35-60 fps low - med (Cause I can't do high quality games using unity if my PC can't handle)
Thank you very much!
Note: I use my ipad because of my PC is slow...
Did you get this as a gift? Here is the care. With a modest 1.8 Ghz processor (welded) and a set of graphics, which is part of the CPU chip, and here is NO slot for a graphics card. Not possible to capacity except an increase in two modules of 8 GB RAM. It has a brick laptop to a power supply. What you have is a unit of basic inetrnet/e-mail.
In my humble OPINION, it should never be your waiting. Then, I thought that you have been pranking, but you're a Brit, so I stopped short.
-
ESXi 5.1 VM running extremely slow after a power failure
Help, our virtual machines are run at a crawl since a power outage a few days ago. Everything seems to be in good shape.
Host is DL385 G7, 12 Dual core AMD, 48 GB memory, data store local storage (4) SAS 600 GB is running in RAID 10 for a total of 1.2 GB
Where I even begin to start looking?
4 critical VM:
Domain controller - Server 2008
SQL Server - 2008 Server
Terminal Server - Server 2008 R2
Mail Gateway - Windows 7
3 other various OS VM:
Windows XP
Server 2008
Linux power virtual management appliance base.
I turned off these 3 for now hoping to free up resources (doesn't help anything).
Memory and CPU use is nothing more than normal. It is sufficient that the virtual machine is so slow to the point where they are almost unusable (block-by-block refresh screens)
Each client computer is a thin client, and they often lose communication for 10-20 seconds each time, I do not know due to timeouts.
If the screenshots of the content of the folder of the virtual machine, or anything else would be helpful, let me know.
Hello
Everything seems to be in good shape.
Check the status tab material on the host and the status of all sensors...
On a host that unmanaged-> Configuration tab - > material - > health
Then, you can take a look at log files and search for:
error, warning, fault, panic, trace... "events".
For ESXi host:
/var/log/VMkernel.log
/var/log/vobd.log
VM log file:
VMware.log - in the same directory as the files of the virtual machine
If it is possible to download...
If you are unable to find anything suspicious in the newspapers using ESXTOP next level...
For troubleshooting with ESXTOP discover these excellent sources:
http://www.yellow-bricks.com/ESXTOP/
Esxtop statistical interpretation
http://www.VMworld.NET/WP-content/uploads/2012/05/Esxtop_Troubleshooting_eng.PDF
See also:
VMware KB: Troubleshoot ESX/ESXi virtual machines performance issues
VMware KB: Troubleshooting problems of network in a vSphere environment performance
VMware KB: Determine if the VM and ESX host blocking problem is caused by hardware issues
VMware KB: Performance high on Windows virtual machines network latency or poor network
VMware KB: Performance of local storage of the poor for VMware ESXi/ESX troubleshooting controller
Kind regards
P.
-
Satellite C660 - 11 H - HDD light is not blinking and laptop extremely slow
Hi, I recently started having problems with the laptop above, when you start the screen blocks on the screen 'windows', the HARD drive light does not work, either.
The computer loads up thereafter, but is very slow.Please note that the laptop was recently withdrawn only from a relatively sho height - problems began shortly after.
I think it might be the hard drive, Pls help.
Thank you
> I think it might be the hard drive, Pls help.
I agree with you. It's probably HDD Hat doesn't work properly.
Hard drives are cheap and you can exchange it alone then I recommend get you the new HARD drive, Exchange, install the original recovery image and test functionality.If you need assistance you are welcome.
-
iMac spinning Rainbow wheel appears each time I click on something and running extremely slow
My iMac (27 inch, mid 2011) is gel/loading every time I click on something. This occurs on the simplest tasks such as the opening of the finder window, open system preferences, right-click on desktop etc.
It happened all of a sudden a few days ago and I have not updated recently... I noticed this occurring has started after I opened the Photos Agent app for the first time and imported more than 1000 images/videos of my iPhone6. Could this be the cause of the problem?
Memory is 4 GB and it has worked very well so far. I checked disk utility and you have no error. Activity monitor looks great too.
Most important - looking the best way to backup or clone the HDD that I have a very important job out there. What is the best way to do it? I have a Macbook Pro, as well as with 100 GB free on it. Can I use it to help somehow?
If someone could help me out that would be great!
Mac form:
OS X Yosemite 10.10.3
Processor: 3.1 GHz Intel Core i5
4 GB OF RAM
More than 500 GB free 1 t
iMac, OS X Yosemite (10.10.3)
Here are my results of EtreCheck (sorry for the bad pictures but I was unable to open the browser to copy paste)
1. the present proceedings is a diagnostic test. It doesn't change anything for the better or worse and therefore, by itself, will not solve the problem. But with the help of the results of the tests, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later versions. I do not recommend running it on older versions of Mac OS X. It will do no harm, but it will not do not much good.
Do not be put off by the complexity of these instructions. The process is much less complicated than the description. You make the tasks more complicated with the computer all the time.
2. If you have already a current backup backup all data before doing anything else. The backup is needed on the general principle, not because of what anyone in the test procedure. Backup is always a must, and when you encounter any kind of problems with the computer, you can be more than the usual loss of data, if you follow these instructions or risk not.
There are ways to back up a computer that is not fully functional. Ask if you need advice.
3 here is instructions to run a UNIX shell script, a type of program. As I wrote above, it doesn't change anything. It does not send or receive data over the network. There is no to generate a report on the State of the computer human readable. This report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents for me or someone else.
You should ask yourself if you can believe me, and if it is safe to run a program at the request of a foreign national. In general, no, he's not sure, and I encourage it.
In this case, however, there are ways for you to decide if the program is safe without having to trust me. First of all, you can read it. Unlike an application that download you and click to start, it is transparent, so any person with the required competence can check what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this site of thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. One of the million registered users to have read the script and set off the alarm if it was dangerous. Then I wouldn't be here now, and you would not be reading this message. See, e.g., this discussion.
Another indication that the test is safe in this threadand this onecan be found, for example, where the comment in which I suggested it was recommended by one of the specialists of the communityApple, as explained here.
However, if you cannot satisfy yourself that these instructions are safe, do not follow them. Ask other solutions.
4. here is a general summary of what you need to do, if you decide to go forward:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window to another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Stick the results, which will be copied automatically, in a response on this page.
These are not specific instructions; just a glimpse. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait and paste it again. You don't need to copy a second time.
5. try to test in conditions that replicate the problem, to the extent possible. For example, if the computer is slow intermittently, run the test during a downturn.
You may have started up in safe mode. If the system is now in safe mode and works pretty well in normal mode to test run, restart as usual before running it. If you can test only in safe mode, this.
6. If you have more than one user and a user is affected by the problem, and the user is not an administrator, and then run the test twice: once under the affected user and one administrator. The results can be different. The user that is created automatically on a new computer, when you start it for the first time is an administrator. If you are unable to log in as an administrator, verify that the user concerned. More personal Mac have only one user, and in this case this section does not apply. Don't log in as root.
7 load the linked web page (the site "Pastebin.") The title of the page is 'Diagnostic Test'. Under the title is a text box, headed by three small icons. The right one represents a Clipboard. Click on this icon to select the text, then copy to the Clipboard of your computer by pressing Control-C key combination.
If the text is not highlighted when you click the icon, select it in triple - click anywhere inside the box. Do not select the whole page, just the text in the box.
8. start the Terminal application integrated in one of the following ways:
☞ Enter the first letters of his name in a Spotlight search. Select from the results (it should be at the top).
☞ In the Finder, select go utilities ▹ of menu bar or press the combination of keys shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing Command + V, then press return. The text that you pasted should disappear immediately.
9. If you see an error message in the Terminal as "Syntax error" or "Event not found", enter
exec bash
and press return. Then paste the script again.
10. If you logged in as an administrator, you will be prompted for your login password. Nothing displayed when you type. You won't see the usual points instead of the characters typed. Make sure that caps lock is turned off. Type carefully, and then press return. You can get a warning to be careful. If you make three unsuccessful attempts to enter the password, the test is still running, but it will produce less information. If you do not know the password, or if you prefer not to enter, just press back three times at the password prompt. Yet once again, the script will run.
If the test takes much longer that usual to run because the computer is very slow, you can be prompted for your password a second time. The permission you grant by entering it will expire automatically after five minutes.
If you are not logged as an administrator, you will be prompted for a password. The test will run. It just will not do anything that requires administrator privileges.
11. the test may take a few minutes to run, depending on the number of files you have and the speed of the computer. A computer that is abnormally slow may take more time to run the test. During execution, a series of lines is displayed in the Terminal window like this:
[Process started]
Part 1 of 4 done at … sec … Part 4 of 4 done at … sec
The test results are on the Clipboard.
Please close this window.
[Process completed]
The intervals between the parties will not be exactly the same, but they give an approximate indication of progress.
Wait for the final "Process complete" message. If you don't see it in about 15 minutes, the test probably won't be all within a reasonable time. In this case, press the Ctrl + C key combination or the point command to stop it. Then go to the next step. You will have incomplete results, but still something. If you close the window of the Terminal, while the test is still running, the partial results will not be saved and you have to start over.
12. when the test is finished, or if you have stopped it because it was taking too long, leaving the Terminal. The results have been saved to the Clipboard automatically. They do not appear in the Terminal window. Please do not copy from there. All you have to do is start a response to this comment and then paste it again by pressing Command-V.
At the top of the results, there will be a line that begins with the words «Start time.» If you do not see, but rather to see a mass of gibberish, you don't expect the "Completed" message is displayed in the Terminal window. Please wait and try again.
If personal information, such as your name or e-mail address, appear in the results, make anonymous before posting. Usually it will be not necessary.
13. in the validation of the results, you see an error message on the web page: "you have included content in your post that is not allowed", or "the message contains invalid characters." It's a bug in the software which manages this website. Thanks for posting the results of the tests on Pastebin, then post here a link to the page you created.
If you have an account on Pastebin, please do not select private in exposure menu to paste on the page, because no one else that you will be able to see it.
14. This is a public forum and others can give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but what're told you to do maybe not. For others who choose to run it, I do not recommend that you view the results of test on this Web site unless I ask.
______________________________________________________________
Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the "Test of diagnosis" referenced), I reserve all rights except as provided in the terms of use agreement for the site of Apple support communities ("CSA"). ASC readers can copy for their personal use. The whole nor any part can be redistributed.
-
I have a Wi - Fi connection and the signal is weak
Hello
(1) operating system do you work?
(2) you get an error message? If Yes, what is the exact full error message?
(3) you use Internet Explorer to browse the web?
(4) you remember changes to the computer before the show?
Wi - Fi and in Windows network connection issues.
-
Convert an Esxi 4 2 Server VM runs extremely slow
Hello
I am very new to virtualization and have just the configuration server ESXi 4 that will replace the VM Server 2 systems we tested. Recently, I tried to convert one of my server-2 VMs (Using the 'Converter Standalone Client') a VM (Version 7) Infrastructure. After two days of continuous operation, the converter was only 5% finished and was transferring data to 24 kb/s (the server is ~ 150 GB in size). This seems to be extremely slow and I hope that there is something that I can do to speed up that this server should run during opening hours and I like that, I can't take it down more than the weekend.
I ran the converter Client on the server that hosts the virtual machine, and that server and the ESXi have dual network adapters connected to a managed switch of FD 100 MB. (They are both on the same switch). The virtual machine was not working and there was almost no other network activity going on during the conversation.
Any help is appreciated
The goal is to eliminate the things that it is not. Download your installation as simple as possible. I don't know what your problem is, but it certainly seems like a network problem. A single 100 MB network adapter should work much faster than the speed you receive.
Other things to eliminate are pass the port problems, configuration issues, cable issues, NIC
Run something like wireshark as you begin your conversion. See if you notice any problems in the capture.
Create a new fresh installation of the VM on the ESXi host and check the flow rate etc. You don't want to go to production if you have problems. Monday will not be fun if you do.
-
My Mac Mini (end 2012) 2.5 ghz memory 8 GB Yosemite 10.10.5 is extremely slow. I read a few articles on communities, but unable to solve the problem. I plan to upgrade memory soon. In addition, a video game doesn't quite work. It starts and stops in 5 seconds and restarts it for a few seconds and stops completely. An advisor to fix the problem will be appreciated.
When you see a beachball cursor or the slowness is particularly bad, note the exact time: hour, minute, second.
These must be run as administrator. If you have only one user account, you are the administrator.
Run the Console application in one of the following ways:
☞ Enter the first letters of his name in a Spotlight search. Select from the results (it should be at the top).
☞ In the Finder, select go utilities ▹ of menu bar or press the combination of keys shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be all Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ all Messages
in the list of logs on the left. If you don't see this list, select
List of newspapers seen ▹ display
in the menu at the top of the screen bar.
Each message in the journal begins with the date and time when it was entered. Highlight date back to the time you noted above.
Select the messages entered since then until the end of the episode, or until they begin to repeat, whichever comes first.
Copy messages to the Clipboard by pressing Control-C key combination. Paste into a reply to this message by pressing command + V.
The journal contains a large amount of information, almost all this is useless to solve any particular problem. When you post a journal excerpt, be selective. A few dozen lines are almost always more than enough.
Please don't dump blindly thousands of lines in the journal in this discussion.
Please do not post screenshots of log messages - text poster.
Some private information, such as your name, may appear in the log. Anonymize before posting.
When you post the journal excerpt, an error message may appear on the web page: "you include content in your post that is not allowed", or "the message contains invalid characters." It's a bug in the forum software. Thanks for posting the text on Pastebin, then post here a link to the page you created.
If you have an account on Pastebin, please do not select private in exposure menu to paste on the page, because no one else that you will be able to see it.
-
Firefox has been extremely slow. Typing, loading, search, even just scroll to the top of a page to the bottom. My daughter had the same thing happens to sound and had to get his computer disassembled and full recharged. I don't have this option. He doesn't have a virus and was completely free of anything that might slow it down.
This has happened
Each time Firefox opened
Is a month ago. It is getting worse.
Hmm... try to download the last version... but if it doesn't, then try Safe Mode. Do not know what could be causing it...
-
My V5-571 CAREB is extremely slow at startup and would become very hot gel frequently
My laptop CAREB 571 V5 running on Windows 10 is extremely slow at startup and becomes very hot, gel frequently.
I recommend reloading the windows to see if it helps the slow and freezing. If it is not the case, I suggest that you contact technical support for repair options. I am including the instructions below to reload Windows without losing any data.
-
XP system is extremely slow start and open programs are more inadmissible
Is anyone know the problem / answer?
My XP Sp3 has EXTREMELY slow start and programs are mostly non_responsive. When I close the programs they Peel the top of the screen down. Can you help me?* original title - screens XP Sp3 frozen, non-resonsive programs, peeling *.
Hi dmahu,
· Did you the latest changes on the computer?
· How long have you been experiencing this problem?
· What happens when you try to open the programs?
· You receive an error message/code?
· What security software you are using on the computer?
· Do you have too many applications on the computer installed?
I suggest you try the steps mentioned below and check if it helps.
Step 1: Perform a clean boot to see if there is a conflict of software like the clean boot helps eliminate software conflicts.
Note: After the boot minimum troubleshooting step, restore your computer to a Normal startupmode.
-
Original title: searchfilterhost problems
I am running Vista family 32-bit and when the computer is left in standby mode, that it does not start normally, usually ok in mode without failure, but even if his place and it works normally is extremely slow. Having verified the use of the processor, 82 processes running anything meaningful except 50 + % is used by searchfilterhost.exe, this would cause the problem and if so how it can be cured.
Hi Brian,.
You have made any changes to your computer recently?
I suggest you to follow the steps and check if it helps.
Method 1: Follow the link and check if that helps.
The problems of wake the computer from sleep modeMethod 2: You can also follow the link and check if it helps.
How to troubleshoot performance problems with sleep, hibernation and resume in Windows VistaMethod 3: Search for viruses using the Microsoft Safety Scanner and check if that helps.
http://www.Microsoft.com/security/scanner/en-us/default.aspxNote: The data files that are infected must be cleaned only by removing the file completely, which means that there is a risk of data loss.
Method 4: You can also check out the link and check if it helps.
Ways to improve your computer's performance
-
Extremely slow and jerky Remote Desktop connection
I visited the thread at the bottom of this post and tried two patches that have been proposed, but I still have problems of slowness.
I use Windows 10 Pro on my desktop at home and I use it to access a work Web page that has the ability to remote into my PC which has Windows 7 Enterprise to work.
As soon as I have I'm having extreme slowness and connection applications are very bug. It makes it impossible to work from home. Help, please!
Remote Desktop is very slow on one another and fast on a single computer
Hello
Thank you for visiting Microsoft Community.
By the description, I understand that the problem with the connection Remote Desktop is extremely slow and jerky on the system.
I certainly understand your concern and appreciate very much all your efforts to try to solve this problem.
To get more information about it, we have a dedicated forum where these issues are dealt with and would be better suited to the TechNet community.
Please visit the link below to find a community that will provide the best support.
https://social.technet.Microsoft.com/forums/Windows/en-us/home?category=w7itpro
I hope this information is useful.
Please let us know if you need more help, we will be happy to help you.
Thank you.
-
Windows 7 goes extremely slow and freezing frequently
I have HT a windows 7 operating system and it goes extremely slow and freezes frequently. You guys you will suggest what the problem in this case and how to resolve this kind of things? I want a little format. Thank you.
Hi Nazaz,
1. What is the number of brand and model of the computer?
2. don't you make changes on the computer before this problem?
I suggest to start the computer in safe mode and check if it helps.
Method 1:
Step 1:
See the link to start in safe mode.
Start your computer in safe mode
Step 2:
If the computer works fine in safe mode, I suggest you perform the clean boot.
See the link to perform the clean boot.
How to perform a clean boot in Windows
http://support.Microsoft.com/kb/929135Note: After troubleshooting, see the section «How to reset the computer to start normally after a boot minimum troubleshooting»
Method 2:
Optimize Windows performance
Note: The data files that are infected must be cleaned only by removing the file completely, which means that there is a risk of data loss.
Additional information:
8.1 Windows, Windows 8 or Windows 7 hangs or freezes
http://support.Microsoft.com/kb/2681286/en-us
Note: The data files that are infected must be cleaned only by removing the file completely, which means that there is a risk of data loss.
How to speed up your slow computer
http://support.Microsoft.com/kb/2746761/en-us
It will be useful. Back to us for any problem related to Windows. We will be happy to help you.
-
My phone blackBerry smartphones is extremely slow and eat the battery
I have faced this problem for 3 days and went to my service provider today to inquire.
My phone has been extremely slow, the time clock thing is for still running, and so my phone dies in 3 to 4 hours with no real use. I was told that it was because I need to update my OS but when I got home and plugged in it says that my phone is up to date and there is no upgrade available OS. I bought a spare battery to see if it was the problem and it is not. This is getting very frustrating. He even got to the point of when I lock the phone I can't unlock it during the same get the screen to turn on. the only way to start is to pull the battery out and put back.
What is the problem with my phone?
Hello maddy 22
It does not matter how old is your phone recharge your device software will help you of course but do not miss the KB14320 , I suggested after reloading of your device OS. Here's how to reload a device on a Mac software:
KB19915 How to perform a reload of the own software application smartphone BlackBerry using BlackBerry Desktop Software for mac
I hope this will help.
Prince
________________________________________________________________________
Click 'Like' If you want to thank someone.
If problem resolves mark message (s) as a 'Solution', so that others can use.
Maybe you are looking for
-
ProBook 4520 s: Hp probook 4520 s very slow on current alternative
Hello After some research when the battery is connected to its own all works to the spped I expect. About connecting AC power imediatley slows down speed unsuable. New TI speeeds save on diconecting. I have: installed the HP Power program and the d
-
Recently had computer problems, now when I turn on my computer I had to go through Microsoft sign on the page before I can access my Start Page. How can I remove this and have my Start Page to come once the computer has developed?
-
The faulty or incorrect error for D6160 message print cartridge
The message said: I have some incorrect cartridge somehow. The cartridge is a good HP363 one and me the printer is off, found another adequate cartridge, reinstalled the driver... does anyone know what I can do? I'm not very brave to take the thing a
-
BlackBerry smartphones I want to retrieve my contacts.
Hello world. I have a blackberry 9800. I have reset to the factory default, so my contact and my Inbox is empty now. I have no backup of them. Is there anything I can get my contacts. There are many crucial number in it. Thank you.
-
Enter the security key for modem
internal printer for network setting. The wireless configuration wizard ask the security key that is 10 digits. I am looking to enter, but it is to show the alpha characters. How can I enter the non alpha numeric characters. Thank you.