I managed to upgrade to qemu 4.1 on a test KVM host and I can confirm I can't
repro the issue in this version.
Great news that is fixed in 4.1.
Thanks everyone for your inputs and the fast replies.
Kind regards,
Fernando
On vie, oct 25, 2019 at 12:28 PM, Fernando Casas Schössow
wrote
Thanks for the reply Kevin.
I will do my best to upgrade to 4.1, test again and report back if this is
fixed or not in that version.
Hopefully it is.
Fernando
On vie, oct 25, 2019 at 12:07 PM, Kevin Wolf wrote:
Am 23.10.2019 um 19:28 hat Fernando Casas Schössow geschrieben:
Hi John, Thanks
BTW just to be clear, qemu is crashing in this scenario *only* if
iothread is enabled for the guest.
Without iothread enabled the operation is completed without any
problems.
On jue, oct 24, 2019 at 11:07 PM, Fernando Casas Schössow
wrote:
> Today I updated to qemu 4.0.1 si
for analysis if needed.
While waiting for replies I will check if I can upgrade to qemu 4.1.0,
try to repro and provide the results.
Thanks.
Fernando
On mié, oct 23, 2019 at 7:57 PM, Fernando Casas Schössow
wrote:
> In virsh I would do this while the guest is running:
>
> virsh at
it to try with 4.0 first and get the strack trace or it will not
help and the only way to go is with 4.1 (or dev)?
Thanks,
Fernando
On mié, oct 23, 2019 at 5:34 PM, John Snow wrote:
On 10/18/19 5:41 PM, Fernando Casas Schössow wrote:
Hi,
Hi! Thanks for the report.
Today while working with two
9 at 7:33 PM, John Snow wrote:
On 10/23/19 1:28 PM, Fernando Casas Schössow wrote:
Hi John, Thanks for looking into this. I can quickly repro the problem with
qemu 4.0 binary with debugging symbols enabled as I have it available already.
Doing the same with qemu 4.1 or development head may be too
Hi,
Today while working with two different Windows Server 2012 R2 guests I
found that when I try to attach an ISO file to a SCSI CD-ROM device
through libvirt (virsh or virt-manager) while the guest is running,
qemu crashes and the following message is logged:
Assertion failed:
Hi,
Today while working with two different Windows Server 2012 R2 guests I found
that when I try to attach an ISO file to a SCSI CD-ROM device through libvirt
(virsh or virt-manager) while the guest is running, qemu crashes and the
following message is logged:
Assertion failed:
+, Fernando Casas Schössow wrote:
Regarding the dumps I have three of them including guest memory, 2 for
virtio-scsi, 1 for virtio-blk, in case a comparison may help to confirm which
is the proble.) I can upload them to a server you indicate me or I can also put
them on a server so you can
with this!
Kind regards,
Fernando
On mié, feb 20, 2019 at 6:53 PM, Paolo Bonzini wrote:
On 20/02/19 17:58, Stefan Hajnoczi wrote:
On Mon, Feb 18, 2019 at 07:21:25AM +, Fernando Casas Schössow wrote:
It took a few days but last night the problem was reproduced. This is the
information from the log
s.
On lun, feb 18, 2019 at 8:21 AM, Fernando Casas Schössow
wrote:
It took a few days but last night the problem was reproduced.
This is the information from the log:
vdev 0x55f261d940f0 ("virtio-blk")
vq 0x55f261d9ee40 (idx 0)
inuse 128 vring.num 128
old_shadow_avail_idx 58874 last_avail
dumps as I
understood you will want to look at both (qemu dump and guest memory dump).
I will reply to this thread once I have any news.
Kind regards.
Fernando
On lun, feb 11, 2019 at 4:17 AM, Stefan Hajnoczi wrote:
On Wed, Feb 06, 2019 at 04:47:19PM +, Fernando Casas Schössow wrote:
I could
on forward
and find the cause of this issue.
Thanks.
On mié, feb 6, 2019 at 8:15 AM, Fernando Casas Schössow
wrote:
I can now confirm that the same happens with virtio-blk and virtio-scsi.
Please find below the qemu log enhanced with the new information added by the
patch provided by Stefan:
vdev 0x55
2552Z qemu-system-x86_64: Virtqueue size exceeded
I just changed the disk back to virtio-scsi so I can repro this again with the
patched qemu and report back.
Thanks.
On lun, feb 4, 2019 at 8:24 AM, Fernando Casas Schössow
wrote:
I can test again with qemu 3.1 but with previous ve
I can test again with qemu 3.1 but with previous versions yes, it was happening
the same with both virtio-blk and virtio-scsi.
For 3.1 I can confirm it happens for virtio-scsi (already tested it) and I can
test with virtio-blk again if that will add value to the investigation.
Also I'm
31, 2019 at 11:32:32AM +, Fernando Casas Schössow wrote:
Sorry for resurrecting this thread after so long but I just upgraded the host
to Qemu 3.1 and libvirt 4.10 and I'm still facing this problem. At the moment I
cannot use virtio disks (virtio-blk nor virtio-scsi) with my guests in order
rustrating that after all this time I couldn't find the cause for
this issue so any ideas are welcome.
Thanks.
Fernando
____
From: Fernando Casas Schössow
Sent: Saturday, June 24, 2017 10:34 AM
To: Ladi Prosek
Cc: qemu-de...@nongnu.org
Subject: Re: [Qemu-de
more than willing to share them.
Thanks in advance.
Fernando
On jue, oct 18, 2018 at 3:40 PM, Fernando Casas Schössow
wrote:
Hi Kevin,
Not at the moment. This is a production system and pretty much up to date but
can't upgrade to 3.0 yet.
If the dump can be of any use, I can upload it somewhere
Fernando Casas Schössow geschrieben:
I hope this email finds you well and I apologize in advance for resurrecting
this thread. I'm currently running on qemu 2.12.1 and I'm still having this
issue every few days but now I managed to get a core dump generated (without
including the guest memory
Schössow
Cc: qemu-devel; qemu-block@nongnu.org; Jeff Cody
Subject: Re: [Qemu-devel] qemu process crash: Assertion failed:
QLIST_EMPTY(>tracked_requests)
On Wed, Dec 13, 2017 at 03:33:01PM +0000, Fernando Casas Schössow wrote:
> Maybe I’m missing something here but, if I recall correctly, th
the debug info. :(
But I’m not 100% sure at the moment.
Sent from my iPhone
On 13 Dec 2017, at 12:23, Stefan Hajnoczi
<stefa...@gmail.com<mailto:stefa...@gmail.com>> wrote:
On Mon, Dec 11, 2017 at 01:42:38PM +0000, Fernando Casas Schössow wrote:
Hello Stefan,
Thanks for your reply.
Fortunat
.
Thanks.
Fer
Sent from my iPhone
On 11 Dec 2017, at 12:56, Stefan Hajnoczi
<stefa...@gmail.com<mailto:stefa...@gmail.com>> wrote:
On Thu, Dec 07, 2017 at 10:18:52AM +0000, Fernando Casas Schössow wrote:
Hi there,
Last night while doing a backup of a guest using the live snapsh
22 matches
Mail list logo
