diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2018-12-04 13:17:46 -0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-01-16 01:46:54 -0800 |
| commit | 92f73d73d04bdc973fe89e2c1682a1c3cc03fe49 (patch) | |
| tree | 8b9b52835951bb982ad3e5cc240b91f0dcacea3f /kernel_loader | |
| parent | 53429509833a8f1a227d977778069df93a4edd44 (diff) | |
| download | crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.tar crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.tar.gz crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.tar.bz2 crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.tar.lz crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.tar.xz crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.tar.zst crosvm-92f73d73d04bdc973fe89e2c1682a1c3cc03fe49.zip | |
devices: block: add resize VmControl request
This allows manual resizing of block devices at runtime via the command
line ('crosvm disk resize <index> <size>'). The virtio config interrupt
is asserted when the disk size changes so that the guest driver can
update the block device to the updated size.
Currently, there is no automatic policy for resizing disks - that will
be implemented in another change. Additionally, this resize operation
just changes the size of the block device; the filesystem will need to
be resized by the guest (e.g. via the 'btrfs filesystem resize' command)
as a separate step either before (shrinking) or after (expanding) the
disk resize operation.
BUG=chromium:858815
TEST=Start crosvm with a control socket (-s) and resize the disk with
'crosvm disk resize' from another shell.
Change-Id: I01633a7af04bfbaffbd27b9227274406d2a2b9cb
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1394152
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'kernel_loader')
0 files changed, 0 insertions, 0 deletions