tag:blogger.com,1999:blog-2228947945609574437.post1113955341083836402..comments2024-03-17T16:23:31.499-04:00Comments on Terence Luk: VMware ESXi 4.1.0 stuck at “Initializing scheduler …” screen on boot up with Cisco UCS C210 M2 serversTerence Lukhttp://www.blogger.com/profile/02612575579652280306noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-2228947945609574437.post-26527271218138334872015-05-13T13:37:45.177-04:002015-05-13T13:37:45.177-04:00I've installed the licensed VM-Ware ESXi 4.1 a...I've installed the licensed VM-Ware ESXi 4.1 and, most of the time, it's working perfectly. Randomly, however, I lose connectivity to the virtual machine having SAP Application installed on it. During this timeout period, the application struck <br />at client end.<br /><br />General Server Details:<br /><br />HP DL380-G5 Proliant<br />RAID level: 0 + 5<br /><br />Separate VLAN for management<br /><br />This, to me, indicates that the issue isn't with networking outside of the ESX host, but rather within the virtual machine or the virtual switch. I've moved the VM to <br />another ESXi host but the problem persists.<br /><br />Another curious sign is the ping latency from the Local Traffic Manager out to a VM node (same ESXi host):<br /><br />PING 172.16.xxx.xxx (172.16.xxx.xxx) 56(84) bytes of data.<br />64 bytes from 172.16.xxx.xxx: icmp_seq=1 ttl=128 time=7.25 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=2 ttl=128 time=9.26 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=3 ttl=128 time=10.2 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=4 ttl=128 time=10.2 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=5 ttl=128 time=9.12 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=6 ttl=128 time=10.3 ms<br /><br />--- 172.16.xxx.xxx ping statistics ---<br />6 packets transmitted, 6 received, 0% packet loss, time 5035ms<br /><br />rtt min/avg/max/mdev = 7.252/9.421/10.319/1.091 ms<br /><br />@AndrewPWR:<br /><br />1. Nothing logged to any of the /var/log files that would be of any help. <br /><br />2. Performance graphs don't indicate that I'm hitting any sort of ceiling.<br /><br />3. Outages last for 1 - 2 minutes, then traffic resumes on its own. <br /><br /><br /><br />After trying different methodologies, configuration, using different network latency test tool. In Last with the help of Mr. Marc (Sr. Infrastructure Specialist) @ SDN Singapore we have found that the bug is in VMXNET 3 driver, all the reports and statics has been forwarded to VM support center and after 1 week they have resolved this bug via releasing a driver patch, details are mentioned below.<br />Name: ESXi410-201404001<br />Ver: 4.1.0 Patch 12<br />Release 2015-04-20 <br />Build: 1682698<br />I will try my level best in future to identify these types of bugs, which will help us and other to run there all live applications flawless.<br />Trying to Upgrade and Migrate on Latest Versions as well.<br /><br /><br /><br /><br /><br /><br /><br /><br />VM-Warehttps://www.blogger.com/profile/17580308360849103389noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-91611549460906132502015-05-13T13:37:34.890-04:002015-05-13T13:37:34.890-04:00I've installed the licensed VM-Ware ESXi 4.1 a...I've installed the licensed VM-Ware ESXi 4.1 and, most of the time, it's working perfectly. Randomly, however, I lose connectivity to the virtual machine having SAP Application installed on it. During this timeout period, the application struck <br />at client end.<br /><br />General Server Details:<br /><br />HP DL380-G5 Proliant<br />RAID level: 0 + 5<br /><br />Separate VLAN for management<br /><br />This, to me, indicates that the issue isn't with networking outside of the ESX host, but rather within the virtual machine or the virtual switch. I've moved the VM to <br />another ESXi host but the problem persists.<br /><br />Another curious sign is the ping latency from the Local Traffic Manager out to a VM node (same ESXi host):<br /><br />PING 172.16.xxx.xxx (172.16.xxx.xxx) 56(84) bytes of data.<br />64 bytes from 172.16.xxx.xxx: icmp_seq=1 ttl=128 time=7.25 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=2 ttl=128 time=9.26 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=3 ttl=128 time=10.2 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=4 ttl=128 time=10.2 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=5 ttl=128 time=9.12 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=6 ttl=128 time=10.3 ms<br /><br />--- 172.16.xxx.xxx ping statistics ---<br />6 packets transmitted, 6 received, 0% packet loss, time 5035ms<br /><br />rtt min/avg/max/mdev = 7.252/9.421/10.319/1.091 ms<br /><br />@AndrewPWR:<br /><br />1. Nothing logged to any of the /var/log files that would be of any help. <br /><br />2. Performance graphs don't indicate that I'm hitting any sort of ceiling.<br /><br />3. Outages last for 1 - 2 minutes, then traffic resumes on its own. <br /><br /><br /><br />After trying different methodologies, configuration, using different network latency test tool. In Last with the help of Mr. Marc (Sr. Infrastructure Specialist) @ SDN Singapore we have found that the bug is in VMXNET 3 driver, all the reports and statics has been forwarded to VM support center and after 1 week they have resolved this bug via releasing a driver patch, details are mentioned below.<br />Name: ESXi410-201404001<br />Ver: 4.1.0 Patch 12<br />Release 2015-04-20 <br />Build: 1682698<br />I will try my level best in future to identify these types of bugs, which will help us and other to run there all live applications flawless.<br />Trying to Upgrade and Migrate on Latest Versions as well.VM-Warehttps://www.blogger.com/profile/17580308360849103389noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-80854590900390958472015-05-13T13:37:31.427-04:002015-05-13T13:37:31.427-04:00I've installed the licensed VM-Ware ESXi 4.1 a...I've installed the licensed VM-Ware ESXi 4.1 and, most of the time, it's working perfectly. Randomly, however, I lose connectivity to the virtual machine having SAP Application installed on it. During this timeout period, the application struck <br />at client end.<br /><br />General Server Details:<br /><br />HP DL380-G5 Proliant<br />RAID level: 0 + 5<br /><br />Separate VLAN for management<br /><br />This, to me, indicates that the issue isn't with networking outside of the ESX host, but rather within the virtual machine or the virtual switch. I've moved the VM to <br />another ESXi host but the problem persists.<br /><br />Another curious sign is the ping latency from the Local Traffic Manager out to a VM node (same ESXi host):<br /><br />PING 172.16.xxx.xxx (172.16.xxx.xxx) 56(84) bytes of data.<br />64 bytes from 172.16.xxx.xxx: icmp_seq=1 ttl=128 time=7.25 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=2 ttl=128 time=9.26 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=3 ttl=128 time=10.2 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=4 ttl=128 time=10.2 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=5 ttl=128 time=9.12 ms<br />64 bytes from 172.16.xxx.xxx: icmp_seq=6 ttl=128 time=10.3 ms<br /><br />--- 172.16.xxx.xxx ping statistics ---<br />6 packets transmitted, 6 received, 0% packet loss, time 5035ms<br /><br />rtt min/avg/max/mdev = 7.252/9.421/10.319/1.091 ms<br /><br />@AndrewPWR:<br /><br />1. Nothing logged to any of the /var/log files that would be of any help. <br /><br />2. Performance graphs don't indicate that I'm hitting any sort of ceiling.<br /><br />3. Outages last for 1 - 2 minutes, then traffic resumes on its own. <br /><br /><br /><br />After trying different methodologies, configuration, using different network latency test tool. In Last with the help of Mr. Marc (Sr. Infrastructure Specialist) @ SDN Singapore we have found that the bug is in VMXNET 3 driver, all the reports and statics has been forwarded to VM support center and after 1 week they have resolved this bug via releasing a driver patch, details are mentioned below.<br />Name: ESXi410-201404001<br />Ver: 4.1.0 Patch 12<br />Release 2015-04-20 <br />Build: 1682698<br />I will try my level best in future to identify these types of bugs, which will help us and other to run there all live applications flawless.<br />Trying to Upgrade and Migrate on Latest Versions as well.VM-Warehttps://www.blogger.com/profile/17580308360849103389noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-74937233576620176612014-12-24T12:26:23.957-05:002014-12-24T12:26:23.957-05:00See latest update on my issue: https://communities...See latest update on my issue: https://communities.vmware.com/message/2461204#2461204Anonymoushttps://www.blogger.com/profile/13933514759906126087noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-20351422723955217272014-12-23T15:45:05.345-05:002014-12-23T15:45:05.345-05:00We have this same issue on our brand new x3650 M4 ...We have this same issue on our brand new x3650 M4 7915 server and cannot seem to resolve it with IBM. I tried legacy boot-mode and UEFI modes with no success. Can you help me resolve it?Anonymoushttps://www.blogger.com/profile/13933514759906126087noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-27165838683144883302013-10-27T01:42:44.601-04:002013-10-27T01:42:44.601-04:00This issue is also seen with 5.1.0 on IBM System x...This issue is also seen with 5.1.0 on IBM System x3650 M3 (7945AC1). <br /><br />I tried disabling legacy USB, but the only thing that worked was unplugging the ps2-2-usb adapter for my KVM. chrisgrinerhttps://www.blogger.com/profile/16244915533518784215noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-56760687850995255692013-04-15T16:33:18.953-04:002013-04-15T16:33:18.953-04:00Apparently this also affects vSphere 5.1 with the ...Apparently this also affects vSphere 5.1 with the R210 too. This setting resolved the issue for me.Rob Rechnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-25015735015140399862012-10-30T09:59:26.544-04:002012-10-30T09:59:26.544-04:00Saw this on an IBM bladeCenter model 7870 (HS22) w...Saw this on an IBM bladeCenter model 7870 (HS22) where USB and media trays are shared with the bladecenter chassis. Was gonna try disabling legacy USB, but a coworker suggested moving the "M/T" assignment to another blade (effectively moving USB and media to another blade). ESXi immediately continued it's bootup once we did that. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-54242528921100261492012-01-10T11:14:44.610-05:002012-01-10T11:14:44.610-05:00I am also in the same situation:
VMware ESXi 4.1.0...I am also in the same situation:<br />VMware ESXi 4.1.0 on HP Proliant DL385 G7 Hangs at loading VMKernel <br />Is say "VMKernel Loaded successfully". But hangs after five bars.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-66489412961509189792011-04-26T11:27:06.132-04:002011-04-26T11:27:06.132-04:00Just upgraded our Test standalone UCS to 1.4m this...Just upgraded our Test standalone UCS to 1.4m this afternoon and still hung on Initialising Scheduler after installing ESXi4.1 - disabling in the BIOS seems to have resolved the issue but again difficult to be definite at this point due to the intermittent issue.Paul Bnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-63411584117829251412011-03-09T23:12:42.000-05:002011-03-09T23:12:42.000-05:00Awesome! Thanks for the heads up Peter.Awesome! Thanks for the heads up Peter.Terence Lukhttps://www.blogger.com/profile/02612575579652280306noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-33988511202567203152011-03-09T04:13:02.064-05:002011-03-09T04:13:02.064-05:00Looks like this is fixed now in 1.4(1m)
"ES...Looks like this is fixed now in 1.4(1m) <br /><br />"ESXi boot up no longer intermittently hangs at the initializing scheduler. (CSCtj19224"Peter Cronwrighthttps://www.blogger.com/profile/12254441387133555467noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-13894998395535735372011-01-19T16:15:35.331-05:002011-01-19T16:15:35.331-05:00Add the IBM x3650 M3 to the list as well. Unpluggi...Add the IBM x3650 M3 to the list as well. Unplugging the USB->PS2 adapter solved the issue.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-60572598353461820522011-01-11T10:49:46.465-05:002011-01-11T10:49:46.465-05:00You can include also Cisco UCS C250 M2 in the list...You can include also Cisco UCS C250 M2 in the list of affected servers.<br />Thanks for this post I was resetting CMOS everytime I rebooted the servers.<br />RegardsUnknownhttps://www.blogger.com/profile/05335600022761517563noreply@blogger.com