On Thu, Nov 16, 2017 at 09:04:48AM -0700, Alex Williamson wrote:
> > Range is unmapped by listener but device has not been reset yet,
> > so it will get errors when attempting to access guest RAM.
>
> So IOMMU faults would occur if the device continues to try to DMA
> into that range. Sloppy orde
On Thu, 16 Nov 2017 17:59:17 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Nov 16, 2017 at 08:53:45AM -0700, Alex Williamson wrote:
> > On Thu, 16 Nov 2017 17:28:44 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Nov 16, 2017 at 01:23:39PM +0100, Greg Kurz wrote:
> > > > Hi,
> > > >
On Thu, Nov 16, 2017 at 08:53:45AM -0700, Alex Williamson wrote:
> On Thu, 16 Nov 2017 17:28:44 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Nov 16, 2017 at 01:23:39PM +0100, Greg Kurz wrote:
> > > Hi,
> > >
> > > I'm resurrecting a thread about a QEMU crash we're still hitting on
> > > pp
On Thu, 16 Nov 2017 17:28:44 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Nov 16, 2017 at 01:23:39PM +0100, Greg Kurz wrote:
> > Hi,
> >
> > I'm resurrecting a thread about a QEMU crash we're still hitting on ppc64.
> > It
> > was reported to the list by Bharata 2 months ago:
> >
> > https://li
On Thu, 16 Nov 2017 17:28:44 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Nov 16, 2017 at 01:23:39PM +0100, Greg Kurz wrote:
> > Hi,
> >
> > I'm resurrecting a thread about a QEMU crash we're still hitting on ppc64.
> > It
> > was reported to the list by Bharata 2 months ago:
> >
> > https://li
On Thu, Nov 16, 2017 at 01:23:39PM +0100, Greg Kurz wrote:
> Hi,
>
> I'm resurrecting a thread about a QEMU crash we're still hitting on ppc64. It
> was reported to the list by Bharata 2 months ago:
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg03685.html
>
> "Hi,
>
> QEMU hits t
Hi,
I'm resurrecting a thread about a QEMU crash we're still hitting on ppc64. It
was reported to the list by Bharata 2 months ago:
https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg03685.html
"Hi,
QEMU hits the below assert
qemu-system-ppc64: used ring relocated for ring 2
qemu-system-
On Thu, Sep 14, 2017 at 10:59:05AM +0200, Igor Mammedov wrote:
> On Thu, 14 Sep 2017 13:48:26 +0530
> Bharata B Rao wrote:
>
> > On Thu, Sep 14, 2017 at 10:00:11AM +0200, Igor Mammedov wrote:
> > > On Thu, 14 Sep 2017 12:31:18 +0530
> > > Bharata B Rao wrote:
> > >
> > > > Hi,
> > > >
> > >
On Thu, Sep 14, 2017 at 10:59:05AM +0200, Igor Mammedov wrote:
> On Thu, 14 Sep 2017 13:48:26 +0530
> Bharata B Rao wrote:
>
> > On Thu, Sep 14, 2017 at 10:00:11AM +0200, Igor Mammedov wrote:
> > > On Thu, 14 Sep 2017 12:31:18 +0530
> > > Bharata B Rao wrote:
> > >
> > > > Hi,
> > > >
> > >
On Thu, 14 Sep 2017 13:48:26 +0530
Bharata B Rao wrote:
> On Thu, Sep 14, 2017 at 10:00:11AM +0200, Igor Mammedov wrote:
> > On Thu, 14 Sep 2017 12:31:18 +0530
> > Bharata B Rao wrote:
> >
> > > Hi,
> > >
> > > QEMU hits the below assert
> > >
> > > qemu-system-ppc64: used ring relocated fo
On Thu, Sep 14, 2017 at 10:00:11AM +0200, Igor Mammedov wrote:
> On Thu, 14 Sep 2017 12:31:18 +0530
> Bharata B Rao wrote:
>
> > Hi,
> >
> > QEMU hits the below assert
> >
> > qemu-system-ppc64: used ring relocated for ring 2
> > qemu-system-ppc64: qemu/hw/virtio/vhost.c:649: vhost_commit: Asse
On Thu, 14 Sep 2017 12:31:18 +0530
Bharata B Rao wrote:
> Hi,
>
> QEMU hits the below assert
>
> qemu-system-ppc64: used ring relocated for ring 2
> qemu-system-ppc64: qemu/hw/virtio/vhost.c:649: vhost_commit: Assertion `r >=
> 0' failed.
>
> in the following scenario:
>
> 1. Boot guest with
Hi,
QEMU hits the below assert
qemu-system-ppc64: used ring relocated for ring 2
qemu-system-ppc64: qemu/hw/virtio/vhost.c:649: vhost_commit: Assertion `r >= 0'
failed.
in the following scenario:
1. Boot guest with vhost=on
-netdev tap,id=mynet0,script=qemu-ifup,downscript=qemu-ifdown,vhost=
13 matches
Mail list logo
