fix(vm): disable NetworkManager not systemd-networkd when both enabled#83
Merged
Conversation
Conflict resolution was backwards: we want systemd-networkd for VM networking. Also add --now so the service stops immediately. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P4Hxvsa529m9F6d6dxLCiG
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
1 participant
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
virtmachine.pywas disablingsystemd-networkdwhen both NM and systemd-networkd were found enabled — exactly backwards from what we want--nowso the service stops immediately, not just on next bootTest plan
/mnt/utmmounts correctly (was failing due to network target confusion)🤖 Generated with Claude Code
https://claude.ai/code/session_01P4Hxvsa529m9F6d6dxLCiG