Skip to content
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

Create a bigger initial disk on Parallels Desktop 13.0 #68

Merged
merged 4 commits into from
Sep 13, 2017

Conversation

legal90
Copy link
Collaborator

@legal90 legal90 commented Sep 11, 2017

Fixes #67

That is a workaround for "plain" -> "expanding" disk conversion on Parallels Desktop 13.0.* .
To get it working as before, we need to create a bigger disk image. The minimal size is 1891Mb.
It makes sense only in the creation phase - after that, the disk will be resized to d.DiskSize.

That is a workaround for "plain" -> "expanding" disk conversion on Parallels Desktop 13.0.* .
To get it working as before, we need to create a bigger disk image. The minimal size is 1891Mb.
It makes sense only in the creation phase - after that, the disk will be always resized to d.DiskSize
@romankulikov
Copy link
Collaborator

@legal90, do you really think that it is worth implementing such a check? May be just to declare that a specific interval of Parallels Desktop versions is broken? I'm in doubts frankly.

@legal90
Copy link
Collaborator Author

legal90 commented Sep 13, 2017

@romankulikov Yes, I just want to release this workaround now, so users will be able to continue using the plugin today, before the "fixed" fersion of Parallels Desktop is released.

Bringing the go-version library might look like an overkill, but I think it's not the last time when we need such version constraints for PD features or workarounds.

@romankulikov
Copy link
Collaborator

Ok.

@romankulikov romankulikov reopened this Sep 13, 2017
@romankulikov romankulikov merged commit 00cfec0 into Parallels:master Sep 13, 2017
@legal90 legal90 deleted the fix-pd13 branch September 13, 2017 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants