qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 00/15] vhost, pc: fixes for 2.5


From: Peter Maydell
Subject: Re: [Qemu-devel] [PULL 00/15] vhost, pc: fixes for 2.5
Date: Thu, 26 Nov 2015 11:26:10 +0000

On 19 November 2015 at 13:35, Michael S. Tsirkin <address@hidden> wrote:
> The following changes since commit 8337c6cbc37c6b2184f41bab3eaff47d5e68012a:
>
>   Update version for v2.5.0-rc0 release (2015-11-13 17:10:36 +0000)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
>
> for you to fetch changes up to 1c7ba94a184df1eddd589d5400d879568d3e5d08:
>
>   exec: silence hugetlbfs warning under qtest (2015-11-19 15:26:05 +0200)
>
> ----------------------------------------------------------------
> vhost, pc: fixes for 2.5
>
> Fixes all over the place.
>
> This also re-enables a test we disabled in 2.5 cycle
> now that there's a way not to get a warning from it.
>
> Signed-off-by: Michael S. Tsirkin <address@hidden>

Hi; I've just noticed that since this pull was applied the Travis
builds have been failing:
https://travis-ci.org/qemu/qemu/builds

The log messages are rather odd but suggest a virtio-user problem:

GTESTER check-qtest-i386
blkdebug: Suspended request 'A'
blkdebug: Resuming request 'A'
main-loop: WARNING: I/O thread spun for 1000 iterations
main-loop: WARNING: I/O thread spun for 1000 iterations
main-loop: WARNING: I/O thread spun for 1000 iterations
main-loop: WARNING: I/O thread spun for 1000 iterations
[vmxnet3][WR][vmxnet3_peer_has_vnet_hdr]: Peer has no virtio
extension. Task offloads will be emulated.
GTester: last random seed: R02S8538d05b7c04668517e6c9985845363e
qemu-system-i386: Device '�P1��*' not found
qemu-system-i386: Failed to read msg header. Read 0 instead of 12.
Original request 11.
qemu-system-i386: Failed to read msg header. Read 0 instead of 12.
Original request 11.
qemu-system-i386: Device 'sd0' not found
qemu-system-i386: Failed to read msg header. Read 0 instead of 12.
Original request 11.
qemu-system-i386: Failed to read msg header. Read 0 instead of 12.
Original request 11.
qemu-system-i386: Failed to read msg header. Read 0 instead of 12.
Original request 11.
qemu-system-i386: Failed to read msg header. Read 0 instead of 12.
Original request 11.
make: *** [check-qtest-i386] Error 1

(note the corrupted string in some of the "device not found" messages --
if you look at different build logs this varies from run to run)

Can you look into this, please?

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]