core: ensure that the user defined VMType
flag is respected for m3 devices
#1045
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.
Hello! I'm creating this to ensure that the
--vm-type
flag is being respected. I understand that at one point qemu had issues on M3 chips, however in my current company we're experiencing issues usingvz
. As such, we've had to revert back toqemu
, and it's worked a treat.To get it going currently we need to run
coilima start --edit
, which is fine for testing, but being able to run start with qemu defined as the vm type and have that setting respected would be a game changer. Happy to work on this and improve if needed, but I think this should do the trick.