Skip to content

Fix set_configuration_vm for multi-value configs (closes #192)#193

Open
martinmiglio wants to merge 1 commit into
masterfrom
fix/custom-resolution-multi-arg
Open

Fix set_configuration_vm for multi-value configs (closes #192)#193
martinmiglio wants to merge 1 commit into
masterfrom
fix/custom-resolution-multi-arg

Conversation

@martinmiglio
Copy link
Copy Markdown
Member

Summary

  • set_configuration_vm passed config_value as a single argv slot, so multi-token values like custom_resolution="270 480 120" reached memuc.exe quoted as one parameter and were rejected with ERROR: invalid config parameter.
  • Split config_value on whitespace and unpack into the memuc_run args, matching the CLI shape that works in a shell. Single-value configs are unaffected.

Fix proposed by @Broadsword in #192.

Test plan

  • On a Windows host with MEmu installed, run memuc.set_configuration_vm(vm_index=0, config_key="custom_resolution", config_value="270 480 120") and confirm SUCCESS: setconfig finished.
  • Verify a single-token config (e.g. cpus) still works.
  • Spot-check geometry which the reporter suspected has the same issue.

memuc_run uses subprocess with shell=False, so a space-separated value
like "270 480 120" was passed as a single argv slot and rejected with
'invalid config parameter'. Split on whitespace so configs that take
multiple tokens (e.g. custom_resolution, geometry) are forwarded as
separate args, matching the memuc CLI's expectations.

Closes #192
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.

Bug--custom_resolution

1 participant