Comment 6 for bug 1235358
Revision history for this message
| Xavier Queralt (xqueralt-deactivatedaccount) wrote Re: selected cylinder exceeds maximum supported by bios | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The problem appears to be in cinder when using the gluster or nfs drivers.
If the source image is bigger (considering the virtual size) than the target volume, those drivers will still copy the image into the volume and resize it to fit the requested size. The problem is with the resulting image after the resize, which won't look as a proper disk to the hypervisor.
Those are the commands called by the gluster (and nfs) driver when creating a volume from an image:
1. truncate -s <volume size>G <volume path>
2. download the image to <image path>
3. qemu-img convert -O raw <source image path> <volume path>
- After this we will have a volume as big as the original image
4. qemu-img resize <volume path> <volume size>G
- After this, if the image was bigger than the volume we might end up with a truncated and unusable image.