From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Ayres Subject: Re: Linux 2.6 guest BUG(). Date: Wed, 01 Feb 2006 14:07:48 -0500 Message-ID: <43E10704.1040506@tektonic.net> References: <43DFC8ED.70400@tektonic.net> <43DFE7D8.2000607@tektonic.net> <43E0DD0E.20600@tektonic.net> <5cfd4b0cbcba9c2d15fab43f57ea87b8@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5cfd4b0cbcba9c2d15fab43f57ea87b8@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 1 Feb 2006, at 16:08, Matt Ayres wrote: > >> I can provide dozens of BUG()'s if required. It just happened again >> on a host in dom0 to the sshd daemon and now that port is locked >> (netstat -nlp reports "-" as the process name). I am able to access >> the server via the console. >> >> I assume you mean Xen's memory usage. I am showing 141MB free out of >> 8112MB total. Our scripts to add accounts don't allow adding more >> accounts then there is memory for, we actually leave about 128MB as a >> buffer. > > That's a bit odd then. If you don't explicitly specify dom0's memory > allocation at boot time then you should end up with 128MB 'slack' left > unallocated. And that should all be <4GB. > > If you are giving dom0 all of memory on boot, and then reducing it > later, that could be a problem (dom0 may end up giving back only memory > >4GB). > Just as an update, I just "upgraded" this specific host from -unstable to 3.0-testing (3.0.1) and I will report back if I still receive these BUG()'s.