From: Peter Maloney <1769189@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1769189] Re: Issue with qemu 2.12.0 + SATA
Date: Sun, 22 Jul 2018 21:06:58 -0000 [thread overview]
Message-ID: <153229361813.2927.7188400353223146067.malone@wampee.canonical.com> (raw)
In-Reply-To: 152544791493.32626.6219738999075353422.malonedeb@gac.canonical.com
Could this affect virtio-scsi? I'm not so sure since it's not perfectly
reliable to reproduce, but v2.12.0 was hanging for me for a few minutes
at a time with virtio-scsi cache=writeback showing 100% disk util%. I
never had issues booting up, and didn't try SATA. v2.11.1 was fine.
My first attempt to bisect didn't turn out right... had some false
positives I guess. The 2nd attempt (telling git the bads from first try)
got to 89e46eb477113550485bc24264d249de9fd1260a as latest good (which is
4 commits *after* the bisect by John Snow) and
7273db9d28d5e1b7a6c202a5054861c1f0bcc446 as bad.
But testing with this patch, it seems to work (or false positive
still... after a bunch of usage). And so I didn't finish the bisect.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1769189
Title:
Issue with qemu 2.12.0 + SATA
Status in QEMU:
Fix Committed
Bug description:
[EDIT: I first thought that OVMF was the issue, but it turns out to be
SATA]
I had a Windows 10 VM running perfectly fine with a SATA drive, since
I upgraded to qemu 2.12, the guests hangs for a couple of minutes,
works for a few seconds, and hangs again, etc. By "hang" I mean it
doesn't freeze, but it looks like it's waiting on IO or something, I
can move the mouse but everything needing disk access is unresponsive.
What doesn't work: qemu 2.12 with SATA
What works: using VirIO-SCSI with qemu 2.12 or downgrading qemu to 2.11.1 and keep using SATA.
Platform is arch linux 4.16.7 on skylake and Haswell, I have attached
the vm xml file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1769189/+subscriptions
next prev parent reply other threads:[~2018-07-22 21:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 15:31 [Qemu-devel] [Bug 1769189] [NEW] Issue with qemu 2.12.0 + UEFI François Guerraz
2018-05-05 18:31 ` [Qemu-devel] [Bug 1769189] " Adee
2018-05-11 12:28 ` Mathias Bösl
2018-05-15 8:42 ` [Qemu-devel] [Bug 1769189] Re: Issue with qemu 2.12.0 + SATA François Guerraz
2018-05-15 16:30 ` Dr. David Alan Gilbert
2018-05-16 21:01 ` blackdevil
2018-05-23 17:30 ` Bruce Rogers
2018-05-25 1:08 ` John Snow
2018-05-25 12:59 ` Bruce Rogers
2018-05-31 0:25 ` John Snow
2018-05-31 19:02 ` John Snow
2018-06-13 20:43 ` John Snow
2018-06-14 7:01 ` Robert Hu
2018-06-14 16:36 ` John Snow
2018-07-22 21:06 ` Peter Maloney [this message]
2018-07-23 18:39 ` John Snow
2018-08-15 7:22 ` Thomas Huth
2018-05-20 17:54 Andrew Randrianasulu
2018-06-01 11:32 ` Stefan Hajnoczi
2018-06-01 16:58 Andrew Randrianasulu
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=153229361813.2927.7188400353223146067.malone@wampee.canonical.com \
--to=1769189@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.