From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= Subject: Re: [BUG] Emulation issues Date: Fri, 31 Jul 2015 13:41:55 +0200 Message-ID: <55BB5F03.8080104@citrix.com> References: <55B8A825.5020608@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD02F55E620@AMSPEX01CL02.citrite.net> <55B8ACB0.6060406@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD02F55E941@AMSPEX01CL02.citrite.net> <55B8DB02.8000904@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD02F55FBC0@AMSPEX01CL02.citrite.net> <55B9F98F.1000906@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD02F55FBF8@AMSPEX01CL02.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD02F55FCB3@AMSPEX01CL02.citrite.net> <55BA213E.2080605@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD02F560050@AMSPEX01CL02.citrite.net> <55BA2447.90407@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD02F5600C0@AMSPEX01CL02.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD02F56C571@AMSPEX01CL01.citrite.net> <64107571.20150731131152@eikelenboom.it> <9AAE0902D5BC7E449B7C8E4E778ABCD02F56D6AE@AMSPEX01CL01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZL8hP-0005Sp-2j for xen-devel@lists.xenproject.org; Fri, 31 Jul 2015 11:42:03 +0000 In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02F56D6AE@AMSPEX01CL01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant , Sander Eikelenboom Cc: Andrew Cooper , xen-devel List-Id: xen-devel@lists.xenproject.org El 31/07/15 a les 13.39, Paul Durrant ha escrit: >> -----Original Message----- >> From: Sander Eikelenboom [mailto:linux@eikelenboom.it] >> Sent: 31 July 2015 12:12 >> To: Paul Durrant >> Cc: Andrew Cooper; Roger Pau Monne; xen-devel >> Subject: Re: [Xen-devel] [BUG] Emulation issues >> >> >> Friday, July 31, 2015, 12:22:16 PM, you wrote: >> >>>> -----Original Message----- >>>> From: xen-devel-bounces@lists.xen.org [mailto:xen-devel- >>>> bounces@lists.xen.org] On Behalf Of Paul Durrant >>>> Sent: 30 July 2015 14:20 >>>> To: Andrew Cooper; Roger Pau Monne; xen-devel >>>> Subject: Re: [Xen-devel] [BUG] Emulation issues >>>> >>>>> -----Original Message----- >>>>> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com] >>>>> Sent: 30 July 2015 14:19 >>>>> To: Paul Durrant; Roger Pau Monne; xen-devel >>>>> Subject: Re: [BUG] Emulation issues >>>>> >>>>> On 30/07/15 14:12, Paul Durrant wrote: >>>>>>> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >>>>>>> (XEN) domain_crash called from io.c:166 >>>>>>> (XEN) d19v0 weird emulation state 1 >>>>>>> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >>>>>>> (XEN) domain_crash called from io.c:166 >>>>>>> (XEN) d19v0 weird emulation state 1 >>>>>>> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >>>>>>> (XEN) domain_crash called from io.c:166 >>>>>>> >>>>>> Hmm. Can't understand how that's happening... handle_pio() >> shouldn't >>>> be >>>>> called unless the state is STATE_IORESP_READY and yet the inner >> function >>>> is >>>>> hitting the default case in the switch. >>>>> >>>>> Sounds like something is changing the state between the two checks. Is >>>>> this shared memory writeable by qemu? >>>>> >>>> >>>> No, this is the internal state. I really can't see how it's being changed. >>>> >> >>> I've tried to replicate your test on my rig (which is an old AMD box but quite >> a big one). Even so I only seem to get about half the VMs to start. The >> shutdown works fine, and I don't see any problems on the Xen console. I'm >> using an older build of Xen but still one with my series in. I'll try pulling up to >> the same commit as you and try again. >> >>> Paul >> >> Hi Paul, >> >> From what i recall it started around when Tiejun Chen's series went in. >> Since I can reproduce this at will I will attempt to perform a bisection. Maybe this can help narrow down the issue. Roger.