Bug 17412 - KVM Full-Screen mode not supported
Summary: KVM Full-Screen mode not supported
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: App/compiz (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: David Reveman
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-02 09:50 UTC by fabiengb
Modified: 2018-06-12 19:07 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description fabiengb 2008-09-02 09:50:36 UTC
Configuration
 
CPU : Intel Core 2 Duo E6850
OS : Ubuntu 8.04
Kernel : 2.6.24-19-generic
Compiz version details :
 
Checking for Xgl: not present. 
Detected PCI ID for VGA: 01:00.0 0300: 10de:0402 (rev a1) (prog-if 00 [VGA controller])
Checking for texture_from_pixmap: present. 
Checking for non power of two support: present. 
Checking for Composite extension: present. 
Comparing resolution (1280x1024) to maximum 3D texture size (8192): Passed.
Checking for nVidia: present. 
Checking for FBConfig: present. 
Checking for Xgl: not present. 
compiz 0.7.4
 
 
Bug reproduction :
 
- Active compiz specials effects
- Run virtual machine
- Set vm resolution to the same resolution of your host
- Switch to full-screen mode
 
-> BUG : 
- KVM switch quickly to full-screen mode, and then, switch back to window mode
- It becomes very difficult to control vm mouse (cursor movement very weird)
- If vm resolution switched back to a lower resolution, host mouse pointer is clipped to the vm window (!)
- Vm must be shut down to unclip mouse pointer
 
No problem when compiz deactivated.
Comment 1 Adam Jackson 2018-06-12 19:07:55 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.