From: "Heiko Wundram" <modelnine@modelnine.org>
To: 'Daniel Stodden' <daniel.stodden@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: AW: VHD BUG in xen4.0 when install windows2008
Date: Sun, 9 May 2010 21:03:32 +0200 [thread overview]
Message-ID: <001e01caefaa$51fd6440$f5f82cc0$@org> (raw)
In-Reply-To: <1273430440.2658.39.camel@ramone.somacoma.net>
As I'm seeing a similar behavior of tapdisk2 (see my recent posts to xen-users, especially "blktap2, also broken in current pv_ops stable-2.6.32.x?"), I can confirm that at least in my testing (I've done some more over the weekend, re. that message), this is indeed an "SMP-related" problem, but only for HVM-64bit domains.
What I can basically say is that:
1) Uni/Multi/32-bit/64-bit PV domains run properly.
1) Uni-VCPU, 32-bit HVM domains run properly.
2) Multi-VCPU, 32-bit HVM domains run properly.
3) Uni-VCPU, 64-bit HVM domains run properly.
4) Multi-VCPU, 64-bit HVM domains cause tapdisk2 to segfault, sometimes, under heavy I/O, and if that happens, causes the Dom0-kernel to freeze/lock up, Bug, and/or all other kinds of undefined behavior, where I really haven't made out a pattern yet.
Interestingly, these errors do not happen when using the "normal" blkback-driver, and I'm very positive (at least that's what happened during my testing) that it's specific to Multi-VCPU, 64-bit HVM domains that the crash occurs, independent of the number of VCPUs bound to Dom0.
--- Heiko.
-----Ursprüngliche Nachricht-----
Von: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] Im Auftrag von Daniel Stodden
Gesendet: Sonntag, 9. Mai 2010 20:41
An: Pasi Kärkkäinen
Cc: Ian Pratt; yingbin wang; xen-devel@lists.xensource.com
Betreff: Re: [Xen-devel] VHD BUG in xen4.0 when install windows2008
On Sat, 2010-05-08 at 15:52 -0400, Pasi Kärkkäinen wrote:
> On Sun, May 09, 2010 at 01:02:42AM +0800, yingbin wang wrote:
> > I have try xenlinux 2.6.18.8. the problem also appear. os can not startup.
> >
> > Windows 2008 R2 Standard Edition 64(disk size: 20G, C:\ 15G, D:\ 5G) on
> > vhd file, the problem appear.
> > does anyone successfully install Windows 2008 R2 Standard Edition 64(disk
> > size: 20G, C:\ 15G, D:\ 5G) on vhd file??
> > env : (xen4.0, kernel2.6.31.13) or (xen4.0, kernel2.6.18.8)
> >
>
> Looking at the log (below) it seems the 'tapdisk2' process segfaults (crashes).
> Sounds like a bug in it..
This is the loop pulling requests from the userspace I/O ring.
Missing a sanity check on the message content, hence the crash.
I would have bet it's smp-related, but sounds as if not.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-09 19:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 5:13 VHD BUG in xen4.0 when install windows2008 yingbin wang
2010-05-08 10:04 ` Ian Pratt
2010-05-08 12:46 ` yingbin wang
2010-05-08 17:02 ` yingbin wang
2010-05-08 19:52 ` Pasi Kärkkäinen
2010-05-09 18:40 ` Daniel Stodden
2010-05-09 19:03 ` Heiko Wundram [this message]
2010-05-10 7:48 ` AW: " Daniel Stodden
2010-05-10 8:17 ` AW: " Heiko Wundram
2010-05-10 21:41 ` Daniel Stodden
2010-06-12 5:04 ` yingbin wang
2010-06-12 8:19 ` Daniel Stodden
2010-06-12 10:47 ` yingbin wang
2010-06-13 0:06 ` Daniel Stodden
2010-06-13 3:01 ` yingbin wang
2010-06-13 9:23 ` Daniel Stodden
2010-05-15 16:02 ` yingbin wang
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='001e01caefaa$51fd6440$f5f82cc0$@org' \
--to=modelnine@modelnine.org \
--cc=daniel.stodden@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).