after much pain ripping out vmware's modules and hard stopping it's services I managed to run <a href="http://vmware-config.pl">vmware-config.pl</a> and I think it fixed it (at least for now) Gotta remember to run that every damn time I let the machine run updates and it pulls a new kernel.<br>
<br><div class="gmail_quote">On Sat, Mar 6, 2010 at 3:15 AM, John Roach <span dir="ltr"><<a href="mailto:jroach@simplicitysys.com">jroach@simplicitysys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I recently had this happen with one of mine, I fixed it by giving the<br>
machine some extra memory and allocating it to the Virtual machine.<br>
<div class="im"><br>
Paul Gray wrote:<br>
> TJ Vance wrote:<br>
><br>
>> Experiencing much the same here. Many posts suggest just using older<br>
>> vmware. I'm on 2.0.1 and just have the manager boot all my VMs so as to<br>
>> not bother with the administrative interface but will eventually need to<br>
>> remedy.<br>
>><br>
>> Cheers<br>
>> TJ<br>
>> (sent from android)<br>
>><br>
>><br>
>>> On Mar 5, 2010 11:55 PM, <<a href="mailto:jrnosee@gmail.com">jrnosee@gmail.com</a><br>
>>> <mailto:<a href="mailto:jrnosee@gmail.com">jrnosee@gmail.com</a>>> wrote:<br>
>>><br>
>>> I continually have problems accessing my vmware server 2 running on<br>
>>> ubuntu. It will work for a bit after restarting the box, but then it<br>
>>> stops working. Eventually I can't even see the login box anymore.<br>
>>><br>
>>><br>
><br>
> Any chance you both have e1000 nics?<br>
><br>
><br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</div></div></blockquote></div><br>