https://bugzilla.novell.com/show_bug.cgi?id=813809 https://bugzilla.novell.com/show_bug.cgi?id=813809#c0 Summary: Virt-Manager Resolution issues - Cirrus, and switching emulation Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: KVM AssignedTo: kvm-bugs@forge.provo.novell.com ReportedBy: tonysu@su-networking.com QAContact: jdouglas@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Unknown whether these issues are all related or separate. 1. Using the default Cirrus emulated driver, changing screen resolution from default by using the KDE "Configure Desktop" tool can result in kaleidoscope effect. Does not switch back to previous resolution after a timeout. Unable to think of a way to troubleshoot this when the display is "crazy." I have experienced this issue using both XFCE and KDE desktops on both 12.2 and 12.3 Host systems (other Desktopa and HostOS not tried). Workaround: Although I have not found a way to fix the problem, the Guest can be made usable by switching the "Video" option in Virtual Machine Manager to "qxl." Can also switch to other video emulators but resolution options for those are limited. 2. Once the video driver has been switched to qxl in Virtual Machine Manager and the changes applied, unable to switch back again to Cirrus. Can switch back and forth for any other emulated video except for this one situation. Attempting to re-enable Cirrus returns an error as follows Error changing VM configuration: XML error: ram attribute only supported for type of qxl Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/details.py", line 2477, in _change_config_helper self.vm.redefine_cached() File "/usr/share/virt-manager/virtManager/domain.py", line 335, in redefine_cached self._redefine_xml(xml) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 147, in _redefine_xml return self._redefine_helper(origxml, newxml) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 137, in _redefine_helper self._define(newxml) File "/usr/share/virt-manager/virtManager/domain.py", line 830, in _define self.conn.define_domain(newxml) File "/usr/share/virt-manager/virtManager/connection.py", line 814, in define_domain return self.vmm.defineXML(xml) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2808, in defineXML if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self) libvirtError: XML error: ram attribute only supported for type of qxl Reproducible: Always Steps to Reproduce: 1.Create a working KVM Guest, running openSUSE 12.3/XFCE or KDE with default Cirrus Video emulation. 2.Using the Desktop's Display Configuration tool, change to 800x600. 3. Wait. Previous working resolution is not re-enabled. 4. Force Shutdown. Unfortunately, it looks like modified "bad" video settings are retained. 5. Open Guest VM "Machine Details" 6. Click on Video 7. Click on "Model", dropdown will display a number of alternatives to Cirrus 8. Select qxl 9, Boot and verify thw system supports high resolutions. 10. Shutdown. 11. Following steps 5-7 again, select "cirrus" 12. Apply the change, which will return the error described above. Actual Results: 1. Returning resolution to previous after timeout does not work. Interesting this performs properly when resolution change is successful (using qxl video emulation). 2. Unable to switch back from qxl to cirrus video emulation. Expected Results: 1. Expected video resolution change to timeout and return to previous setting. 2. Expected to be able to change from qxl to cirrus video emulation. Am recommending this as "Normal" priority although I found a workaround because at least for me the workaround wasn't immediately obvious, I was just destroying and re-building Guests from scratch as being faster and simpler than attempting to troubleshoot, so could be considered "serious." But, once found the workaround (using qxl video emulation instead, and perhaps staying with it), it's a simple fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.