-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add qcow2 support #225
Add qcow2 support #225
Conversation
Update readme.md
Allocation info
Disk space
…ync-3.x Update action-pack/gitlab-sync action to v3
…t-2.x Update action-pack/increment action to v2
Display IP errors
Hide ifconfig
Add MAC variable
MAC variable
Provide info about ipvlan
Hide netcat output
Multiline errors
workflow_dispatch
build: Debug
build: Debug
build: Debug
build: Debug
build: Add annotations
build: Bash
build: Docker Metadata
* fix: Default RAM size
* fix: DNS resolution
Thank you very much!! But two days ago I did a force push to the main branch, causing all existing forks to become invalid. I did not expect anyone was working on something, but I see your fork is from before that date. Is it possible that you create a fresh fork and copy the three files you modified to that one? Because I cannot merge this one without breaking the master. Thanks in advance! |
Also when switching the Would be really that when a data file is detected with the opposite extension to I will see if I have the time to add that function after the pullrequest gets merged. |
Moved to #226 |
This PR adds qcow2 disk image support while maintaining backwards compatibility.
qemu-img
does have support for raw image files, but I chose not to use that so theALLOCATE
flag would keep working. A lot of code could be removed by converting everything to useqemu-img
, though.