From mboxrd@z Thu Jan 1 00:00:00 1970 From: yingbin wang Subject: Re: AW: VHD BUG in xen4.0 when install windows2008 Date: Sat, 12 Jun 2010 13:04:41 +0800 Message-ID: References: <4FA716B1526C7C4DB0375C6DADBC4EA37ACEAA5FE3@LONPMAILBOX01.citrite.net> <20100508195226.GB17817@reaktio.net> <1273430440.2658.39.camel@ramone.somacoma.net> <001e01caefaa$51fd6440$f5f82cc0$@org> <1273477736.14481.22.camel@ramone.somacoma.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1273477736.14481.22.camel@ramone.somacoma.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Daniel Stodden Cc: Heiko Wundram , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org hi, had you created the patch to make tapdisk run the device queue synchronousl= y? if yes, could you tell me how to get it? thanks wyb 2010/5/10 Daniel Stodden : > On Sun, 2010-05-09 at 15:03 -0400, Heiko Wundram wrote: >> 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 o= nly 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/loc= k up, Bug, and/or all other kinds of undefined behavior, where I really hav= en't made out a pattern yet. >> >> Interestingly, these errors do not happen when using the "normal" blkbac= k-driver, and I'm very positive (at least that's what happened during my te= sting) that it's specific to Multi-VCPU, 64-bit HVM domains that the crash = occurs, independent of the number of VCPUs bound to Dom0. > > Okay, one thing which was going to happen soon is a patch to make > tapdisk run the device queue synchronously. From your description I'm > just not very convinced that this resolves such issues as well. Looks > like it needs some 64 bit testing beforehand. > > Thanks for the hints. Does HVM up there mean it's rather triggered by > qemu alone? Were you running pv drivers? > > Cheers, > Daniel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >