-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Cloud / QCOW2: set basic image size to 16Gb for all cloud images #8046
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…/ should be larger for start This adds fixed +16Gb of resize, which doesn't make image any bigger, but when importing this as is, it might be better to not start without any free space. Now its 16Gb - cca. 600Mb.
WalkthroughThe changes introduce a new global variable Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
do I understand it right that the 16GB will be dynamically allocated. the qcow file will still be more or less the same size and only grow as the file-system inside the VM is actually filling up? |
yes, file size is unchanged. |
Description
Cloud QCOW2 images are as small as they can be, but file-system could should be larger for start
This adds fixed +16Gb of resize, which doesn't make image any bigger, but when importing this as is, it might be better to not start without any free space. Now its 16Gb - cca. 600Mb.
How Has This Been Tested?
Checklist: