Bug 1847959 - novnc working in grayscale and low resolution after upgrade to OSP15/OSP16
Summary: novnc working in grayscale and low resolution after upgrade to OSP15/OSP16
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: seabios
Version: ---
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: 8.3
Assignee: Gerd Hoffmann
QA Contact: Guo, Zhiyi
URL:
Whiteboard:
: 1873566 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-17 12:47 UTC by Mauro Oddi
Modified: 2023-12-15 18:12 UTC (History)
20 users (show)

Fixed In Version: seabios-1.13.0-2.module+el8.2.1+7284+aa32a2c4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1852926 (view as bug list)
Environment:
Last Closed: 2020-07-28 07:13:49 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
bios fix (1.04 KB, patch)
2020-06-25 08:54 UTC, Gerd Hoffmann
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1884990 0 None None None 2020-06-24 15:55:30 UTC
Red Hat Knowledge Base (Solution) 5356921 0 None None None 2020-10-01 11:11:19 UTC
Red Hat Product Errata RHBA-2020:3172 0 None None None 2020-07-28 07:14:41 UTC

Description Mauro Oddi 2020-06-17 12:47:19 UTC
Description of problem:
After upgrading to OpenStack 15 the VNC console of an instance is displayed in grayscale and low resolution (640x480). 

Furthermore setting hw_video_model=qxl in the image property would resolve the issue (by changing the default display setting)


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Create an instance with default hw_video_model (cirrus)
2. Access vnc console
3.

Actual results:
grayscale 640x480 display

Expected results:
high res color display

Additional info:

Comment 13 Daniel Berrangé 2020-06-24 15:55:31 UTC
This same issue looks like it is reported upstream: https://bugs.launchpad.net/qemu/+bug/1884990

That claims that downgrading the vgabios fixes it.

Comment 15 Gerd Hoffmann 2020-06-25 07:33:32 UTC
(In reply to Daniel Berrangé from comment #13)
> This same issue looks like it is reported upstream:
> https://bugs.launchpad.net/qemu/+bug/1884990
> 
> That claims that downgrading the vgabios fixes it.

Confirmed.  1.13 is broken, 1.12 works.  Going bisect now ...

Comment 16 Gerd Hoffmann 2020-06-25 08:54:02 UTC
Created attachment 1698762 [details]
bios fix

Comment 25 Danilo de Paula 2020-06-26 19:15:53 UTC
Exploded trees are in sync again.

Comment 34 Gerd Hoffmann 2020-07-02 12:10:38 UTC
Upstream commit is d11c75185276ded944f2ea0277532b7fee849bbc

Upstream plans: release seabios 1.14 by end of july, use that for qemu 5.1.

So with rhel-8.3-av rebasing to qemu 5.1 it makes sense to also rebase seabios to 1.14 and pick up the bugfix that way.

For rhel-8.2.1-av we'll have to backport the bugfix.

Comment 45 Guo, Zhiyi 2020-07-09 02:05:51 UTC
Reproduce this issue against seabios-bin-1.13.0-1.module+el8.2.0+5520+4e5817f3.noarch

Steps:
Try to boot a windows 10 2004 VM with cirrus-vga:
/usr/libexec/qemu-kvm \
-name guest=win10,debug-threads=on \
-S \
-object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-win10/master-key.aes \
-machine pc-q35-rhel8.2.0,accel=kvm,usb=off,dump-guest-core=off \
-cpu Haswell-noTSX-IBRS,vme=on,ss=on,vmx=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,md-clear=on,stibp=on,arch-capabilities=on,ssbd=on,xsaveopt=on,pdpe1gb=on,abm=on,ibpb=on,amd-ssbd=on,skip-l1dfl-vmentry=on,pschange-mc-no=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff \
-m 8192 \
-overcommit mem-lock=off \
-smp 2,sockets=1,dies=1,cores=1,threads=2 \
-uuid acd4cd59-5cb9-4c5f-9624-3a44828f5d78 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=35,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-reboot \
-global ICH9-LPC.disable_s3=1 \
-global ICH9-LPC.disable_s4=1 \
-boot strict=on \
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 \
-blockdev '{"driver":"file","filename":"/home/win10.qcow2","node-name":"libvirt-2-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \
-device ide-hd,bus=ide.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2,write-cache=on \
-blockdev '{"driver":"file","filename":"/home/en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2cc.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1,bootindex=1 \
-netdev tap,fd=36,id=hostnet0 \
-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:42:d2:64,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-vnc 0.0.0.0:0 \
-device cirrus-vga,id=video0,bus=pcie.0,addr=0x1 \
-device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2. Connect to vnc console

After step 2, find win10 screen is a gray and resolution is 640x480

Verify this issue against seabios-bin-1.13.0-2.module+el8.2.1+7284+aa32a2c4.noarch

After step 2, win10 screen has normal color and resolution is 1024 x 768

Comment 47 errata-xmlrpc 2020-07-28 07:13:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3172

Comment 48 John Ferlan 2020-10-01 11:11:20 UTC
*** Bug 1873566 has been marked as a duplicate of this bug. ***


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