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

VM Creation is failing for s390x based installation #2314

Open
sanjayy-ibm opened this issue Dec 13, 2024 · 3 comments
Open

VM Creation is failing for s390x based installation #2314

sanjayy-ibm opened this issue Dec 13, 2024 · 3 comments

Comments

@sanjayy-ibm
Copy link

When we goto 'Virtual Images' and select create > from YAML (See image attached), whatever the default YAML that gets generated is having a machine type as q35, but it complaining with error only allowed value is s390-ccw-virtio (See image attached).
Uploading screenshots_ConsoleUI.zip…

@sanjayy-ibm
Copy link
Author

@upalatucci

@chandramerla
Copy link

@upalatucci : The code which generates the default yaml seems to be here - https://github.com/kubevirt-ui/kubevirt-plugin/blob/c9cb011db42f0ae0f5ff3622b8a1e04d73dc03ee/src/templates/vm-yaml.ts

For s390x based cluster (control-plane running on s390x), can we identify that somehow and use a file with machine type defined as s390-ccw-virtio?

@sanjayy-ibm I'm unable to view the screenshots. So, putting them here again.

Option to create from yaml
option to create from yaml

Error on s390x when creating from yaml
error on s390x when creating from yaml

@upalatucci
Copy link
Member

Hei guys. I'm sorry, but the current console does not allow editing the YAML from the dynamic plugin on the fly. I'm sorry but we can't do that. Moreover, typically only admins have access to nodes and their arch so will not work for all users. But maybe we can think of adding a config in the console for those cases? We should talk about that with Sam

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

No branches or pull requests

3 participants