From: Stefan Hajnoczi <stefanha@gmail.com>
To: arun.sasi1@wipro.com
Cc: libvirt-users@redhat.com, stefanha@linux.vnet.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qcow2
Date: Thu, 19 May 2011 20:05:13 +0100 [thread overview]
Message-ID: <BANLkTimyq630S_pQeJQMh7mawhH5yaDVGg@mail.gmail.com> (raw)
In-Reply-To: <2E7A71644A98EC4983B36C4946F763F13C6B3C@blr-mgr-msg.wipro.com>
On Thu, May 19, 2011 at 3:24 PM, <arun.sasi1@wipro.com> wrote:
> I couldn't find any error when I do consistency check on the image file...
Good, so there are no problems with your data.
> What can be the reason for not starting the VM.
Did you find any more error messages besides the sound related errors
in /var/log/libvirt/qemu/<domain>.log?
> Here I am suspecting when the base server go for reboot lesser image will start and it cached and larger image will take more time to create the cache...
>
> Was this correct... if yes could you please help me how to increase the caching...
No, there is no "cache creation". There is no startup delay for qcow2
image files.
Stefan
next prev parent reply other threads:[~2011-05-19 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2E7A71644A98EC4983B36C4946F763F133F099@blr-mgr-msg.wipro.com>
[not found] ` <20110518155803.GA23434@stefanha-thinkpad.localdomain>
2011-05-18 16:18 ` [Qemu-devel] Qcow2 arun.sasi1
2011-05-18 16:58 ` Stefan Hajnoczi
2011-05-18 18:03 ` arun.sasi1
2011-05-19 8:22 ` Stefan Hajnoczi
2011-05-19 14:24 ` arun.sasi1
2011-05-19 19:05 ` Stefan Hajnoczi [this message]
2011-05-30 8:53 ` arun.sasi1
2011-05-30 9:31 ` arun.sasi1
2011-06-07 17:10 ` arun.sasi1
2011-06-08 8:19 ` Stefan Hajnoczi
2011-06-08 9:02 ` arun.sasi1
2011-06-16 9:56 ` [Qemu-devel] Base server as file server arun.sasi1
2011-06-16 10:36 ` Stefan Hajnoczi
2011-06-16 10:46 ` arun.sasi1
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=BANLkTimyq630S_pQeJQMh7mawhH5yaDVGg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=arun.sasi1@wipro.com \
--cc=libvirt-users@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).