Bug 1252677
| Summary: | guests starting in virt-manager with larger screen size than previously | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jens Petersen <petersen> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 22 | CC: | berrange, crobinso, petersen, pnemade, projects.rg, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-09-12 15:56:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jens Petersen
2015-08-12 05:11:45 UTC
This might be something along the lines of: https://bugzilla.redhat.com/show_bug.cgi?id=1240820 But you say you've seen this on f22 as well, are you using the fedora-virt-preview repo? What libvirt version do you have? Is this for new VMs only, or even pre-existing ones? I too saw this on Fedora 22 few days ago but as fedora 23 got frozen I stopped using virt-manager for sometime and now fresh installed f23 as host system last week. I today tried to install F23 Alpha using virt-manager, first time on this fresh system. The moment I got anaconda installation screen it showed bigger screen( unable to fit on all contents on same screen). I tried different options in View menu. Finally got full contents when enabled just checkbox View->Scale Display-> "Auto resize VM with windows" and View->Scale Display-> Always. This was not the case in Fedora 22 host. So, I can reproduce above for f23 on f23 for new VM's. $ rpm -qa | grep virt | sort libgovirt-0.3.3-2.fc23.x86_64 libvirt-client-1.2.18-1.fc23.x86_64 libvirt-daemon-1.2.18-1.fc23.x86_64 libvirt-daemon-config-network-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-interface-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-network-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-nodedev-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-nwfilter-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-qemu-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-secret-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-storage-1.2.18-1.fc23.x86_64 libvirt-daemon-kvm-1.2.18-1.fc23.x86_64 libvirt-gconfig-0.2.1-1.fc23.x86_64 libvirt-glib-0.2.1-1.fc23.x86_64 libvirt-gobject-0.2.1-1.fc23.x86_64 libvirt-python-1.2.18-1.fc23.x86_64 redland-virtuoso-1.0.17-4.fc23.x86_64 virt-manager-1.2.1-2.fc23.noarch virt-manager-common-1.2.1-2.fc23.noarch Especially Gtk2 based guests seem to suffer from this restriction in somewhere the complex SPICE logic. Easily reproduced today also. Host is using parag@f23 ~]$ rpm -qa | grep virt | sort libgovirt-0.3.3-2.fc23.x86_64 libvirt-client-1.2.18-1.fc23.x86_64 libvirt-daemon-1.2.18-1.fc23.x86_64 libvirt-daemon-config-network-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-interface-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-network-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-nodedev-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-nwfilter-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-qemu-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-secret-1.2.18-1.fc23.x86_64 libvirt-daemon-driver-storage-1.2.18-1.fc23.x86_64 libvirt-daemon-kvm-1.2.18-1.fc23.x86_64 libvirt-gconfig-0.2.2-1.fc23.x86_64 libvirt-glib-0.2.2-1.fc23.x86_64 libvirt-gobject-0.2.2-1.fc23.x86_64 libvirt-python-1.2.18-1.fc23.x86_64 redland-virtuoso-1.0.17-4.fc23.x86_64 virt-manager-1.2.1-3.fc23.noarch virt-manager-common-1.2.1-3.fc23.noarch This is really causing issues with installation UI and then in installed system the window is way to bigger. Poked at this, turns out its a spice-gtk issue with a fix upstream. Duping to that bug, I'll do builds shortly *** This bug has been marked as a duplicate of bug 1240721 *** |