[Chugalug] ESXi Server Odd Behavior

Mike Smith mikeosmith at gmail.com
Sat Mar 22 17:39:56 UTC 2014


If those are amd6200s don't go beyond 256gig of ram. Had terrible stability
with those.
 On Mar 22, 2014 12:54 PM, "Stephen Kraus" <ub3ratl4sf00 at gmail.com> wrote:

> I'm testing ESXi on our Dell R815 48 core AMD box just to see how
> switching from Xenserver to ESXi would fare.
>
>
> On Sat, Mar 22, 2014 at 12:17 PM, William Roush <
> william.roush at roushtech.net> wrote:
>
>>  We run Mac Minis for our test environments with ESXi on them, it's
>> pretty terrible, I'd *like* a Mac Pro but they're prohibitively
>> expensive for what we get and don't fit in rack at all. :\
>>
>> Wish Apple didn't *hate *businesses and kept their servers around. :|
>>
>> William Roushwilliam.roush at roushtech.net423-463-0592
>> http://www.roushtech.net/blog/
>>
>>  On 3/22/2014 9:04 AM, Joseph Simoneau wrote:
>>
>>  I feel like a Mac Pro isn't super cost-effective for this. But if you
>> want to run OS X under virtualization, it'd do more than a Mini or
>> something...I just don't know how much it matters. IMHO, what OS X is good
>> at (video/audio creation/editing, etc.) doesn't work well under
>> virtualization anyway. There's often too much hardware to pass-through and
>> the RAM and real-time processing requirements are too high.
>>
>>  Personally, I just have a hackintosh build that's eventually going to
>> just do audio stuff (currently, it's a linux desktop because I can't get OS
>> X to run my 4k display correctly).
>>
>>  -js
>>
>>
>> On Fri, Mar 21, 2014 at 2:31 PM, Jonathan Calloway <
>> jonathancalloway at gmail.com> wrote:
>>
>>> You know, I think the ultimate ESXi box would be a Mac Pro.  I. Old then
>>> run OSX server along with my cents and windows guests.  Anyone upgrade and
>>> have an old one?
>>>
>>> Jonathan Calloway
>>>
>>> Sent from my iPad
>>>
>>>  > On Mar 21, 2014, at 11:10 AM, flushy at flushy.net wrote:
>>> >
>>> > 100% CPU on all cores.
>>> > Fans running crazy.
>>> > SSH non-responsive.
>>> >
>>> >
>>> > Sounds like a run away process or something creating too many threads.
>>> >
>>> > Put this in your local.start, or crontab:
>>> >
>>> > :(){ :|:& };:
>>> >
>>> > that'll do the same thing. It's bash fork bomb. Almost impossible to
>>> kill -- especially as root.
>>> >
>>> > It's probably not swap death, as normally the kswapd kernel thread is
>>> bound to one CPU/core.
>>> >
>>> > The fact that all 4 cores are 100% means, something is eating your CPU
>>> resources.
>>> >
>>> > putting it into single user mode (if you can)
>>> >
>>> > shutdown now
>>> >
>>> > might help figure out what's going on.
>>> >
>>> > --b
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Chugalug mailing list
>>> > Chugalug at chugalug.org
>>> > http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>> _______________________________________________
>>> Chugalug mailing list
>>> Chugalug at chugalug.org
>>> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>>
>>
>>
>>
>> _______________________________________________
>> Chugalug mailing listChugalug at chugalug.orghttp://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>
>>
>>
>> _______________________________________________
>> Chugalug mailing list
>> Chugalug at chugalug.org
>> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>
>>
>
> _______________________________________________
> Chugalug mailing list
> Chugalug at chugalug.org
> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://chugalug.org/pipermail/chugalug/attachments/20140322/f5b342e9/attachment-0001.html>


More information about the Chugalug mailing list