From: "Roger Pau Monné" <roger.pau@entel.upc.edu>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: qemu-xen qdisk performance
Date: Mon, 13 Feb 2012 12:37:03 +0100 [thread overview]
Message-ID: <CAPLaKK7dimHzig_s-_9gmpV5soWe9DhVfNtDFzquFpRg7V2ZhA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1202101550540.7456@kaball-desktop>
2012/2/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>:
> On Fri, 10 Feb 2012, Roger Pau Monné wrote:
>> Hello,
>>
>> I've recently setup a Linux Dom0 with a 3.0.17 kernel and Xen 4.1.2,
>> and since the 3.x series doesn't have blktap support I'm using qdisk
>> to attach raw images. I've been playing with small images, something
>> like 1GB, and everything seemed fine, speed was not fantastic but it
>> was ok. Today I've set up a bigger machine, with a 20GB raw hdd and
>> the disk write throughput is really slow, inferior to 0.5MB/s. I'm
>> trying to install a Debian PV there, and after more than 3 hours it is
>> still installing the base system.
>>
>> I've looked at the xenstore backend entries, and everything looks fine:
>>
>> /local/domain/0/backend/qdisk/21/51712/frontend =
>> "/local/domain/21/device/vbd/51712" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/params =
>> "aio:/hdd/vm/servlet/servlet.img" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/frontend-id = "21" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/online = "1" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/removable = "0" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/bootable = "1" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/state = "4" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/dev = "xvda" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/type = "tap" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/mode = "w" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/feature-barrier = "1" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/info = "0" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/sector-size = "512" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/sectors = "40960000" (n0,r21)
>> /local/domain/0/backend/qdisk/21/51712/hotplug-status = "connected" (n0,r21)
>>
>> Also, the related qemu-dm process doesn't seem to be hung by CPU, in
>> fact it is reporting a CPU usage of 0% almost all the time. I've
>> attached to the qemu-dm process with strace, and it is doing lseeks
>> and writes like crazy, is this normal? Is there any improvement when
>> using qemu-upstream?
>
> Yes, great improvements.
> The old qemu-xen uses threads to simulate async IO so it is very slow;
> upstream QEMU uses Linux AIO and is much faster.
That's great news, so qdisk performance in qemu-upstream should be
similar to blktap?
> I wouldn't expect it to hang completely though, that might be a bug.
No, it doesn't hang completely, just very slow.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-13 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 15:22 qemu-xen qdisk performance Roger Pau Monné
2012-02-10 15:53 ` Stefano Stabellini
2012-02-13 11:37 ` Roger Pau Monné [this message]
2012-02-13 11:59 ` Stefano Stabellini
2012-02-13 14:41 ` Roger Pau Monné
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=CAPLaKK7dimHzig_s-_9gmpV5soWe9DhVfNtDFzquFpRg7V2ZhA@mail.gmail.com \
--to=roger.pau@entel.upc.edu \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).