Hi
I searched enough about this problem but couldn’t find the answer.
I have installed VirtualBox, but screen not running in fullscreen mode!
Please tell me what’s the problem.
What does “screen not running in fullscreen mode!” mean?
Can you describe the problem in more detail, please?
Also it might be helpful to know what OS you are running as guest. IIUYC, the host is openSUSE 13.2, right?
You might have to install the guest additions in the guest for fullscreen mode to work.
Works for me without using guest additions, but use Oracle_VM_VirtualBox_Extension_Pack-4.3.20-96996.vbox-extpack.
Using precompiled repositories of openSUSE, for VirtualBox Kernel_stable_standard :
http://download.opensuse.org/repositories/Virtualization/Kernel_stable_standard/ but this : http://download.opensuse.org/repositories/Kernel:/stable/standard/
Everything works well in 13.1,13.2 and Tumbleweed.
X79-PRO:~ # zypper se -si VirtualBox
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+------------------------------+---------+----------------------------------+--------+--------------------------------------
i | virtualbox | package | 4.3.20-126.2 | x86_64 | Virtualization/Kernel_stable_standard
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-126.1 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.26 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.25 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.24 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.23 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.22 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.21 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.20 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.2_2.g88366a3-125.18 | x86_64 | (System Packages)
i | virtualbox-guest-kmp-desktop | package | 4.3.20_k3.18.4_1.gabfc700-126.2 | x86_64 | Virtualization/Kernel_stable_standard
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-126.1 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.26 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.25 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.24 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.23 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.22 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.21 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.3_1.gc3e148f-125.20 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.2_2.g88366a3-125.18 | x86_64 | (System Packages)
i | virtualbox-host-kmp-desktop | package | 4.3.20_k3.18.4_1.gabfc700-126.2 | x86_64 | Virtualization/Kernel_stable_standard
i | virtualbox-qt | package | 4.3.20-126.2 | x86_64 | Virtualization/Kernel_stable_standard
My host :
frank@X79-PRO:/home/frank> inxi -Fz
System: Host: X79-PRO Kernel: 3.18.4-1.gabfc700-desktop x86_64 (64 bit) Desktop: KDE 4.14.4
Distro: openSUSE 20150127 (Tumbleweed)
Machine: Mobo: ASUSTeK model: P9X79 PRO v: Rev 1.xx Bios: American Megatrends v: 4701 date: 05/07/2014
CPU: Quad core Intel Core i7-3820 (-HT-MCP-) cache: 10240 KB
clock speeds: max: 5700 MHz 1: 2602 MHz 2: 2622 MHz 3: 2658 MHz 4: 2787 MHz 5: 2057 MHz 6: 3034 MHz
7: 2284 MHz 8: 2389 MHz
Graphics: Card: NVIDIA GK107 [GeForce GTX 650]
Display Server: X.Org 1.16.2 drivers: nouveau (unloaded: fbdev,nv,vesa) Resolution: 1360x768@60.02hz
GLX Renderer: Gallium 0.4 on NVE7 GLX Version: 3.0 Mesa 10.4.3
Audio: Card-1 NVIDIA GK107 HDMI Audio Controller driver: snd_hda_intel
Card-2 Intel C600/X79 series High Definition Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k3.18.4-1.gabfc700-desktop
Network: Card: Intel 82579V Gigabit Network Connection driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 1120.2GB (67.0% used) ID-1: /dev/sda model: WDC_WD1002FAEX size: 1000.2GB
ID-2: /dev/sdb model: KINGSTON_SH103S3 size: 120.0GB
Partition: ID-1: / size: 41G used: 23G (60%) fs: btrfs dev: /dev/sda3
ID-2: /tmp size: 41G used: 23G (60%) fs: btrfs dev: /dev/sda3
ID-3: /home size: 890G used: 675G (76%) fs: btrfs dev: /dev/sda4
ID-4: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 25.0C mobo: 24.0C gpu: 26.0
Fan Speeds (in rpm): cpu: 270000 mobo: 270000 fan-1: 793 fan-3: 0 fan-4: 0 fan-5: 0
Info: Processes: 358 Uptime: 17:48 Memory: 3149.5/64501.0MB Client: Shell (ksh) inxi: 2.2.18
My guest :
vbox@linux-4kq7:~> inxi -Fz
System: Host: linux-4kq7 Kernel: 3.18.3-1-desktop x86_64 (64 bit) Desktop: KDE 4.14.4
Distro: openSUSE 20150127 (Tumbleweed)
Machine: System: innotek product: VirtualBox v: 1.2
Mobo: Oracle model: VirtualBox v: 1.2 Bios: innotek v: VirtualBox date: 12/01/2006
CPU: Dual core Intel Core i7-3820 (-MCP-) cache: 6144 KB
clock speeds: max: 3602 MHz 1: 3602 MHz 2: 3602 MHz
Graphics: Card: InnoTek Systemberatung VirtualBox Graphics Adapter
Display Server: X.Org 1.16.2 drivers: ati,vboxvideo (unloaded: fbdev,vesa)
Resolution: 1360x681@60.00hz
GLX Renderer: Chromium GLX Version: 2.1 Chromium 1.9
Audio: Card Intel 82801AA AC'97 Audio Controller driver: snd_intel8x0 Sound: ALSA v: k3.18.3-1-desktop
Network: Card: Intel 82540EM Gigabit Ethernet Controller driver: e1000
IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 73.7GB (13.4% used) ID-1: /dev/sda model: VBOX_HARDDISK size: 73.7GB
Partition: ID-1: / size: 27G used: 7.3G (28%) fs: btrfs dev: /dev/sda3
ID-2: /tmp size: 27G used: 7.3G (28%) fs: btrfs dev: /dev/sda3
ID-3: /home size: 40G used: 18M (1%) fs: btrfs dev: /dev/sda4
ID-4: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 187 Uptime: 0:03 Memory: 428.5/9879.1MB Client: Shell (bash) inxi: 2.2.18
Try checking the settings and provide more data, thanks and best regards.
Sorry for my English
Well, as I said, it depends on the guest.
If you install openSUSE as guest, the guest additions are already included and installed automatically. So you are in fact using guest additions. 
And I don’t think the extension pack is necessary. From the VirtualBox manual:
Additional extension packs can be downloaded which extend the functionality of the VirtualBox base package. Currently, Oracle provides the one extension pack, which can be found athttp://www.virtualbox.organd provides the following added functionality:
- The virtual USB 2.0 (EHCI) device; see Section 3.10.1, “USB settings”.
- VirtualBox Remote Desktop Protocol (VRDP) support; see Section 7.1, “Remote display (VRDP support)”.
- Host webcam passthrough; see chapter Section 9.7.1, “Using a host webcam in the guest”.
- Intel PXE boot ROM.
- Experimental support for PCI passthrough on Linux hosts; see Section 9.6, “PCI passthrough”.
No mention of fullscreen mode.
Using precompiled repositories of openSUSE, for VirtualBox Kernel_stable_standard :
http://download.opensuse.org/repositories/Virtualization/Kernel_stable_standard/ but this : http://download.opensuse.org/repositories/Kernel:/stable/standard/
Everything works well in 13.1,13.2 and Tumbleweed.
I don’t think a newer Kernel is necessary either.
I don’t find any explicit mention of fullscreen mode in the manual, but for additional resolutions and for being able to resize the virtualbox window (and changing the guests resolution by doing so) you do need the guest additions installed in the guest (which include a graphics driver for the emulated vbox video card).
Perhaps it relates to improvements comments https://www.virtualbox.org/manual/ch04.html , where said : Better video support ( and also in 1.8.5. Resizing the machine’s window)
Also from version 4.3.x see no difference between having added the guest additions ( except add me to the group of vboxsf ) , is not whether it is because it comes so in repositories .
Using precompiled repositories of openSUSE, for VirtualBox Kernel_stable_standard
I chose to use these repositories instead of using dkms, which if used in another pc, but with nvidia drivers.
Anyway I still have much to learn, not whether the problem that has, is because I assign little ram memory on your video settings .
Thank you very much for the comments and kind regards.
Post Data maybe this link will can be helpful, because it has all versions and additions : http://download.virtualbox.org/virtualbox/
Yes, I think so.
Also from version 4.3.x see no difference between having added the guest additions ( except add me to the group of vboxsf ) , is not whether it is because it comes so in repositories .
I’m not sure I understand that correctly.
Again, if you install openSUSE in a VM, the guest additions are automatically installed. So of course you see no difference if you install them manually later.
I chose to use these repositories instead of using dkms, which if used in another pc, but with nvidia drivers.
You do not need those repos. If you only use the kernel included in your openSUSE version, the standard VirtualBox packages from the distribution will work as well, even when there is a kernel update.
If you use the standard kernel, you can also use the Virtualization repo to get the latest VirtualBox version, but in that case you need the standard one that you can find in YaST->Software Repositories->Add->Community Repositories.
The second of the two repos you mentioned is Kernel:stable. This contains the latest kernel. You don’t need this to have VirtualBox working without dkms.
It’s actually the other way round: if you use this repo to get the latest kernel, the standard VirtualBox packages (built for the kernel included in the distribution) will not work any more, so you need the first repo you mentioned as well.
But normally you should not need the latest kernel (in particular not for VirtualBox), also for the nvidia driver it’s easier to just stay with the standard kernel shipped with your openSUSE version.
Anyway I still have much to learn, not whether the problem that has, is because I assign little ram memory on your video settings .
Hm?
I thought it works fine for you?
Post Data maybe this link will can be helpful, because it has all versions and additions : http://download.virtualbox.org/virtualbox/
VirtualBox has a menu entry for downloading/installing the guest additions automatically, you don’t have to download them manually.
And I think it’s easier to use the packaged VirtualBox version.
As you write yourself, fullscreen mode should work with that anyway (I cannot try myself at the moment, but will do so as soon as possible).
Hi,
Yes guest additions comes builtin as a kernel module on any modern openSUSE release, so mouse integration and screen auto resize should work-out-of-the-box.
Hello:
Although not appreciation changes in the resolution in openSUSE in guest mode, if it has done installing XP (guest adittions corrects the display resolution, format 4:3 to 16:9, it being all good, or guest Ad… Improves the resolution of screen)
. From the same program of VirtualBox, i have also the Guest Adittions downloading (from internet) , but is also available in the guest mode , this option for if you want to done manually .
As it is in Spanish, he left a red arrow indicating from where you can do .
Everything that you mentioned me is correct, thank you for this .
What of the kernel, is because I’ve been testing different arquitecturar of Intel, at least several teams performed tests of openSUSE . (Haswell, Broadwell, Sandy Bridge and Ivy Bridge… ) : with openSUSE with both repositories/Virtualization/Kernel_HEAD_standard/ , As with Kernel_stable_standard/ , (both repositories available , but there is a small delay when there is a kernel update, you might be left one day without work, but the next is corrected everything and once again to run ).
All updates are at the host level (but also modifies guest, with updates , yesterday and before yesterday has happened ) . Sometimes if it does change the kernel, but incl. does nothing; and there is not
/etc/init.d/vboxdrv setup
because
X79-PRO:~ # /etc/init.d/vboxdrv setup
Recompiling VirtualBox kernel module, NOT. It has been packaged. done
,Why is already compiled .
If it works everything you’ve said that your dkms or using the kernel of the distribution .
Test teams are: p9x79 with Icore7 64 Gb of RAM, p8z77-m Icore7 16Gb ram, Z87 deluxe 32Gb ram and Rampage iv black edition 64Gb of RAM (all testing with openSUSE) .
Thank you for the comments, this will help me to correct the work that I am doing in the openSUSE wiki.
regards
i am sorry for my bad english
X79-PRO:~ # /etc/init.d/vboxdrv setup
Recompiling VirtualBox kernel module, NOT. It has been packaged. done,Why is already compiled .
If it works everything you’ve said that your dkms or using the kernel of the distribution .
Test teams are: p9x79 with Icore7 64 Gb of RAM, p8z77-m Icore7 16Gb ram, Z87 deluxe 32Gb ram and Rampage iv black edition 64Gb of RAM (all testing with openSUSE) .
Thank you for the comments, this will help me to correct the work that I am doing in the openSUSE wiki.
Hi,
There are two version of virtualbox package that you can install, one from the opensuse repos which is where your vbox package probably came from. Another one is from virtualbox.org, which requires some kernel packages and
vboxdrv setup
is used.
Thanks for the help and information.
I will try to prove that another version, on another computer.
I hope to be lucky.
Greetings