On Feb 15, 2005, at 12:42 PM, Tom Morris wrote:
I should have noted that I was testing and wanted to make sure that I did not have any resource issues. So that is why the guest was defined with a excessive amount of storage!
This very well might be your problem.
It may be that it's stuck waiting for what VM considers its entire working set to be paged in, and since that's A LOT, it's never actually in a state where it can proceed, and eventually your network stuff gets confused and times out.
I'd recommend something a little less extravagant, like 384 or 512 MB. That might just fix your problem all by itself.
Adam
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
