Hi Stefan,
I can confirm that the symbols are included in the binary using gdb.
I will send you and Paolo an email with the link and credentials (if needed) so
you can download everything.
Thanks!
On jue, feb 21, 2019 at 12:11 PM, Stefan Hajnoczi wrote:
On Wed, Feb 20, 2019 at 06:56:04PM
On Wed, Feb 20, 2019 at 06:56:04PM +, 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
Hi Paolo,
This is Fernando, the one that reported the issue.
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
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:
>>
>> vdev 0x55f261d940f0 ("virtio-blk")
>> vq 0x55f261d9ee40 (idx 0)
>>
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:
>
> vdev 0x55f261d940f0 ("virtio-blk")
> vq 0x55f261d9ee40 (idx 0)
> inuse 128 vring.num 128
> old_shadow_avail_idx
Problem reproduced with virtio-scsi as well on the same guest, this time it
took less than a day.
Information from the log file:
vdev 0x55823f119f90 ("virtio-scsi")
vq 0x55823f122e80 (idx 2)
inuse 128 vring.num 128
old_shadow_avail_idx 58367 last_avail_idx 58113 avail_idx 58367
avail 0x3de8a800
Thanks for looking into this Stefan.
I rebuilt Qemu with the new patch and got a couple of guests running with the
new build. Two of them using virtio-scsi and another one using virtio-blk. Now
I'm waiting for any of them to crash.
I also set libvirt to include the guest memory in the qemu
On Wed, Feb 06, 2019 at 04:47:19PM +, Fernando Casas Schössow wrote:
> I could also repro the same with virtio-scsi on the same guest a couple of
> hours later:
>
> 2019-02-06 07:10:37.672+: starting up libvirt version: 4.10.0, qemu
> version: 3.1.0, kernel: 4.19.18-0-vanilla, hostname:
I could also repro the same with virtio-scsi on the same guest a couple of
hours later:
2019-02-06 07:10:37.672+: starting up libvirt version: 4.10.0, qemu
version: 3.1.0, kernel: 4.19.18-0-vanilla, hostname: vmsvr01.homenet.local
LC_ALL=C
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 0x55d22b8e10f0 ("virtio-blk")
vq 0x55d22b8ebe40 (idx 0)
inuse 128 vring.num 128
2019-02-06T00:40:41.742552Z
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
Are you sure this happens with both virtio-blk and virtio-scsi?
The following patch adds more debug output. You can build as follows:
$ git clone https://git.qemu.org/git/qemu.git
$ cd qemu
$ patch apply -p1
...paste the patch here...
^D
# For info on build dependencies see
Hi Stefan,
Thanks for looking into this. Please find the requested details below.
If you need any further details (like the host storage details) just let me
know.
Host details:
CPU: Intel(R) Xeon(R) CPU E3-1230 V2
Memory: 32GB (ECC)
OS: Alpine 3.9
Kernel version: 4.19.18-0-vanilla
Qemu
On Thu, Jan 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
Hi,
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 to avoid this issue so as a workaround I'm using SATA
15 matches
Mail list logo
