[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [BUG] Emulation issues


  • To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
  • From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
  • Date: Fri, 31 Jul 2015 11:39:55 +0000
  • Accept-language: en-GB, en-US
  • Cc: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Roger Pau Monne <roger.pau@xxxxxxxxxx>
  • Delivery-date: Fri, 31 Jul 2015 11:40:07 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHQyee9+pAJgVEo1EWTXUn+dTE1Kp3yPJYA///i8QCAAEREAP//8vQAgAF1SaD//+BQgAAES/FAAAEf9JAAAH3vAAAETAAA///hPoD//95N8P/+XYGQgAMy/gD//9a/AA==
  • Thread-topic: [Xen-devel] [BUG] Emulation issues

> -----Original Message-----
> From: Sander Eikelenboom [mailto:linux@xxxxxxxxxxxxxx]
> 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@xxxxxxxxxxxxx [mailto:xen-devel-
> >> bounces@xxxxxxxxxxxxx] 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@xxxxxxxxxx]
> >> > 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.
> 

Interesting.

  Paul



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.