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

Remove UVM/container cloning functionality #1740

Merged
merged 1 commit into from
May 3, 2023

Conversation

kevpar
Copy link
Member

@kevpar kevpar commented Apr 23, 2023

This is commit 1/6 in a chain. Recommended to review in order. If reviewing a later PR in the chain, you can view individual commits to see just what that PR changes.

This change completely removes the support for cloning/late cloning that was added a few years ago. The reasoning behind this is as follows:

  • There are no plans to utilize cloning at this point in time.
  • The cloning support required extensive/invasive changes across many parts of the shim. This has made future changes and refactorings more difficult in some cases. While these changes are still possible, it seems like an unnecessary burden if we are not going to use cloning.
  • The cloning functionality was never actually utilized, and thus may still have had fixes needed to be production-ready.

If cloning is needed again in the future, we will be able to revert this commit to add it back.

@kevpar
Copy link
Member Author

kevpar commented Apr 24, 2023

@ambarve could you PTAL?

This change completely removes the support for cloning/late cloning that
was added a few years ago. The reasoning behind this is as follows:
- There are no plans to utilize cloning at this point in time.
- The cloning support required extensive/invasive changes across many
  parts of the shim. This has made future changes and refactorings more
  difficult in some cases. While these changes are still possible, it
  seems like an unnecessary burden if we are not going to use cloning.
- The cloning functionality was never actually utilized, and thus may
  still have had fixes needed to be production-ready.

If cloning is needed again in the future, we will be able to revert this
commit to add it back.

Signed-off-by: Kevin Parsons <kevpar@microsoft.com>
Copy link
Contributor

@ambarve ambarve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@kevpar
Copy link
Member Author

kevpar commented May 3, 2023

CI failures are not related.

@kevpar kevpar merged commit fe4a458 into microsoft:main May 3, 2023
anmaxvl pushed a commit that referenced this pull request Oct 20, 2023
This PR updates our ADO fork to commits in hcsshim up to commit hash [7769a64](7769a64). This includes support for partitioned scsi devices and ensuring filesystem format for lcow scsi devices.

Related work items: #1728, #1740, #1741, #1742, #1743, #1744, #1745, #1747, #1748, #1749, #1750, #1752, #1754, #1756, #1757, #1767, #1769, #1771, #1772, #1773, #1779
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

5 participants