On 07/01/2014 06:57 AM, Keith Wesolowski via smartos-discuss wrote: > On Tue, Jul 01, 2014 at 02:52:16PM +0100, Nigel Magnay via smartos-discuss > wrote: > >> Create a VMWare machine (VMWare fusion, in my instance). Give it 2GB Ram. >> Boot SmartOS. Follow the "how to compile smartos on smartos" steps. System >> locks solid about half way through (I/O is idle). > > This might (or might not) be a bug, but 2 GB is not enough to build > SmartOS.
2 Gb of DRAM is enough to build SmartOS, but there are a few issues with the wiki page you've referenced that I've noticed in taking another look at it in those situations. I routinely build SmartOS in Vmware Fusion with 2-4 Gb of DRAM with no problem. The guidelines that it has for setting max_physical_memory to 32 Gb are not correct on smaller systems and that will lead to problems. You've overprovisioned memory, so you're likely swapping quite a bit. In addition, there was an addendum added to that page recently to deal with more of the lower memory configurations and turn down the parallelism. In the case described below, you'll still want to go through and get a dump, but I'd be curious to understand what the set of zones and KVM instances provisioned on that machine looks like. >> I can repeat exactly with an AMD-based microserver box, and it's the same >> behaviour as our dual-CPU, 64Gb RAM supermicro system when it gets put >> under load. > > Send the "locked up" system an NMI, which will generate a crash dump. > File a bug with the dump attached. If you look through the existing > issues, you'll see that bug reports with crash dumps get a lot of > attention. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
