Re: [Xen-devel] io.c:164:d25v0 Weird HVM ioemulation status 1. domain_crash called from io.c:165

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Fri, Apr 24, 2015 at 02:02:36PM +0200, Sander Eikelenboom wrote:
> Hi, 
> 
> On Xen-unstable I encountered this non stopping logspam while trying to 
> shutdown an HVM domain with 
> pci-passthrough:
> 
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.

And I saw as well with the latest unstable. Hadn't tried to narrow it down.

> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
>  etc. etc. etc.
> 
> The domain had shutdown perfectly well on earlier occasions, but this time it
> kept running. It did drop from it's assigned 3 vpcu's to 1 vpcu, but it 
> stalled 
> there.
> The log spam only stopped by destroying the guest.
> 
> Since i haven't seen it before, it's probably hard to replicate.
> 
> --
> Sander
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

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