how do we install virtio drivers if its missing? How do I verify it on the centos cloud image if its there?
On Tue, Aug 1, 2017 at 12:19 PM, Abel Lopez <[email protected]> wrote: > Your custom image is likely missing the virtIO drivers that the cloud > image has. > > Instead of running through the DVD installer, I'd suggest checking out > diskimage-builder to make custom images for use on Openstack. > > On Tue, Aug 1, 2017 at 10:16 AM Paras pradhan <[email protected]> > wrote: > >> Also this is what I've noticed with the centos cloud image I downloaded. >> If I add few packages( around a GB), the sizes goes up to 8GB from 1.3 GB. >> Running dd if=/dev/zero of=temp;sync;rm temp failed due to the size of >> the disk on the cloud images which is 10G. zeroing failed with No space >> left on device. Any other options? >> >> Thanks >> Paras. >> >> On Tue, Aug 1, 2017 at 9:43 AM, Paras pradhan <[email protected]> >> wrote: >> >>> I ran virt-sparsify. So before running virt-sparsify it was 6.0GB and >>> after it is 1.3GB. >>> >>> Thanks >>> Paras. >>> >>> On Tue, Aug 1, 2017 at 2:53 AM, Tomáš Vondra <[email protected]> >>> wrote: >>> >>>> Hi! >>>> >>>> How big are the actual image files? Because qcow2 is a sparse format, >>>> it does not store zeroes. If the free space in one image is zeroed out, it >>>> will convert much faster. If that is the problem, use „dd if=/dev/zero >>>> of=temp;sync;rm temp“ or zerofree. >>>> >>>> Tomas >>>> >>>> >>>> >>>> *From:* Paras pradhan [mailto:[email protected]] >>>> *Sent:* Monday, July 31, 2017 11:54 PM >>>> *To:* [email protected] >>>> *Subject:* [Openstack-operators] custom build image is slow >>>> >>>> >>>> >>>> Hello >>>> >>>> >>>> >>>> I have two qcow2 images uploaded to glance. One is CentOS 7 cloud image >>>> downloaded from centos.org. The other one is custom built using >>>> CentOS 7.DVD. When I create cinder volumes from them, volume creation from >>>> the custom built image it is very very slow. >>>> >>>> >>>> >>>> >>>> >>>> CenOS qcow2: >>>> >>>> >>>> >>>> 2017-07-31 21:42:44.287 881609 INFO cinder.image.image_utils >>>> [req-ea2d7b12-ae9e-45b2-8b4b-ea8465497d5a >>>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf >>>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d >>>> default] *Converted 8192.00 MB image at 253.19 MB/s* >>>> >>>> >>>> >>>> Custom built qcow2: >>>> >>>> INFO cinder.image.image_utils [req-032292d8-1500-474d-95c7-2e8424e2b864 >>>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf >>>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d >>>> default] *Converted 10240.00 MB image at 32.22 MB/s* >>>> >>>> >>>> >>>> I used the following command to create the qcow2 file >>>> >>>> qemu-img create -f qcow2 custom.qcow2 10G >>>> >>>> >>>> >>>> What am I missing ? >>>> >>>> >>>> >>>> Thanks >>>> Paras. >>>> >>>> >>>> >>>> >>>> >>> >>> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
