Thanks. I researched on these options that you mentioned but looks like they are not available in Virtualbox unfortunately. What really surprises me is that the cluster nodes are sometimes extremely stable and runs fine for as long as 10hrs. Sometimes it's so fragile that it panics within a few minutes. I really can't understand why it behaves like this. In fact I have a pretty decent quad core cpu (core i7-740QM) with 8GB of physical memory. I usually don't run any other apps when I launch the cluster. This pm_tick panic is a great mystery for me.
> Gorak, > > The panics will be due to the fact that you are > running in a VirtualBox > and that the networking won't be guaranteed to be > handled in the same > timely manner as if it was a physical machine. At > least, that's what I > suspect. I don't know if binding your VirtualBox > processes to fixed > processors under Windows would make any difference. > It's worth a try. > > I know with LDoms, there is a flag you have to set to > indicate that the > networks are for cluster interconnects. I suspect > that that overcomes > this sort of issue. > > Regards, > > Tim > --- > > > On 07/14/11 01:56, gorak wrote: > > Venku/hs86490, > > > > I apologize. It was so stupid of me that I had a > typo in my zpool > > which I never noticed. When manually importing the > zpool, I used the > > correct zpool name but when entering the clresource > command i > > misspelled it. Sorry again and thanks for all your > help in taking > > time to respond to me. Everything works absolutely > fine for me right > > now. > > > > I have a different issue now. Occasionally I'm > facing cluster panics > > because of pm_tick delays. I tried setting the > hearbeat_quantum and > > heartbeat_timeout values using scconf, to their > maximum limits, but > > I'm still getting those panics. Any idea why? > > -- > > Tim Read > Software Developer > Solaris Availability Engineering > Oracle Corporation UK Ltd > Springfield > Linlithgow > EH49 7LR > > Phone: +44 (0)1506 672 684 > Mobile: +44 (0)7802 212 137 > Twitter: @timread > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~~~~~~~~~ > > NOTICE: This email message is for the sole use of the > intended > recipient(s) and may contain confidential and > privileged information. > Any unauthorized review, use, disclosure or > distribution is prohibited. > If you are not the intended recipient, please contact > the sender by > reply email and destroy all copies of the original > message. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~~~~~~~~~ > _______________________________________________ > ha-clusters-discuss mailing list > ha-clusters-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ha-cluste > rs-discuss > -- This message posted from opensolaris.org _______________________________________________ ha-clusters-discuss mailing list ha-clusters-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss
