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

Enhancement: Allow ability to modify DOM0 memory allocation #2218

Closed
agador opened this issue Jun 14, 2017 · 6 comments · Fixed by #5437
Closed

Enhancement: Allow ability to modify DOM0 memory allocation #2218

agador opened this issue Jun 14, 2017 · 6 comments · Fixed by #5437

Comments

@agador
Copy link

agador commented Jun 14, 2017

Context

xo-web 5.9.1

Expected behavior

Add ability to modify the DOM0 memory allocations and suggest REBOOT (since it is required to have the changed value take effect).

Current behavior

Not currently available in XO nor in XenCenter, except for XS-7.1

The function can be performed via the CLI on any version of XS. The ability to use XC to modify the values is only available on XS-7.1

@olivierlambert
Copy link
Member

I suppose the XenAPI only expose this since 7.1

There is probably no other way than using CLI for previous versions.

@agador
Copy link
Author

agador commented Jun 14, 2017

That was my impression as well. I wasn't sure if you wanted to do some "XOA" magic or not. If you want to make it a 7.1+ feature so you my use the API, I'm good with that.

@olivierlambert
Copy link
Member

I think there is no reasonable magic to do it, so we'll probably display the option if it's a 7.1 or more recent 👍

@brezlord
Copy link

Hi, when will this feature be available in XO?

@olivierlambert
Copy link
Member

Hi,

Likely when we have more bandwidth and/or when a paid custom will raise the priority :) So I can't really tell now.

@julien-f
Copy link
Member

julien-f commented Dec 1, 2020

The implementation should be straightforward: simply exposing the ability to set the VM of the host's control domain.

If it does not work, we should use xapi-inspector between XCP-ng Center and the XAPI.

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