Bug 2033595 - [machines] compatibility in s390x about VM graphics console, boot order and SCLP console
Summary: [machines] compatibility in s390x about VM graphics console, boot order and S...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: cockpit-machines
Version: 9.0
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: rc
: 9.0
Assignee: Simon Kobyda
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-17 11:36 UTC by YunmingYang
Modified: 2023-06-28 07:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-17 07:29:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-106086 0 None None None 2021-12-17 11:37:40 UTC

Description YunmingYang 2021-12-17 11:36:13 UTC
Description of problem:
c-machines will add graphics by default when creating a VM, but it will cause VM shutoff immediately when creating VM with PXE. According by https://bugzilla.redhat.com/show_bug.cgi?id=2032472, s390x seems to not support graphics and boot order, and use "SCLP" console instead of "viritio" console, so compatibility in s390x about these features may be needed


Version-Release number of selected components (if applicable):
cockpit-258-1.el9.s390x
cockpit-machines-256-1.el9.noarch
libvirt-dbus-1.4.1-5.el9.s390x

How reproducible:
100%


Steps to Reproduce:



Actual results:



Expected results:
1 compatibility in s390x about VM graphics console, boot order and SCLP console


Additional info:

Comment 1 Martin Pitt 2022-01-04 15:30:14 UTC
Simon is looking into this.

Comment 3 RHEL Program Management 2023-06-17 07:29:16 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.