Created attachment 691036 [details] 'overflowing' image under a virt-manager install of F18 Description of problem: Anaconda, in F18, lacks a documented command / boot time option to restrict a GUI install to permit keeping the visual image within limited sizes I received 'push back' for thread hijacking from Adam Williamson yesterday on the anaconda mailing list, when I posted > * There's an awful lot of horizontal padding There is an awful lot of scrolling right and left and up and down, period, searching for the 'next' button to push I understand the _desire_ to use lots of screen real estate, but darn it, I'd rather have an interface that lived in the northwest corner as as to its control cluster, so I did not have to 'chase around' using elevator bars looking for what to click next Adopting a statement that the installer screen controls must live in the Northwest 1024x800 would attain that end -------------- his response: Please, please don't do this. Don't take a thread about a specific issue which is asking specific questions and insert barely related other problems. All it leads to is confusion and irritation. If you want to discuss a different problem, start a different thread. > Adopting a statement that the installer screen controls must > live in the Northwest 1024x800 would attain that end They do. It is tested down to 800x600. That screenshot is at 1024x768. --------------- (back to me) Not that I can see, to get to an install image limited to 800 x 600 by any documented I checked the boot options available using 'tab' at the start of the boot. I checked the installation documentation at: http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/ap-admin-options.html I checked the outlined anaconda wiki documentation (it is stale, referring to being stale as of F17) https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options I fired up virt-manager and started a local ISO based install -- The screen show is an exact 'import' of what was offered. 'identify' says the image is: rrold@centos-6 ~]$ identify anaconda-install-not-size_limited.png anaconda-install-not-size_limited.png PNG 805x771 805x771+0+0 16-bit DirectClass 107kb so: 805x771 and clearly running off the bottom and right making virt-manager full screen, it eats: rrold@centos-6 ~]$ identify FS-shot.png FS-shot.png PNG 1680x1050 1680x1050+0+0 16-bit DirectClass 164kb so: 1680x1050 (which is the local monitor's display size per: xdpyinfo ...) Version-Release number of selected component (if applicable): anaconda (initial) for F18 ... anaconda-18.37.11-1 How reproducible: as above Steps to Reproduce: as above Actual results: overly large image with no way to constrini its size per the Williamson comment Expected results: a documented way to exploit the asserted available limitation on sizes of install GUI images by documenting the needed boot options Additional info:
Created attachment 691038 [details] unconstrained 'full screen' image
Did you try appending "resolution=WxH" to the kernel command line? Fedora 18 Installation Guide Chapter 11. Boot Options 11.1.2. Configuring the Interface To use a specific display resolution, enter resolution=setting as a boot option. For example, to set the display resolution to 1024×768, enter: linux resolution=1024x768 http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/ap-admin-options.html#sn-boot-options-interface
NB: Some of the installer windows are misaligned at 800x600: Bug 901551 - Anaconda Screens are larger than VM 800x600
I tried running the installer under virt-manager. The default video driver is qxl, and qxl defaults to 1024x768. If you get the scroll bars, can't you just resize the VM window until they disappear?
(In reply to comment #4) > I tried running the installer under virt-manager. The default video driver > is qxl, and qxl defaults to 1024x768. If you get the scroll bars, can't you > just resize the VM window until they disappear? That test was in a VM with the qxl driver. With virt-manager running directly on an F18 bare-metal host, the default driver is cirrus. The std and qxl drivers default to a smaller VM window. virt-manager also supports various resizing and scaling options.
anaconda defaults to running at the highest resolution available that X selects, and then runs full screened in that. If the UI is ending up weird, it's likely a bug somewhere in GTK or X land. We very rarely specify widget sizes, and it's only for certain small pieces. For changing the resolution that the environment anaconda runs in, you need to pass resolution= on the command line.
testing the: linux resolution=1024x768 variant as to comment 4, the problem is that the full screen resolution default is pushed off the bottom of the screen by XFCE's top widget bar, and crowded at the bottom by the bottom widget bars, resulting in an inability to see the entire install screen without scrolling around
no, it looks as though 'Plymouth' resizes the screen away from the passed in resolution-1024x768 argument Right after the image resized itself above 2014x768, I snapshotted: acme.png errold@centos-6 ~]$ identify acme.png acme.png PNG 805x646 805x646+0+0 16-bit DirectClass 40.5kb and it is full height (opening the elevator bar) as acem2.png errold@centos-6 ~]$ identify acme2.png acme2.png PNG 1298x890 1298x890+0+0 16-bit DirectClass 48.6kb
Created attachment 692804 [details] right after it over-rides the command line resolution- argument
Created attachment 692805 [details] it is again full X screen height ;(
(In reply to comment #7) > testing the: > linux resolution=1024x768 > variant > > as to comment 4, the problem is that the full screen resolution default is > pushed off the bottom of the screen by XFCE's top widget bar, and crowded at > the bottom by the bottom widget bars, resulting in an inability to see the > entire install screen without scrolling around Are you running the installer from a DVD image or a Live image? Setting the resolution on the kernel command line only works with the DVD. While running a Live image, you can set the display resolution from the desktop with the Display control panel before starting the installer. Have you tried configuring a different video driver in virt-manager? The "std" and "qxl" video drivers default to a lower resolution (1024x768) than the "cirrus" driver in my tests. Tested with: $ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Final/Final/Fedora-18-x86_64-Live-XFCE.iso -vga std -boot menu=on -usbdevice mouse
(In reply to comment #11) ... > Have you tried configuring a different video driver in virt-manager? > > The "std" and "qxl" video drivers default to a lower resolution (1024x768) > than the "cirrus" driver in my tests. ... Confusingly, qemu and virt-manager use different names for some of the video drivers. What qemu calls "std" is what virt-manager calls "vga". This can be verified by looking at the -vga option of the qemu-kvm command line while running a virt-manager emulation: $ ps -ef | grep qemu qemu 9021 1 3 19:42 ? 00:01:50 /usr/bin/qemu-kvm -name vm-1 ... -vga std ... BTW, the third and fourth screenshots show that the cirrus video driver is being used.
as to comment 11 I am using virt-manager and Fedora-18-x86_64-DVD.iso under Centos 6, updated to current debian-6.0.1a-amd64-netinst.iso lost+found zoot-i386.iso Fedora-17-x86_64-DVD.iso redhat-5.2-i386.iso Fedora-18-x86_64-DVD.iso valhalla-i386-disc1.iso [root@centos-6 ISOs]# which virt-manager /usr/bin/virt-manager [root@centos-6 ISOs]# rpm -qf /usr/bin/virt-manager virt-manager-0.9.0-14.el6.x86_64 [root@centos-6 ISOs]# comemnt 12 does not ask a question or that I perform an action and report results that I can see
(In reply to comment #13) ... > virt-manager-0.9.0-14.el6.x86_64 ... That is a very old version of virt-manager. The latest Fedora version is: virt-manager-0.9.4-4.fc18 https://admin.fedoraproject.org/updates/search/virt-manager Can you reproduce this problem with Fedora 18?
As to comment 14, I will set up a test box; the quoted libvirt version is the 'stock' one for a RHEL 6 install, which seems a reasonable platform for a virtualization dom0 host for guest instance domU installs, however
I'm seeing a lot of comments here indicating problems with using virt-manager, but not really anything having to do with anaconda. Just today, I was testing anaconda on more constrained resolutions and with the addition of -vga std -display sdl, using inst.resolution= worked just fine for me.