CentOS7 VirtualBox Resolution limited to 1024?

[wutsinterweb]

I am new here, and still pretty new to Linux and trying to learn as I go.

I have the latest updated CentOS 7 installed in my virtual box in Mint and ran through the KDE GUI the Guest Additions from the KDE file manager inside the CentOS 7 VM. I cannot change my resolutions at all, not higher, not lower. I am stuck at 1024x768 and my monitor will do 1920x1080. I'm using a pretty old video card but all my other VMs work fine with resolutions, my system is a 4th gen i5 with 32 GB RAM, Z97 board.

I tried this thread:

viewtopic.php?f=49&t=59780&p=252502&hil ... on#p252502

With this line:

Code: Select all

VBoxManage getextradata vboxvm enumerate

And I got this in the terminal emulator:

VBoxManage getextradata vboxvm enumerate
bash: VBoxManage: command not found

There are a number of old posts going back to 2010 and such talking about making changes to X11, but this is 2017 and I don't want to break my VM, I've already done that a couple times messing around with this.

[TrevorH]

The VBoxManage command needs to be run on the host not the guest.

However I believe that if you installed the vbox guest additions correctly/successfully then it shouldn't need that. You might want to check with the vbox folks to find out how to tell if it worked or not. Or just repeat it to make sure and read the relevant log file in /var/log to check what it did if it scrolls past too quickly to read.

[wutsinterweb]

Ok, yeah, it showed having completing all tasks with the Guest Additions install, no errors, and all my other VMs of Windows and other Linux Distros work on this same system with guest additions.

May I ask something else that I am trying to figure out that is related?

VB installs Guest Additions with its VM software, but I cannot figure out where that ISO is in the CentOS directory path. I found, in /dev/disk/by-label a blue BBOXADDITIONSxxxxx but no .iso on the end, so I don't think it's working as an iso? I wanted to manually mount it with term and try doing the process of installing GA IN term.

I also wonder if my Guest Additions is too old, it was updated not long ago, but if it were wouldn't it throw up an error?

[TrevorH]

If I remember correctly, on the guest menu you should have an option to mount the iso - which is actually on the host - on the Devices menu, there's an "Insert Guest Additions CD..." option. Once you do that it should just be a matter of mounting /dev/sr0 on a directory on the guest and going from there.

[wutsinterweb]

Ah, /dev/sr0 (or something, but right in the dev directory itself. Ah!

[wutsinterweb]

Solved:

As per your advice to check with VBox folks I found a thread of someone with a slightly different issue but that a particular version of Guest Additions they listed should be used. Ran it, all good now.

[dalepres]

Since this is current and, I think, related to my issue, I'm going to add mine here instead of a new thread.
It could be a Virtual Box issue, but the problem I am having, similar to the OP's, only happens after doing yum update on build 1708. My older builds all work with guest additions installed and even 1708 builds work up until the point I run yum update. Once I run that, the screen goes back to 1024x768 and I can expand the window but the guest doesn't expand to go with it. Auto-size guest is grayed out on the view menu as is Virtual Screen Resize.

So the problem comes from some update to 1708 builds applied to VMs running on my hardware - NVidia GX970 graphics on my laptop. Has anyone else seen this problem? It's very easily reproduceable, at least on my laptop.

*edit* just to be clear, I meant that my problem is resizing, similar to the OPs. He didn't say whether yum update had anything to do with his issue. */edit*

THanks,

Dale

[TrevorH]

You have to reinstall the guest additions for each new kernel.

[dalepres]

I have reinstalled the guest additions but it didn't help.

[hunter86_bg]

Can you log off this VM and before login select the small 'gear' icon and select the 'gnome classic' option.
After that log in and write us if there is a difference.