Red Hat Bugzilla – Bug 1023049
Switching to VT and back changes resolution to 640x400
Last modified: 2015-05-31 15:02:36 EDT
Created attachment 815789 [details]
bug demonstration video
Description of problem:
When I boot into Fedora 20 GNOME LiveCD and switch to tty2 and back, the resolution changes to 640x400 (as reported by xrandr). It doesn't happen always, but mostly. If I do it several times, I am able to reproduce it always.
During the back-to-GUI switch, this is printed to system journal:
> kernel: kvm: zapping shadow pages for mmio generation wraparound
When edit my VM properties and change Spice to VNC, the problem disappears.
Version-Release number of selected component (if applicable):
F20 Beta TC5 Live Desktop x86_64
90% (100% with several retries)
Steps to Reproduce:
1. create a VM in virt-manager
2. boot F20 Live
3. switch to tty2 and back
The guest system journal prints this during the switch:
Oct 24 09:50:01 localhost systemd: Starting Getty on tty2...
Oct 24 09:50:01 localhost systemd: Started Getty on tty2.
Oct 24 09:50:01 localhost spice-vdagentd: closed vdagent virtio channel
Oct 24 09:50:02 localhost kernel: input: spice vdagent tablet as /devices/virtual/input/input5
Oct 24 09:50:02 localhost spice-vdagentd: opening vdagent virtio channel
Oct 24 09:50:03 localhost kernel: input: spice vdagent tablet as /devices/virtual/input/input6
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
I haven't seen this with f21 or f22 host/VM combos, so closing as CURRENTRELEASE