First VM provisioning is slow for large VM images
Bug #1005956 reported by
Salman Baset
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
To provision a VM, OpenStack:
(1) copies the image over the network to the compute node in _base directory
(2) If its a qcow2 image, it is converted to raw
(3) Creates a copy of the raw using cp operation.
(4) Creates qcow2 disks from the image in (3).
(2) can eliminated using force_to_raw=False in nova.conf
However, copying is a costly operation, if the image size is large. Image size can be large due to VM snapshotting, or for Windows images. Need to eliminate it. Can we simply create qcow2 disks from the image copied over the network? Something like:
qemu-img create -o qcow2 new.img 10G -b image_from_network
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
To post a comment you must log in.
The copy of the raw is to allow different size disks. If qemu-img supports resizing when it creates an image backed to another file, then yes we could optimize it to work as you say. Does it support such a thing? We would also have to update the imagecache code to handle not having the <uuid>_<size> versions of the file.