From: Thomas Huth <1483070@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1483070] Re: VIRTIO Sequential Write IOPS limits not working
Date: Tue, 07 Aug 2018 17:43:12 -0000 [thread overview]
Message-ID: <153366379234.3443.2579726964190926825.malone@wampee.canonical.com> (raw)
In-Reply-To: 20150810001525.6231.66973.malonedeb@gac.canonical.com
Has this issue ever been fixed? If not, is there still interest in
fixing it? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1483070
Title:
VIRTIO Sequential Write IOPS limits not working
Status in QEMU:
Incomplete
Bug description:
Root Problem:
IOPS limit does not work for VIRTIO devices if the disk workload is a sequential write.
To confirm:
IDE disk devices - the IOPS limit works fine. Disk transfer speed limit works fine.
VIRTIO disk devices - the IOPS limit works fine for random IO (write/read) and sequential read, but not for sequential write. Disk transfer speed limits work fine.
Tested on Windows 7,10 and 2k12 (Fedora drivers used and here is the twist):
virtio-win-0.1.96 (stable) or older won't limit write IO if workload is sequential.
virtio-win-0.1.105 (latest) or newer will limit but I have had two test machines crash when under high workload using IOPS limit.
For Linux:
The issue is also apparent, tested on Ubuntu 14.04
On the hypervisor (using KVM) machine I have tried with Qemu 2.1.2
(3.16.0-4-amd64 - Debian 8) and Qemu 2.3.0 (3.19.8-1-pve - Proxmox 3.4
and 4) using multiple machines but all are 64bit intel.
Even though the latest VIRTIO guest drivers fix the problem, the guest
drivers shouldn't be able to ignore the limits the host puts in place
or am I missing something??
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1483070/+subscriptions
next prev parent reply other threads:[~2018-08-07 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 0:15 [Qemu-devel] [Bug 1483070] [NEW] VIRTIO Sequential Write IOPS limits not working James Watson
2015-08-10 9:59 ` Stefan Hajnoczi
2015-08-13 23:34 ` Peter Lieven
2015-08-14 6:26 ` Alberto Garcia
2018-08-07 17:43 ` Thomas Huth [this message]
2018-10-07 4:17 ` [Qemu-devel] [Bug 1483070] " Launchpad Bug Tracker
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=153366379234.3443.2579726964190926825.malone@wampee.canonical.com \
--to=1483070@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.