Red Hat Bugzilla – Bug 500057
vesa driver stopped working inside KVM-84
Last modified: 2018-04-11 02:45:34 EDT
Description of problem:
The Xorg vesa driver stopped recognizing the emulated graphics card (VESA mode) inside KVM-84.
Probably related to Ubuntu bug #356133.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(II) VESA: driver for VESA chipsets: vesa
(WW) Falling back to old probe method for vesa
(EE) No devices detected.
Access emulated graphics card using vesa driver.
Host system: Debian lenny, x86_64, Linux 2.6.26 (standard Debian kernel), kvm-84
Filed upstream as #21661.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 343822 [details]
This configuration worked fine before.
Created attachment 343823 [details]
Xorg.0.log for attached xorg.conf (Attachment #343822 [details])
Created attachment 343824 [details]
Xorg.0.log when run without xorg.conf
Created attachment 343825 [details]
xorg.conf with BusID specified
Created attachment 343827 [details]
Xorg.0.log for xorg.conf with BusID (Attachment #343825 [details])
It was reported that specifying the BusID worked in one particular case (with kvm-85 userspace, though), so I tested that as well. Made no difference.
The pv console device doesn't claim its pci class correctly, and the X server treats it as a candidate primary video device. This is way lame.
Fixed in 220.127.116.111-1.fc11
Created attachment 345277 [details]
Xorg.0.log with 18.104.22.1681-1 / 2.2.0-3
Still fails for me with the same error message. Versions:
Created attachment 345973 [details]
Xorg.0.log for KVM-85
While I can now confirm it works using KVM-85 (not KVM-84) on Ubuntu Jaunty, it doesn't for Fedora.