org
Subject: Re: [Qemu-devel] Guest unresponsive after Virtqueue size exceeded error
Hi Ladi,
After running for about 15hrs two different guests (one Windows, one Linux)
crashed with around 1 hour difference and the same error in qemu log "Virqueue
size exceeded".
The Linux guest was already runn
Hi Ladi,
After running for about 15hrs two different guests (one Windows, one Linux)
crashed with around 1 hour difference and the same error in qemu log "Virqueue
size exceeded".
The Linux guest was already running on virtio_scsi and without virtio_balloon.
:(
I compiled and attached gdbserve
Hi Ladi,
Small update. Memtest86+ was running on the host for more than 54 hours. 8
passes were completed and no memory errors found. For now I think we can assume
that the host memory is ok.
I just started all the guests one hour ago. I will monitor them and once one
fails I will attach the d
Hi Fernando,
On Wed, Jun 21, 2017 at 2:19 PM, Fernando Casas Schössow
wrote:
> Hi Ladi,
>
> Sorry for the delay in my reply.
> I will leave the host kernel alone for now then.
> For the last 15 hours or so I'm running memtest86+ on the host. So far so
> good. Two passes no errors so far. I will t
Hi Ladi,
Sorry for the delay in my reply.
I will leave the host kernel alone for now then.
For the last 15 hours or so I'm running memtest86+ on the host. So far so good.
Two passes no errors so far. I will try to leave it running for at least
another 24hr and report back the results. Hopefully
On Tue, Jun 20, 2017 at 8:30 AM, Fernando Casas Schössow
wrote:
> Hi Ladi,
>
> In this case both guests are CentOS 7.3 running the same kernel
> 3.10.0-514.21.1.
> Also the guest that fails most frequently is running Docker with 4 or 5
> containers.
>
> Another thing I would like to mention is tha
Hi Ladi,
In this case both guests are CentOS 7.3 running the same kernel 3.10.0-514.21.1.
Also the guest that fails most frequently is running Docker with 4 or 5
containers.
Another thing I would like to mention is that the host is running on Alpine's
default grsec patched kernel. I have the op
Hi Fernando,
On Tue, Jun 20, 2017 at 12:10 AM, Fernando Casas Schössow
wrote:
> Hi Ladi,
>
> Today two guests failed again at different times of day.
> One of them was the one I switched from virtio_blk to virtio_scsi so this
> change didn't solved the problem.
> Now in this guest I also disabled
Hi Ladi,
Today two guests failed again at different times of day.
One of them was the one I switched from virtio_blk to virtio_scsi so this
change didn't solved the problem.
Now in this guest I also disabled virtio_balloon, continuing with the
elimination process.
Also this time I found a diffe
On Fri, Jun 16, 2017 at 12:11 PM, Fernando Casas Schössow
wrote:
> Hi Ladi,
>
> Thanks a lot for looking into this and replying.
> I will do my best to rebuild and deploy Alpine's qemu packages with this
> patch included but not sure its feasible yet.
> In any case, would it be possible to have th
Hi Ladi,
Thanks a lot for looking into this and replying.
I will do my best to rebuild and deploy Alpine's qemu packages with this patch
included but not sure its feasible yet.
In any case, would it be possible to have this patch included in the next qemu
release?
The current error message is he
Hi,
On Wed, Jun 14, 2017 at 11:56 PM, Fernando Casas Schössow
wrote:
> Hi there,
>
> I recently migrated a Hyper-V host to qemu/kvm runing on Alpine Linux 3.6.1
> (kernel 4.9.30 -with grsec patches- and qemu 2.8.1).
>
> Almost on daily basis at least one of the guests is showing the following
>
Hi there,
I recently migrated a Hyper-V host to qemu/kvm runing on Alpine Linux 3.6.1
(kernel 4.9.30 -with grsec patches- and qemu 2.8.1).
Almost on daily basis at least one of the guests is showing the following error
in the log and the it needs to be terminated and restarted to recover it:
q
13 matches
Mail list logo