To view parent comment, click here.
To read all comments associated with this story, please click here.
Thats interesting, as where I work is a primarily IBM site, and pSeries/AIX is the buggiest P.O.S I've ever worked on.
LPAR's are not totally separate, I've seen DLPAR operations on one LPAR kill another due to memory conflicts. We frequently see Power5 and 6 boxes drop when they suddenly offline 8gb of RAM, or decide to offline a cpu for laugh.
The IBM VIO server is memory and CPU intensive and prone to having strange issues which you just can't trace through its complicated configuration (why the hell is every network card enX on AIX???).
I guess its what you're used to... I work on AIX and yearn for Sun - looks like you're the other way around!
AIX has LPAR support since 2000 or 2001. Sun is trying a new thing every year, it's annoying.
To be able to use LDOMs in our one-year-old Sun T1000s, We had to upgrade the OS, the firmware, and install ten freakin patchs. :-(
That's not what I call a "mature technology"...
Edited 2008-10-15 19:19 UTC
- unability to patch zones (we are using u3)
U3 is fairly old now.
- performance problems (thanks to processes block in kernel mode).
Can you elaborate on this please? Is there a bugid?
- and now the servers reboot itself in u5
bugid?
Solaris 10 is the most crappy release from Sun. You are taking Sun's blueprints/site like a reliable source. But it's only some ads from Sun, in fact the reality is by far different.
Can you point out which Blueprints are incorrect so
we can get them fixed please. It's also interesting
that you use this argument as a retort - did you
read the article linked by the OP? What would you call
that?
On the other side AIX and LPAR are working like a charm...
charm
⢠noun
1 the power or quality of delighting or fascinating others.
2 a small ornament worn on a necklace or bracelet.
3 an object, act, or saying believed to have magic power.
Seems somehow appropriate given the nature of your
post.
Yes and we paid to be early adopters of solaris zones.
Performance problem is mainly due to the fact that each zones share the same kernel. Thus when a software goes in kernel mode, the CPU time is not controlled anymore and the zone. So if there is a software bug during kernel mode, the zone will eat all the CPUs despite ressource control set.
Its no bug, it's the way zone are working.
http://forums.sun.com/thread.jspa?forumID=844&threadID=5316991
you can find the bug ID (6696124) in the thread but Sun removed it for security reason ....
charm
⢠noun
1 the power or quality of delighting or fascinating others.
2 a small ornament worn on a necklace or bracelet.
3 an object, act, or saying believed to have magic power.
Seems somehow appropriate given the nature of your
post.
Ignoring the sarcastic tone in the above post (as we do not use sarcasm here in the Middle East) the meaning is given here: http://idioms.thefreedictionary.com/work+like+a+charm:
work like a charm
if a plan or method works like a charm, it has exactly the effect that you want it to.
or
to operate perfectly.
Edited 2008-10-16 18:42 UTC





Member since:
2006-09-23
We are using zones here, we have only problems.
- unability to patch zones (we are using u3)
- performance problems (thanks to processes block in kernel mode).
- and now the servers reboot itself in u5
Solaris 10 is the most crappy release from Sun. You are taking Sun's blueprints/site like a reliable source. But it's only some ads from Sun, in fact the reality is by far different.
On the other side AIX and LPAR are working like a charm...
Edited 2008-10-15 16:25 UTC