Bug 1919805 - [DOCS] Enable bochs-display for UEFI guests
Summary: [DOCS] Enable bochs-display for UEFI guests
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.5
: ---
Assignee: Richard Hoch
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On: 1707118 1707119 1724098 1753645 1754394 1754396
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-25 08:14 UTC by Arik
Modified: 2021-05-05 08:01 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: Technology Preview
Doc Text:
With this update, support for the Bochs display video card emulator has been added for UEFI guest machines. This feature is now the default for a guest UEFI server that uses compatibility level 4.6 or above, where BOCHS is the default value of Video Type.
Clone Of: 1753645
Environment:
Last Closed: 2021-05-05 08:01:39 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:
emarcus: needinfo-
emarcus: needinfo-

Attachments (Terms of Use)

Comment 3 Arik 2021-04-04 20:14:00 UTC 
BTW, the feature page: https://www.ovirt.org/develop/release-management/features/virt/bochs-display.html
Comment 7 Richard Hoch 2021-04-06 09:42:02 UTC 
QA: Please provide technical review of https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/-/merge_requests/1940
Comment 22 Richard Hoch 2021-05-02 07:44:22 UTC 
Arik,

Eli Marcus raised a good point:

Should we change "cluster version" to "compatibility version" in the last line of the following? 

In {virt-product-fullname} 4.4.5, you must do the following to enable this feature:

. Run the following command:
+
----
 engine-config --set EnableBochsDisplay=true --cver=<version>
----
where `<version>` is the cluster version.
Comment 23 Arik 2021-05-02 14:57:02 UTC 
Yes, that would be more accurate since the compatibility version doesn't have to be that of the cluster.
Specifically this would happen in the following case: the VM resides in a 4.4 (or 4.2 or 4.3) cluster and set with custom compatibility version 4.5 - so it's compatibility version is 4.5
Note You need to log in before you can comment on or make changes to this bug.