From: Matt Ayres <matta@tektonic.net>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Linux 2.6 guest BUG().
Date: Wed, 01 Feb 2006 14:07:48 -0500 [thread overview]
Message-ID: <43E10704.1040506@tektonic.net> (raw)
In-Reply-To: <5cfd4b0cbcba9c2d15fab43f57ea87b8@cl.cam.ac.uk>
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.
prev parent reply other threads:[~2006-02-01 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1F40Cd-00042S-PI@xenbits.xensource.com>
2006-01-31 20:30 ` [Xen-changelog] Fix VCPU locking in sched_adjdom for multi-VCPU guests Matt Ayres
2006-01-31 22:35 ` Keir Fraser
2006-01-31 22:42 ` Matt Ayres
2006-01-31 23:57 ` Keir Fraser
2006-02-01 16:08 ` Linux 2.6 guest BUG(). (was: Re: Re: [Xen-changelog] Fix VCPU locking in sched_adjdom for multi-VCPU guests) Matt Ayres
2006-02-01 16:27 ` Keir Fraser
2006-02-01 16:34 ` Linux 2.6 guest BUG() Matt Ayres
2006-02-01 19:07 ` Matt Ayres [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E10704.1040506@tektonic.net \
--to=matta@tektonic.net \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.