[
https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325104#comment-14325104
]
Marcus Sorensen edited comment on CLOUDSTACK-6181 at 2/17/15 11:32 PM:
-----------------------------------------------------------------------
You need both, don't you? that's what resizevolume.sh did. CloudStack actually
resizes qcow2 via libvirt directly as of 4.5, but still requires the virsh
blockresize to notify the guest about the disk size change (not require a power
cycle), because the libvirt java bindings don't support blockresize. This is
actually somewhat confusing, as libvirt java can resize *volumes*, but not
inform domains about blockdevice size changes.
By the way, the corrupted qcow2 issue is something I've only seen when trying
to resize an empty qcow2. Create a volume, attach it, resize it without
partitioning or formatting, and it corrupts. This happens via libvirt resize or
qemu-img resize. I've been looking for the upstream fixes, but it has been
tough to track down and probably won't be feasible to tell people to patch
their qemu.
was (Author: mlsorensen):
You need both, don't you? that's what resizevolume.sh does.
> Root resize
> -----------
>
> Key: CLOUDSTACK-6181
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Storage Controller, UI
> Affects Versions: 4.4.0
> Environment: KVM/libvirt/CentOS, Xenserver
> Reporter: Nux
> Labels: disk, resize, template
> Fix For: 4.4.0
>
>
> Rationale:
> Currently the root size of an instance is locked to that of the template.
> This creates unnecessary template duplicates, prevents the creation of a
> market place, wastes time and disk space and generally makes work more
> complicated.
> Real life example - a small VPS provider might want to offer the following
> sizes (in GB):
> 10,20,40,80,160,240,320,480,620
> That's 9 offerings.
> The template selection could look like this, including real disk space used:
> Windows 2008 ~10GB
> Windows 2008+Plesk ~15GB
> Windows 2008+MSSQL ~15GB
> Windows 2012 ~10GB
> Windows 2012+Plesk ~15GB
> Windows 2012+MSSQL ~15GB
> CentOS ~1GB
> CentOS+CPanel ~3GB
> CentOS+Virtualmin ~3GB
> CentOS+Zimbra ~3GB
> CentOS+Docker ~2GB
> Debian ~1GB
> Ubuntu LTS ~1GB
> In this case the total disk space used by templates will be 828 GB, that's
> almost 1 TB. If your storage is expensive and limited SSD this can get
> painful!
> If the root resize feature is enabled we can reduce this to under 100 GB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
