-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi display support #590
Comments
Would adding a repeatable The way it'd work is when specifying Providing the |
That sounds reasonable.. it would need to be possible to configure multiple displays for CI jobs, though (Github Actions or Cirrus CI). |
Alternatively we can support a comma-separated list of resolutions for |
I like the format of the single Edit: (Not my PR, but I'm watching the project and multiple displays would be useful for us as well). |
Sounds good!
I think that should be fine. The displays can be rearranged using these APIs so the main display is not always the one on the left. |
I was a bit reluctant to preserve the multiple display configuration in the VM's configuration file (which gets pushed to the OCI registry), so I've decided to see how Tart and You get the following error when configuring a VM with
And the following error when configuring a VM with two
UTM documentation says that:
Regarding Anka:
Anka fails to start the VM after running Running |
I'd like to use tart for integration testing of software that enumerates and keeps track of system displays. Multi display is a key use case for testing.
I think Virtualization.Framework supports this, so it's a matter of exposing it from the CLI. Anka has support for configuring up to 2 displays, both with the same resolution, which is probably good enough.
The text was updated successfully, but these errors were encountered: