Skip to content
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

Add Toggle For Platform Viridian Status #6572

Closed
RFWave opened this issue Dec 6, 2022 · 4 comments · Fixed by #6631
Closed

Add Toggle For Platform Viridian Status #6572

RFWave opened this issue Dec 6, 2022 · 4 comments · Fixed by #6631

Comments

@RFWave
Copy link

RFWave commented Dec 6, 2022

Is your feature request related to a problem? Please describe.
In XCP-NG and XenServer there is an underlying Hyper-V emulation layer called Viridian that is enabled by default on most VM templates. There are issues on some BSD guests such as OpenBSD where it causes some communication issues with the domU guest driver when this is enabled. I normally have to run the command below in the CLI of the hypervisor to get it fixed.

xe vm-param-set uuid= platform:viridian=false

If there was a toggle for this option in Xen-Orchestra under the advanced VM options page it would make things way easier to manage for the guest VMs.

Describe the solution you'd like
Add a toggle that changes the VM platform parameter between viridian=false and viridian=true in the advanced VM options page.

Describe alternatives you've considered
I have been looking at making some templates that just include the options that I need but that does not help for managing existing VMs.

@olivierlambert
Copy link
Member

Hi,

Thanks for the report. Maybe a BSD template without this set to true could be also a solution?

@RFWave
Copy link
Author

RFWave commented Dec 6, 2022

I definitely would like to get a proper BSD template set as well but I do know that the Viridian layer has caused some issues for other Guest VMs such as windows Server 2008. The places where I have seen this crop up as an issue is mostly in niche areas for lesser used OSs.

The details on how to solve it and what command you need to run are really hard to find because of the niche nature of where you encounter issues with the layer. Having an option that you could toggle as a part of VM management would simplify troubleshooting and help avoid the google rabbit hole when trying to find the few bits of documentation on Viridian.

@julien-f
Copy link
Member

julien-f commented Dec 9, 2022

@olivierlambert What should we about this?

@olivierlambert
Copy link
Member

I suppose adding a toggle in advanced might help. Not for this release but for the next one seems doable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants