It would be really helpful if someone could explain what is happening through out the install process. Once the VMs are created and boot up you are kind of in the dark for a long time. In my situation the VMs boot up and hang for about 10-15 mins at "2.013418 NMI watchdog enabled, takes one hw-pmu counter." What is going on at this point?
Eventually, the next line of parameters seem to show up on the screen on character at a time, and eventually, the three VMs boot up in not particular order. One of my three seems to take much longer than the others. Once they all boot up, I quickly login and tail the /var/messages/sva.log for each one. All the messages look like normal activity and I seem to be chugging along on each VM.
What is the next step? My install seems to fail because one of the VMs and the host its on randomly goes offline during a "QoS" line that I didn't capture this time around. The other two hosts end up at a "FORCE REBOOT" point and seem to keep going.
Is this intentional that one host should go offline in the cluster at this point? It just kind of sits there like that while the other two seem to continue on their way, completely booting up and rebooting again. If I let things sit indefinitely, they seem to get to a milestone and wait, while the 3rd one just remains offline. Eventually the entire process times out and a rollback begins.
If I reboot the host that is offline in another scenario, it will reconnect to the cluster and I can boot its VM, but the entire process still times out.
The network setups are identical on all three hosts. I feel like I'm really close here, after attempting this process over a dozen times. I'm starting to really dislike this product, yet I accept that I must be missing something.
My vcenter vsa log looks great until this happens. There's no indication of what happened to the host that went offline.