qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Halsey Pian" <halsey.pian@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel]  qcow2 problem in CentOS
Date: Tue, 23 Dec 2014 18:32:26 +0800	[thread overview]
Message-ID: <003301d01e9b$c1e52b10$45af8130$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Hi All,

 

QCOW2 feature included in Qemu-2.1.2 version works fine in Fedora, but there is issue in CentOS 6.5/7.

 

We can create a qcow2 img file using qemu-img in CentOS

 

>  qemu-img create -f qcow2 test.qcow2 10G

 

Then using qemu-system-x86_64 or virt-manager to install one VM to this file test.qcow2 created above, the disk size is not 10G but
only basic about 200K. 

 

Are there similar issues in CentOS? Or maybe something I missed. Could you give help on it? Thanks!

 

 

 

Best Regards

Halsey Pian

 


[-- Attachment #2: Type: text/html, Size: 6060 bytes --]

             reply	other threads:[~2014-12-23 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 10:32 Halsey Pian [this message]
2014-12-23 10:59 ` [Qemu-devel] qcow2 problem in CentOS Paolo Bonzini

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='003301d01e9b$c1e52b10$45af8130$@gmail.com' \
    --to=halsey.pian@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).