Skip to content

Use machine_type under vsrx device attribute instead of libvirt template#3411

Merged
ipspace merged 2 commits into
ipspace:devfrom
sdargoeuves:vsrx_use_machine_type
May 19, 2026
Merged

Use machine_type under vsrx device attribute instead of libvirt template#3411
ipspace merged 2 commits into
ipspace:devfrom
sdargoeuves:vsrx_use_machine_type

Conversation

@sdargoeuves
Copy link
Copy Markdown
Collaborator

#3406 (review)

I didn't understand why it wouldn't work, until I've realised I needed to have it under node inside libvirt

@sdargoeuves sdargoeuves force-pushed the vsrx_use_machine_type branch from 497ca1e to 61f8c63 Compare May 18, 2026 23:21
@sdargoeuves
Copy link
Copy Markdown
Collaborator Author

Hopefully this doesn't fall into the new classic: "AI changed the tests to fit the (bad) code it created", because I didn't use AI to edit those tests!

More seriously, I am not sure what's the right approach when it comes to testing. There were 4 topology containing vsrx, I've updated 4 output files and 1 input files (to test when the value is set to false).

Copy link
Copy Markdown
Owner

@ipspace ipspace left a comment

Choose a reason for hiding this comment

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

Looks great to me. Thank you! Now I have to change the box-building process to use device machine_type if defined.

@ipspace ipspace merged commit 8bea427 into ipspace:dev May 19, 2026
5 checks passed
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.

2 participants