All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: stoeni <xen@stoeni.de>
Cc: Xen Devs <xen-devel@lists.xensource.com>
Subject: Re: PAE on xen-2.0 testing?
Date: Mon, 17 Oct 2005 15:03:48 -0400	[thread overview]
Message-ID: <1129575828.3496.139.camel@pluto.linsolutions.com> (raw)
In-Reply-To: <4353ECC6.4060200@stoeni.de>

On Mon, 2005-10-17 at 20:26 +0200, stoeni wrote:
> Mark Williamson schrieb:
> > I'm afraid if you want PAE you'll want unstable/3.0 - it'll probably never be 
> > backported to 2.0.  Xen-unstable is relatively stable now though, so you 
> > might want to try it out for evaluation purposes since it will become 3.0 
> > eventually.
> 
> ok, good to know. the 3.0 thing doesn't really work, after mailing
> hundreds :) of mails with keir yesterday the source from today broke the
> system again. gdth causes a panic .. if it compiles some vif are coming
> up, some not. same show as on saturday/sunday :(
> 
> i'll wait the next days for an upcoming source that will work on this
> maschine ;-)
> 
How long ago did you start seeing these issues and on what hardware.
With two or three nics I see this on an SMP Athlon and a UP P4.
By this I mean vif not mapping to a bridge or mapping ro the wrong
bridge.

 If I go back to a single nic setup using a secondary ip on the dom0 for
the domU gateway things are playing nice.

 With two and three nics and bridge between dom0's I just increased the
rate at which of my hair follicle count declines :-)


Regards,
Ted

  reply	other threads:[~2005-10-17 19:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 18:16 PAE on xen-2.0 testing? stoeni
2005-10-17 18:19 ` David F Barrera
2005-10-17 18:21 ` Mark Williamson
2005-10-17 18:26   ` stoeni
2005-10-17 19:03     ` Ted Kaczmarek [this message]
2005-10-17 20:56       ` stoeni
  -- strict thread matches above, loose matches on Subject: below --
2005-10-18  5:54 Ian Pratt
2005-10-18  8:12 ` stoeni
2005-10-18  8:17   ` Steven Hand
2005-10-18  8:30     ` stoeni

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=1129575828.3496.139.camel@pluto.linsolutions.com \
    --to=tedkaz@optonline.net \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen@stoeni.de \
    /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.