All of lore.kernel.org
 help / color / mirror / Atom feed
From: stoeni <xen@stoeni.de>
To: Xen Devs <xen-devel@lists.xensource.com>
Subject: Re: PAE on xen-2.0 testing?
Date: Mon, 17 Oct 2005 22:56:30 +0200	[thread overview]
Message-ID: <43540FFE.8090002@stoeni.de> (raw)
In-Reply-To: <1129575828.3496.139.camel@pluto.linsolutions.com>

Ted Kaczmarek schrieb:
 > How long ago did you start seeing these issues and on what hardware.

box is: 2*2.8xeon (fsb 800) with intel chipset 7230, 6x1gb ram, single
e100 and dual e1000 (only the first e1000 active) and 150gb raid5 on
icp/gdth with debian 3.1 (sarge) as base system.

first try with xen 3.0 because auf 6gb ram. xen 2.0.7 sees only 3g ram
in this machine, don't know why, other boxes (ten at production) using
full 4gb ram on xen 2.0.7.

> 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.

same behavior with the sources from today. vif assigned to first domU,
second domU crashes, third domU got a vif but doesnt work. very strange.

actual i did a make uninstall an used release  "Sun Oct 16 17:25:15 2005
+0100 7396:9b51e7637676", starting three domains gives the following
results:

one network vif3.1 (why 3.1 and not 2.1?)

domU 1 up, no networking
domU 2 up, no networking
domU 3 did not start

also nice, all domains configured with 1024 mb ram, but look here:

Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       123    -      4  r-----     19.7
vm-tempo           1      1023    0      1  -b----     12.5
vm-tempo1          2      1024    0      1  -b----      0.6

why 1023 and 1024? ;-)

very strange. yesterday with some help from keir i got it up and running
with the sources from sunday, but can't get it up and running after
using the sources from today (doing make uninstall an so on). restored
some backups etc. but it's not working at the moment.

after shuting down this domains vm-tempo doesn't find a root fs ...
arghl .. all domains are equal except the logical volumes and networking
stuff.

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

thanks for the tip, it's worth a try. maybe i'll try the e100 instead of
the e1000.

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

hrhr ... until xen-unstable i also had much and long hairs :))

-- 
Tschaw/2,
Stoeni!

++ Please remember: rm -rf means "read mail -really fast" ++

  reply	other threads:[~2005-10-17 20:56 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
2005-10-17 20:56       ` stoeni [this message]
  -- 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=43540FFE.8090002@stoeni.de \
    --to=xen@stoeni.de \
    --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.