From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
hdegoede@redhat.com, Andrey Korolyov <andrey@xdel.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] usb-storage assertions
Date: Wed, 13 Jan 2016 17:13:46 +0100 [thread overview]
Message-ID: <1452701626.11179.3.camel@redhat.com> (raw)
In-Reply-To: <20160112145655.GO17626@redhat.com>
On Di, 2016-01-12 at 14:56 +0000, Daniel P. Berrange wrote:
> On Tue, Jan 12, 2016 at 03:36:40PM +0100, Kevin Wolf wrote:
> > Am 12.01.2016 um 15:17 hat Gerd Hoffmann geschrieben:
> > > On Sa, 2016-01-09 at 20:34 +0300, Andrey Korolyov wrote:
> > > > Hello,
> > > >
> > > > during regular operations within linux guest with USB EHCI frontend I
> > > > am seeing process crashes with an assert during regular operations
> > > > like dpkg install:
> > > >
> > > > hw/usb/dev-storage.c:334: usb_msd_handle_reset: Assertion `s->req ==
> > > > ((void *)0)' failed.
> > <iotune>
> > <total_bytes_sec>10000000</total_bytes_sec>
> > <read_iops_sec>400000</read_iops_sec>
> > <write_iops_sec>100000</write_iops_sec>
> > </iotune>
> Yes, that works with QEMU and will map through to the -drive I/O
> tuning parameters.
Works, successfully slowing down things to the point that a git clone of
a linux kernel source tree from another machine in the same lan takes
hours instead of minutes.
That doesn't seem to be enough to trigger the asserts though :(
Things are very slow but rock solid ...
cheers,
Gerd
next prev parent reply other threads:[~2016-01-13 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 17:34 [Qemu-devel] usb-storage assertions Andrey Korolyov
2016-01-12 14:17 ` Gerd Hoffmann
2016-01-12 14:36 ` Kevin Wolf
2016-01-12 14:56 ` Daniel P. Berrange
2016-01-13 16:13 ` Gerd Hoffmann [this message]
2016-01-13 16:28 ` Andrey Korolyov
2016-01-15 18:08 ` Andrey Korolyov
2016-01-18 9:38 ` Gerd Hoffmann
2016-01-18 9:50 ` Andrey Korolyov
2016-01-18 13:55 ` Gerd Hoffmann
2016-01-18 23:49 ` Andrey Korolyov
2016-01-19 7:13 ` Gerd Hoffmann
2016-01-19 10:59 ` Andrey Korolyov
2016-01-19 11:44 ` Gerd Hoffmann
2016-01-19 14:19 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1452701626.11179.3.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=andrey@xdel.ru \
--cc=berrange@redhat.com \
--cc=hdegoede@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).