From: Jean-Yves Migeon <jym@NetBSD.org>
To: xen-devel@lists.xensource.com
Subject: Re: unpredictable Xen crash w NetBSD 5.0.2(XEN3PAE_DOMU)
Date: Sat, 25 Sep 2010 12:26:24 +0200 [thread overview]
Message-ID: <4C9DCE50.1040700@NetBSD.org> (raw)
In-Reply-To: <AANLkTi=N0sDTAxx3FxPwdk6he2cHmKHDbe2a6YxtqD=s@mail.gmail.com>
On 25.09.2010 07:24, 彧 wrote:
> Dear all:
>
> I'm sorry I crossmail.
>
> I try setup aoe-vblade server on netbsd 5.0.2(domU)
> and I try to do some stress test with
> for i in {65536}; do dd if=/dev/zero of=/dev/etherd/e?.? bs=4K;done
> on a Linux box
> Two Xen dom0 configurations I use:
> 1. 32bits SuSE Enterprise Linux 11sp1 2.6.32.12-0.7-xen with 32bits
> Xen 4.0.0_21091_04-0.2.6
> 2. 64bits Gentoo 2.6.32-xen-r1 with 64bits Xen 4.0.0
> The NIC is RTL-8169 on board
>
> After 20~40mins later, whole system (include dom0 and Xen) will crash
> and reboot.
> xm dmesg
> dmesg
> system message log
> xend.log
> console
> output nothing at crash
>
> However if I replace NetBSD with FreeBSD 8.0p2 and SuSE JeOS 11.3
> the stress test is stable (~6hours).
>
> Can anyone give me sugguestions to figure out what's the problem?
Only suggestions to isolate the problem first, sorry :/
I occasionally encountered weird reboots, due to (virtual) ethernet
problems. They were all memory related, under reasonable load in dom0,
with pages bouncing back and forth between dom0 and domU.
What I would try (first) is to keep the NetBSD (domU, correct?) running,
but comment out the vif line in the associated xmdomain.cfg file, or
detach it, before doing your stress tests.
I'd like to see your network setup in dom0 (brctl + ifconfig), if it's
possible, too.
--
Jean-Yves Migeon
jym@NetBSD.org
next prev parent reply other threads:[~2010-09-25 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 5:24 unpredictable Xen crash w NetBSD 5.0.2(XEN3PAE_DOMU) 彧
2010-09-25 10:26 ` Jean-Yves Migeon [this message]
2010-09-28 4:34 ` 彧
2010-09-25 10:54 ` Manuel Bouyer
2010-09-25 13:36 ` 彧
2010-09-25 19:34 ` Manuel Bouyer
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=4C9DCE50.1040700@NetBSD.org \
--to=jym@netbsd.org \
--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.