Bug 1404182
| Summary: | RFE: virt-resize should support a URL as the outdisk | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Xianghua Chen <xchen> |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | low | Docs Contact: | Yehuda Zimmerman <yzimmerm> |
| Priority: | low | ||
| Version: | 7.4 | CC: | pasik, ptoscano, rjones, wshi, yoguo |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libguestfs-1.36.1-1.el7 | Doc Type: | Enhancement |
| Doc Text: |
Resized disks can be written directly to a remote location
With this update, the *virt-resize* utility can write its output to a remote location. This may be useful, for example, in directly writing the resized disk image to a Ceph storage volume. The *virt-resize* output disk can be specified using a URI. Any supported input protocol and format can be used to specify the output.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 22:11:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1359086 | ||
| Bug Blocks: | |||
|
Description
Xianghua Chen
2016-12-13 09:32:30 UTC
Also, the virt-builder should support URL too. (In reply to Xianghua Chen from comment #1) > Also, the virt-builder should support URL too. Needs a separate RFE for that one. (In reply to Richard W.M. Jones from comment #2) > (In reply to Xianghua Chen from comment #1) > > Also, the virt-builder should support URL too. > > Needs a separate RFE for that one. Ok, thanks. New bug for this: #1405273 Patch (apparently easier than expected) posted for this: https://www.redhat.com/archives/libguestfs/2017-January/msg00038.html Fixed upstream with https://github.com/libguestfs/libguestfs/commit/8a2b0738d1b79f288b14fc35294567430d10b7ec which is in libguestfs >= 1.35.21. Verified with package: libguestfs-1.36.3-3.el7.x86_64 Steps: 1. Prepare a ceph server (10.66.144.75 as the ceph mon) Create a pool: libvirt-pool Prepare a guest image:rbd-secret.img 2. On remote machine: # qemu-img create -f raw rbd:libvirt-pool/out-disk.raw:mon_host=10.66.144.75 10G 3. $ rbd -p libvirt-pool ls out-disk.raw rbd-secret.img 4. On remote machine: # virt-resize --format=raw --resize /dev/sda1=+200M --expand /dev/sda2 rbd://10.66.144.75:6789/libvirt-pool/rbd-secret.img --output-format=raw rbd://10.66.144.75:6789/libvirt-pool/out-disk.raw Actual results: ------------------------------------------------------------------------- [ 0.0] Examining rbd://10.66.144.75:6789/libvirt-pool/rbd-secret.img ********** Summary of changes: /dev/sda1: This partition will be resized from 1.0G to 1.2G. The filesystem xfs on /dev/sda1 will be expanded using the 'xfs_growfs' method. /dev/sda2: This partition will be resized from 7.0G to 8.8G. The LVM PV on /dev/sda2 will be expanded using the 'pvresize' method. ********** [ 2.4] Setting up initial partition table on rbd://10.66.144.75:6789/libvirt-pool/out-disk.raw [ 2.9] Copying /dev/sda1 100% ⟦▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒⟧ 00:00 [ 10.1] Copying /dev/sda2 100% ⟦▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒⟧ 00:00 [ 71.4] Expanding /dev/sda1 using the 'xfs_growfs' method [ 72.5] Expanding /dev/sda2 using the 'pvresize' method Resize operation completed with no errors. Before deleting the old disk, carefully check that the resized disk boots and works correctly. ------------------------------------------------------------------------------ In step 4, the command can be executed successfully. So verified this bug. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2023 |