public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: J- MAN <jmandawg@hotmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Problems KVM-84
Date: Tue, 10 Mar 2009 15:47:05 +0200	[thread overview]
Message-ID: <49B66F59.5000603@redhat.com> (raw)
In-Reply-To: <BAY102-W2139785413083807492C85D2A10@phx.gbl>

J- MAN wrote:
>
> > I don't think this is a regression from kvm-83. Large qcow2 files have 
> > lots of metadata which needs to be loaded up front. If the kernel 
> > doesn't have this cached, it will take a long time.
>
> I'm just wondering what happend between 83 and 84, because there is no 
> startup delay in 83.
> My real problem is that libvirt times out when waiting for my virtual 
> machine to start using 84, unless i manually start the machine first 
> to get it cached.
>
> This makes using libvirt & virt-manager useless with 84 unless i 
> pre-start all my VMs manually to get them cached.
>
> I'm suprised nobody else is having this issue.  If there is anything 
> else i can do to help please let me know.


Try (with kvm-83):

  echo 255 > /proc/sys/vm/drop-caches
  qemu ...

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2009-03-10 13:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  0:58 Problems KVM-84 Jay Mann
2009-02-27  6:52 ` Thomas Mueller
2009-03-09 10:22 ` Avi Kivity
     [not found]   ` <01a301c9a0b1$4af7f730$e0e7e590$@com>
2009-03-09 12:19     ` jmandawg
2009-03-09 12:37       ` Avi Kivity
     [not found]         ` <BAY102-W25DF72B635B00AD337130D2A00@phx.gbl>
2009-03-10  8:39           ` Avi Kivity
     [not found]             ` <BAY102-W2139785413083807492C85D2A10@phx.gbl>
2009-03-10 13:47               ` Avi Kivity [this message]
2009-03-11 11:15 ` Avi Kivity
2009-03-11 14:12   ` Anthony Liguori
2009-03-11 14:52     ` [Qemu-devel] " 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=49B66F59.5000603@redhat.com \
    --to=avi@redhat.com \
    --cc=jmandawg@hotmail.com \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox