From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Jay Mann <jmandawg@hotmail.com>, Uri Lublin <ulublin@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
kvm@vger.kernel.org
Subject: [Qemu-devel] Re: Problems KVM-84
Date: Wed, 11 Mar 2009 09:12:15 -0500 [thread overview]
Message-ID: <49B7C6BF.6030803@codemonkey.ws> (raw)
In-Reply-To: <49B79D50.4090300@redhat.com>
Avi Kivity wrote:
> Jay Mann wrote:
>> Hi,
>>
>> I just downloaded built and installed kvm-84 on ubuntu Hardy x64
>> 2.6.24-23-
>> server and I’m getting the following 2 problems that did not exists
>> in kvm-83.
>>
>> 1. The qemu emulater (bios screen) takes a long time to start (~10
>> seconds), and subsequently Libvirt times out when I try to start a
>> guest VM from virsh.
>
> This is caused by qemu r6404:
>
> commit 5d4cbd78aa33f6d034a62207c99ad0b64af44621
> Author: aliguori <aliguori@c046a42c-6fe2-441c-8c8c-71466251a162>
> Date: Thu Jan 22 18:57:22 2009 +0000
>
> block-qcow2: keep highest allocated byte (Uri Lublin)
> We want to know the highest written offset for qcow2 images.
> This gives a pretty good (and easy to calculate) estimation to how
> much more allocation can be done for the block device.
> It can be usefull for allocating more diskspace for that image
> (if possible, e.g. lvm) before we run out-of-disk-space
> Signed-off-by: Uri Lublin <uril@redhat.com>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>
> Scanning the file at startup is slow. We need to find a better way.
Any quick ideas? Seems like this is broken by design. Unless we can
find a quick fix, I'm going to revert this in the stable tree.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-03-11 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20090227T005557-327@post.gmane.org>
2009-03-11 11:15 ` [Qemu-devel] Re: Problems KVM-84 Avi Kivity
2009-03-11 14:12 ` Anthony Liguori [this message]
2009-03-11 14:52 ` Avi Kivity
2009-03-11 20:19 ` Anthony Liguori
2009-03-11 16:06 ` Jamie Lokier
2009-03-11 22:59 ` Uri Lublin
2009-03-11 18:37 ` Uri Lublin
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=49B7C6BF.6030803@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jmandawg@hotmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=ulublin@redhat.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).