I appreciate the coverage of VMWorld that you’ve been offering - the last point you blogged from the session:
“Try to limit the use of resxtop, and use it for real-time troubleshooting not monitoring.”

I havn’t used resxtop yet, but had plans to tie it into a monitoring system. Do you have any more detail on why it is suggested that it shouldn’t be used for monitoring?

Thanks.

Windows Page File is not handled by VMware View but there techniques to help you deal with them. Couple weeks ago I posted an article named “Pagefiles and VDI. Not so simple” http://myvirtualcloud.net/?p=1050

Nice write-up!

7 kids? Abstinence is not necessarily a bad thing. ;o)

This information should be easier to find !!

I am a Netlist shareholder. The link above is for the yahoo NLST board where there can be some good discussion occasionally.

CSCO UCS is important (for NLST shareholders) because it uses an ASIC-on-motherboard approach to improve the memory-loading/memory-bandwidth tradeoff problem.

NLST is able to put ASIC/buffer chip on the memory module itself, with HyperCloud memory modules that are plug and play and require no BIOS updates.

NLST HyperCloud promised:
- ability to load higher memory
- runs at full 1333 MHz
- lower power (does something with turning off power for ranks not in use ?)
- uses “lower dollar per bit” memory chips to emulate “higher dollar per bit” memory chips which improves economics for NLST (in a way similar to CSCO use of large number of memory slots)

NLST has demoed HyperCloud at exhibitions using DELL, HP and IBM machines.

On HP machines:

http://www.prnewswire.com/news-releases/netlist-demonstrates-new-hypercloud-memory-modules-at-supercomputing-09-70174702.html
Netlist Demonstrates New HyperCloud Memory Modules at Supercomputing 09

On IBM machines:

http://www.prnewswire.com/news-releases/netlist-introduces-low-voltage-hypercloud-industrys-first-135v-virtual-rank-memory-module-92165154.html
Netlist Introduces Low Voltage HyperCloud, Industry’s First 1.35V Virtual Rank Memory Module

According to company, they had a dozen OEMs qualifying HyperCloud, which has been upped to “3 dozen” companies now.

Won some qualifications recently (SuperMicro, Viglen), with testimonials:

http://finance.yahoo.com/news/Supermicro-Qualifies-Netlists-prnews-2550444882.html?x=0&.v=1
Supermicro Qualifies Netlist’s HyperCloud Memory on High-Density Servers

http://finance.yahoo.com/news/Viglen-Selects-Netlists-prnews-2806446361.html?x=0&.v=1
Viglen Selects Netlist’s HyperCloud Memory for HPC Applications

Another area of concern for shareholders is litigation.

However there have been some successes recently with wins over:

- MetaRAM (Fred Weber’s outfit) where they conceded related IP to NLST (the rest was sold to GOOG)

- Texas Instruments (which was accused of leaking info obtained under NDA from NLST to JEDEC) - settled recently (reportedly favorably for NLST)

The most visible case is GOOG vs. NLST where judge has ruled in favor of NLST claims construction. After TXN settlement, NLST has asked court that following testimony obtained from JEDEC lawyer and GOOG employee Rob Sprinkle they have all the “facts” in place and matter can goto summary judgement (i.e. no need for jury trial which is primarily used to ascertain “facts”). Discovery is complete and judge has been urging parties to settle. So summary judgement request is likely to be approved, thereby moving timeline from Nov 2010 to a bit earlier (summary judgement hearing Sept 14).

GOOG vs. NLST is interesting because it was started by GOOG to protect itself against potential injunction against it’s servers, but judge forced GOOG to turn over it’s server to NLST lawyers where it was found to be using JEDEC “Mode C” proposed standard. JEDEC had earlier issued letters to members and GOOG that “Mode C” potentially infringed NLST IP.

It was in response to this that NLST vs. GOOG was started.

It turns out that GOOG had it’s own hardware division that was contracting for the buffer chips and GOOG was essentially manufacturing it’s own memory modules. It is unclear just how prevalent use of this type of memory is at GOOG.

GOOG will settle eventually, however such settlement will probably include future business with NLST.

Other litigation is against Inphi (which is seeking to manufacture buffer chips based on JEDEC “Mode C” proposed standard). Unlike MetaRAM which held significant IP, Inphi holds little IP in this area - they have been using a Sanmina-SCI patent application and other patents to provoke interference at USPTO for patent reexamination (which are routinely accepted by USPTO).

However Sanmina-SCI patent application has gotten rejected again.

Inphi litigation however is still very early (not even started discovery) so they will mature much after GOOG litigation and related JEDEC stuff is settled and done.

Anyway, so this is the short intro to NLST

The two KB articles are emc223285 for VMAX and emc13308 for DMX-4 and earlier.

emc13308 also has the following instructions for accessing the WWN encoder/decoder tool via Powerlink:

* Powerlink>support>product and diagnostic tools>Environmental Analysis tools>HEAT
* Select “visit the HEAT website”
* Once there, go to the top and select “Analysis tools”, drop down to WWN/iSCSI decoder, copy/paste the WWN from your output the select “continue”