I don't believe mine was memory related as there is plenty to spare. Setting 'cpu_type=core2duo' allowed installation to proceed and the VM runs fine after installation with the cpu_type override removed.
--jason > On Feb 2, 2016, at 5:13 PM, Eric <[email protected]> wrote: > >> On Mon, Feb 1, 2016 at 5:46 PM Jason Lawrence <[email protected]> wrote: >> I found a suggestion in >> https://github.com/joyent/smartos-live/issues/456#issuecomment-112663295 to >> change the cpu_type, and the install continued after I specified 'core2duo' >> (but not 'Nehalem'). >> >> Anyone have any experience with this approach? > > Hey Jason. OP here. If you keep going after that comment you'll get a post > that solved it for me: > > https://github.com/joyent/smartos-live/issues/456#issuecomment-113349256 > > Essentially, by default there's an additional amount of RAM that's allocated > from the amount given to the VM, which caused it to immediately stop soon > after starting. > > smartos-discuss | Archives | Modify Your Subscription ------------------------------------------- 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
