[Solved]Cannot get wide screen screen on Fedora guest

[DrongoBG]

Hey guys, the title sais it all. I have a Fedora guest and it doesn't want to go to widescreen resolution.

Host OS: Win8 x64
Guest OS: Fedora 17 x86
Vbox version: 4.2.12
Guest additions CD: 4.2.12

What I did: Right after first boot of the guest i entered

Code: Select all

yum install dkms

All went ok, I rebooted the guest.

After that I mounted the guest additions CD and started the install, where something failed. Here's a log screenshot(yeah my shared clipboard is also broken :/)

Can anyone help me?

[Perryg]

This should help Howto: Install Linux Guest Additions

[DrongoBG]

Thank you! These steps are misssing in the official guide.

For those, who are too lazy to figure it out themselves (like me). Do this!

1. Run:

Code: Select all

yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel

Or alternatively:

Code: Select all

yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-pae-devel

2. Update system to latest version via the update tool

3. Install GA

[DrongoBG]

Alright, new problem.

After installing guest additions, when I run fedora on fullscrenn, the UI starts to freeze from time to time. I can't really explain it. It's not laggy, it's not with low performance, it just.... well freezes from time to time. When I run in scaled mode (same resolution) this problem is gone. What could this be?

[mpack]

How big is the fullscreen display, and how much graphics memory did you allocate in the VM settings?

[DrongoBG]

The resolution of the fullscreen display is 1366x768, and so is the guest os resolution. Graphics memory is 256, and RAM is 2048, CPUs - 4.

[mpack]

A VM log file would perhaps help. See Minimum information needed for assistance.

[DrongoBG]

VBox version: 4.2.12 r84980
Host: Windows 8 64bit, 8GB RAM DDR3, Nvidia GeForce 630M with 2GB dedicated VRAM + an integrated video, Intel Core i7-3632QM.
Guest: Fedora 17 from here (image 8 ) -> http://virtualboxes.org/images/fedora/#fedora17

Guest Settings:

Code: Select all

Name:            MyFedora
Groups:          /
Guest OS:        Fedora
UUID:            aa154110-a4a6-4f36-a365-b6d649a3b8b6
Config file:     D:\Fedora-17-x86\Fedora-17-x86.vbox
Snapshot folder: D:\Fedora-17-x86\Snapshots
Log folder:      D:\Fedora-17-x86\Logs
Hardware UUID:   aa154110-a4a6-4f36-a365-b6d649a3b8b6
Memory size:     2048MB
Page Fusion:     off
VRAM size:       256MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  4
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             off
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
State:           powered off (since 2013-05-28T15:11:52.000000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0):            Controller IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            Controller SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
Controller IDE (1, 0): Empty
Controller SATA (0, 0): D:\Fedora-17-x86\Fedora-17-x86.vdi (UUID: 4778cddf-2105-
4c21-a9ed-2f1b1abdbe39)
NIC 1:           MAC: 080027E64A19, Attachment: NAT, Cable connected: on, Trace:
 off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Prom
isc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: AC97)
Clipboard Mode:  Bidirectional
Drag'n'drop Mode:  disabled
VRDE:            disabled
USB:             enabled
EHCI:            enabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Guest:

Configured memory balloon size:      0 MB

[Perryg]

You are not actually running on your nvidia card but an intel graphics adapter. See log:

• 00:00:03.274971 OpenGL Info: Render SPU: GL_VENDOR: Intel
  00:00:03.274994 OpenGL Info: Render SPU: GL_RENDERER: Intel(R) HD Graphics 4000
  00:00:03.275002 OpenGL Info: Render SPU: GL_VERSION: 4.0.0 - Build 9.17.10.2867

This could be the cause of all your issues. I believe this is due to power saving and you should see how to set the host to use your full video card when using VBox/guests.

That and using someone else's build that was create using completely different hardware.

[DrongoBG]

Well yeah, that solved the problem. The nvidia driver SHOULD automatically switch to the Nvidia card when sensing that the integrated can't handle the process, but this was not the case. When I made it run on the nvidia GPU everything went fine. Thank you for the help.