[
https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048610#comment-14048610
]
Wei Zhou commented on CLOUDSTACK-6191:
--------------------------------------
Guys,
which version of QEMU do you use for testing?
we tested on QEMU 1.2.0 just now, it failed with the following error:
2014-07-01 07:49:16,715 INFO [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-2:null) Attempting to create storage pool
b97fb62e-ece9-3cc9-aa40-c30b74072d9b (NetworkFilesystem) in libvirt
2014-07-01 07:49:16,790 INFO [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-2:null) Attempting to create storage pool
ea41809e-5121-387c-94a7-ee1674e57b14 (NetworkFilesystem) in libvirt
2014-07-01 07:49:16,811 INFO [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-2:null) Attempting to create volume
49a46349-005f-11e4-9be4-005056ac252f (NetworkFilesystem) in pool
ea41809e-5121-387c-94a7-ee1674e57b14 with size 2621440000
2014-07-01 07:49:16,849 ERROR [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-2:null) Failed to create
/mnt/ea41809e-5121-387c-94a7-ee1674e57b14/49a46349-005f-11e4-9be4-005056ac252f
due to a failed executing of qemu-img: info: invalid option -- '-'qemu-img
version 1.2.0, Copyright (coffee) 2004-2008 Fabrice Bellardusage: qemu-img
command [command options]QEMU disk image utilityCommand syntax: check [-f fmt]
[-r [leaks | all]] filename create [-f fmt] [-o options] filename [size]
commit [-f fmt] [-t cache] filename convert [-c] [-p] [-f fmt] [-t cache] [-O
output_fmt] [-o options] [-s snapshot_name] [-S sparse_size] filename
[filename2 [...]] output_filename info [-f fmt] filename snapshot [-l | -a
snapshot | -c snapshot | -d snapshot] filename rebase [-f fmt] [-t cache] [-p]
[-u] -b backing_file [-F backing_fmt] filename resize filename [+ |
-]sizeCommand parameters: 'filename' is a disk image filename 'fmt' is the
disk image format. It is guessed automatically in most cases 'cache' is the
cache mode used to write the output disk image, the valid options are:
'none', 'writeback' (default, except for convert), 'writethrough',
'directsync' and 'unsafe' (default for convert) 'size' is the disk image size
in bytes. Optional suffixes 'k' or 'K' (kilobyte, 1024), 'M' (megabyte,
1024k), 'G' (gigabyte, 1024M) and T (terabyte, 1024G) are supported. 'b' is
ignored. 'output_filename' is the destination disk image filename
'output_fmt' is the destination format 'options' is a comma separated list of
format specific options in a name=value format. Use -o ? for an overview of
the options supported by the used format '-c' indicates that target image
must be compressed (qcow format only) '-u' enables unsafe rebasing. It is
assumed that old and new backing file match exactly. The image doesn't
need a working backing file before rebasing in this case (useful for
renaming the backing file) '-h' with or without a command shows this help and
lists the supported formats '-p' show progress of command (only certain
commands) '-S' indicates the consecutive number of bytes that must contain
only zeros for qemu-img to create a sparse image during
conversionParameters to check subcommand: '-r' tries to repair any
inconsistencies that are found during the check. '-r leaks' repairs only
cluster leaks, whereas '-r all' fixes all kinds of errors, with a higher
risk of choosing the wrong fix or hiding corruption that has already
occured.Parameters to snapshot subcommand: 'snapshot' is the name of the
snapshot to create, apply or delete '-a' applies a snapshot (revert disk to
saved state) '-c' creates a snapshot '-d' deletes a snapshot '-l' lists all
snapshots in the given imageSupported formats: vvfat vpc vmdk vdi sheepdog rbd
raw host_cdrom host_floppy host_device file qed qcow2 qcow parallels nbd dmg
tftp ftps ftp https http cow cloop bochs blkverify blkdebug
2014-07-01 07:49:16,855 ERROR [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-2:null) Failed to fetch the information of file
/mnt/b97fb62e-ece9-3cc9-aa40-c30b74072d9b/dd3be21c-f780-4088-b991-03fcdc0d494d.qcow2
the error was: info: invalid option -- '-'qemu-img version 1.2.0, Copyright
(coffee) 2004-2008 Fabrice Bellardusage: qemu-img command [command options]QEMU
disk image utilityCommand syntax: check [-f fmt] [-r [leaks | all]] filename
create [-f fmt] [-o options] filename [size] commit [-f fmt] [-t cache]
filename convert [-c] [-p] [-f fmt] [-t cache] [-O output_fmt] [-o options]
[-s snapshot_name] [-S sparse_size] filename [filename2 [...]] output_filename
info [-f fmt] filename snapshot [-l | -a snapshot | -c snapshot | -d snapshot]
filename rebase [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F backing_fmt]
filename resize filename [+ | -]sizeCommand parameters: 'filename' is a disk
image filename 'fmt' is the disk image format. It is guessed automatically in
most cases 'cache' is the cache mode used to write the output disk image, the
valid options are: 'none', 'writeback' (default, except for convert),
'writethrough', 'directsync' and 'unsafe' (default for convert) 'size' is
the disk image size in bytes. Optional suffixes 'k' or 'K' (kilobyte, 1024),
'M' (megabyte, 1024k), 'G' (gigabyte, 1024M) and T (terabyte, 1024G) are
supported. 'b' is ignored. 'output_filename' is the destination disk image
filename 'output_fmt' is the destination format 'options' is a comma
separated list of format specific options in a name=value format. Use -o ?
for an overview of the options supported by the used format '-c' indicates
that target image must be compressed (qcow format only) '-u' enables unsafe
rebasing. It is assumed that old and new backing file match exactly. The
image doesn't need a working backing file before rebasing in this case
(useful for renaming the backing file) '-h' with or without a command shows
this help and lists the supported formats '-p' show progress of command (only
certain commands) '-S' indicates the consecutive number of bytes that must
contain only zeros for qemu-img to create a sparse image during
conversionParameters to check subcommand: '-r' tries to repair any
inconsistencies that are found during the check. '-r leaks' repairs only
cluster leaks, whereas '-r all' fixes all kinds of errors, with a higher
risk of choosing the wrong fix or hiding corruption that has already
occured.Parameters to snapshot subcommand: 'snapshot' is the name of the
snapshot to create, apply or delete '-a' applies a snapshot (revert disk to
saved state) '-c' creates a snapshot '-d' deletes a snapshot '-l' lists all
snapshots in the given imageSupported formats: vvfat vpc vmdk vdi sheepdog rbd
raw host_cdrom host_floppy host_device file qed qcow2 qcow parallels nbd dmg
tftp ftps ftp https http cow cloop bochs blkverify blkdebug
> Volume provisioning type option
> -------------------------------
>
> Key: CLOUDSTACK-6191
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Management Server
> Reporter: Yoshikazu Nojima
> Assignee: Yoshikazu Nojima
> Priority: Minor
> Fix For: 4.5.0
>
>
> Thin provisioning of a volume saves consumption of a storage, and fat
> provisioning minimizes IOPS performance overhead.
> This feature implements a global setting to provide users an option to select
> how to provision volumes.
> Design doc:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option
--
This message was sent by Atlassian JIRA
(v6.2#6252)
