From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Problems KVM-84 Date: Wed, 11 Mar 2009 09:12:15 -0500 Message-ID: <49B7C6BF.6030803@codemonkey.ws> References: <49B79D50.4090300@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jay Mann , kvm@vger.kernel.org, Uri Lublin , qemu-devel To: Avi Kivity Return-path: Received: from rv-out-0506.google.com ([209.85.198.231]:52571 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752344AbZCKOMV (ORCPT ); Wed, 11 Mar 2009 10:12:21 -0400 Received: by rv-out-0506.google.com with SMTP id g37so22584rvb.1 for ; Wed, 11 Mar 2009 07:12:19 -0700 (PDT) In-Reply-To: <49B79D50.4090300@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > Jay Mann wrote: >> Hi, >> >> I just downloaded built and installed kvm-84 on ubuntu Hardy x64 =20 >> 2.6.24-23- >> server and I=E2=80=99m getting the following 2 problems that did not= exists=20 >> in kvm-83. >> >> 1. The qemu emulater (bios screen) takes a long time to start (~1= 0=20 >> seconds), and subsequently Libvirt times out when I try to start a=20 >> guest VM from virsh. =20 > > This is caused by qemu r6404: > > commit 5d4cbd78aa33f6d034a62207c99ad0b64af44621 > Author: aliguori > 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 > Signed-off-by: Anthony Liguori > > 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=20 find a quick fix, I'm going to revert this in the stable tree. Regards, Anthony Liguori