feat: add direct virtualization support - #49
Merged
Martin Heberling (Bickor) merged 3 commits intoSep 17, 2026
Merged
Conversation
Matthew Christopher (matthchr)
approved these changes
Sep 17, 2026
Matthew Christopher (matthchr)
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DirectVirtualizationvalue for theSupportedVirtualizationTypesSKU capabilitySKU.IsDirectVirtualizationSupported()in both the legacy and v2 packagesHasCapabilityWithSeparatorcapability handling for both nested and direct virtualizationNestedVirtualizationandDirectVirtualizationAPI values do not match each otherThe Compute API reports these virtualization types as mutually exclusive values, not as a combined collection.
Testing
go test -race ./...(root module)go vet ./...(root module)go test -race ./...(v2module)go vet ./...(v2module)golangci-lintcould not load the repository's legacy configuration with the locally installed golangci-lint v2.4.0.The repository
coverageworkflow currently fails during dependency setup before running tests: it pins Go 1.25 but installsgolang.org/x/tools@latest, which now requires Go 1.26.