LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-04-2019, 08:20 PM   #16
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 924

Rep: Reputation: 353Reputation: 353Reputation: 353Reputation: 353

Okay, I'm gonna have to backtrack on my above statement the VirtualBox 6.0.0 is not broken.

Several issues just cropped up. I was doing an upgrade of a Slackware64-current machine that was a few updates behind, during the package upgrading it would freeze, the machine was workable, in other words I could Ctrl-C out of slackpkg (shudder). After a couple more tries with similar results I decided to wipe the machine out and start fresh using the DVD created from Alien Bob's mirror-slackware-current.sh. Two attempts at that, both failed, some sort of error that disk might be full (hogwash).

Long story short, I'm back on 5.2.22 r126460, all is well again. Yes 6.0.0 is broken at least for me.
 
Old 01-05-2019, 05:46 AM   #17
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
I've tried almost every combination.

I've always, at least for as long as i can remember kept the guest up to date with virtualbox-kernel-addons and virtualbox-addons. On Slackware Current have to jump through a few updates on kernel upgrades.

After the last kernel upgrade to 4.19.13 after not managed to resolve all the issues at the same time.

This is what I've done all on the guest

Start the guest. I have virtualbox-kernel-addons.5.2.8-4.14.71 installed. Get Full Screen, but mount.vboxsf fails.

Remove packages virtualbox-kernel-addons and virtualbox-addons and reboot.

Get Full Screen, but mount.vboxsf fails.

Compile virtualbox-kernel-addons and virtualbox-addons using virtualbox 5.2.8 and kernel 4.19.13.

Install virtualbox-kernel-addons-5.2.22_4.19.13-x86_64-1_SBo.tgz and virtualbox-addons-5.2.22-x86_64-1_SBo.tgz and reboot.

Get Full Screen, but mount.vboxsf fails.

Remove packages virtualbox-kernel-addons and virtualbox-addons and reboot.

Get Full Screen, but mount.vboxsf fails.

Install guestadditions 5.2.22 and reboot

Don't get Full Screen, but mount.vboxsf succeeds. I do see all the desktop, but it doesn't occupy the entire VirtualBox host window and even then the mouse can't be moved down to the lower third of the guest desktop.

It doesn't seem to make any difference if I follow the instructions given by Qury for GuestAdditions 6.0.1

As others seem to be able to get the guest working in all it's glory I'm beginning to wonder if there's something wrong with my installation of Slackware Current and I should try installing a new Slackweare Current VirtualBox guest from scratch. This may be a good idea even if it is just to practice the process of installing a fresh Slackware install.

Alex
 
Old 01-05-2019, 01:32 PM   #18
Aeterna
Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, CRUX, FreeBSD, Funtoo, HardenedBSD, OpenIndiana
Posts: 147

Rep: Reputation: Disabled
Quote:
Originally Posted by aikempshall View Post
Drakeo are you suggesting that I upgrade my host (14.2) to VirtualBox 5.2.22 and my 14.2+ client to 5.2.22 as well?
If I may add:
I have VB 5.2.22 installed on host Slackware (reverted from VB 6.0 because of sound issues and really slow disk access in the VM clients)
but my Slackware-current running as VM client has VBoxGuestAdditions 6.0 installed because client is running kernel 4.20.

This works well without any problems.

Last edited by Aeterna; 01-05-2019 at 01:35 PM.
 
Old 01-07-2019, 09:03 AM   #19
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
I've now done a fresh install of Slackware 14.2+ in a new VirtualBox Guest instance. Noticed that when I swapped over to init 4 that KDE occupied the full window of VirtualBox. This seems to confirm what I'd read in https://www.omgubuntu.co.uk/2018/01/...s-linux-kernel


Quote:
Coming to the Linux Kernel

Work to add features in VirtualBox Guest Additions to the Linux kernel is underway by kernel developers. The first fruits of their labor will appear in Linux 4.16.

These additional features are licensed under the GPL and sit in the kernel tree. That means no additional proprietary code or binary blobs are loaded on your system

Why does this matter?

Well, it means the next time you boot a Linux distribution with the Linux 4.16 (or later) kernel, VirtualBox Guest Additions will be already installed. You won’t need to enable, add, install or tweak anything (in theory).

With a clean install of Slackware 14.2+ I get ]
  1. the desktop of the guest occupying the complete VirtualBox host window;
  2. the shared clipboard doesn't work
  3. the mount for shared directories, using -t vboxsf, doesn't work

I then followed the instructions given by Qury to install GuestAdditions 6.0.1. I now get
  1. shared clipboard working
  2. the mount for shared folders, using -t vboxsf, working

And as a bonus the desktop of the guest still occupies the complete VirtualBox host window.

So a good result.

This thread has been side tracked, by me, from it's initial query which was why I couldn't compile virtual-kernel-addons.

The answer to that, which I accept, is that VirtualBox guest 5.2.8 is too far back to successfully compile against kernel 4.19.13.

During the course of the discussion I moved it on, with help from others, to dispensing with virtualbox-addons and virtualbox-kernel-addons for Linux Kernels greater then 4.16 or thereabouts and instead using Guest Additions.

I will dwell on this and see if there is anything I can do to fix the VirtualBox guest that started life with kernel 4.14.71 and finally ended with kernel 4.19.13 and has had various versions of virtualbox-addons, virtualbox-kernel-addons and Guest Addtions applied to it and is currently stuck with the guest desktop not occupying the full VirtualBox host window, but can mount shared directories and where the shared clipboard works.

Alex
 
Old 01-07-2019, 12:23 PM   #20
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 150

Rep: Reputation: 136Reputation: 136
Quote:
Originally Posted by aikempshall View Post
... is currently stuck with the guest desktop not occupying the full VirtualBox host window ...
What exactly do you mean by this?

I use Slackware64-current on a Windows 10 host (company laptop), when i maximize or set the guest to full screen, it sometimes does not change the resolution of the guest, however 1-2 subsequent switch to and from full screen mode (Ctrl+F) resolves this. (for the record i use xfce4 and lxdm login manager from slackbuilds.org)
 
Old 01-08-2019, 08:47 AM   #21
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
Quote:
Originally Posted by Qury View Post
What exactly do you mean by this?

I use Slackware64-current on a Windows 10 host (company laptop), when i maximize or set the guest to full screen, it sometimes does not change the resolution of the guest, however 1-2 subsequent switch to and from full screen mode (Ctrl+F) resolves this. (for the record i use xfce4 and lxdm login manager from slackbuilds.org)

I've used the wrong choice of words when I said full screen. What I mean is that I expect the guest desktop to use all of the window in the host Virtualbox. I've attached an example of what I don't want and another example of what I'm expecting.

Alex
Attached Thumbnails
Click image for larger version

Name:	What-I-am-expecting.jpg
Views:	9
Size:	42.9 KB
ID:	29427   Click image for larger version

Name:	What-i-do-not-want.jpg
Views:	8
Size:	38.5 KB
ID:	29428  
 
Old 01-08-2019, 10:15 AM   #22
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 150

Rep: Reputation: 136Reputation: 136
ok, i get it now. Try it with other desktop environments as well, when i was testing with KDE5 on my home machine (host was Slackware as well) then i had to manually set the display resolution in the guest too.
 
Old 01-15-2019, 05:58 AM   #23
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
Well still got problems here. Mostly whatever I do I end up with
  1. being able to share folders (vboxsf)
  2. getting the guest to automatically occupy the full window in the host. I think VirtualBox calls this dynamic resizing

but not both at the same time.

This is what I do
  1. I start with a guest that has dynamic resizing but not shared folders
  2. Install VirtualBoxGuestAdditions
  3. Now have shared folders but not dynamic resizing
  4. uninstall VirtualBoxGuestAdditions
  5. Now don't have shared folders or dynamic resizing


Though I said I can't get dynamic resizing and shared folders working at the same time I have managed it twice. Once with a completely new install of Slackware 14.2+ in a new guest and on another occasion on an existing install when I inadvertently accepted the new config files at the end of a slackpkg upgrade-all.

I'm wondering now whether this has anything to do with my X display set up. Specifically the existence or absence of /dev/dri/card0

I've done an sdiff of the Xorg.0.log from a guest that has dynamic resizing and the Xorg.0.log from a guest that doesn't have dynamic resizing. I've attached the results

In the attached file the left hand side I can get dynamic resizing but on the right side I can't.

In other words within the guest I seem to
  1. get dynamic resizing if /dev/dri/card0 exists.
  2. not get dynamic resizing if /dev/dri/card0 doesn't exist


I now need to understand what's happened to /dev/dri/card0 when I install VboxGuestAdditions.


Alex
Attached Thumbnails
Click image for larger version

Name:	Xorg-sdiff.jpg
Views:	4
Size:	214.1 KB
ID:	29471  
 
Old 01-15-2019, 06:28 AM   #24
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
From my previous posting

Quote:
I'm wondering now whether this has anything to do with my X display set up. Specifically the existence or absence of /dev/dri/card0

My grub.cfg file includes the nomodeset option in the linux boot line as seen from the screen shot contained in the attached file grub.jpg

If I edit the grub commands before booting by pressing 'e' at the grub screen then remove the nomodeset option and then boot I now get dynamic resizing. See attachment.

If I leave the nomodeset option as is I don't get dynamic resizing.

Need to understand why I've got nomodeset in this guest in the first place.

Alex
Attached Thumbnails
Click image for larger version

Name:	grub.jpg
Views:	4
Size:	60.3 KB
ID:	29472  
 
Old 01-15-2019, 09:42 AM   #25
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
In /etc/default/grub I changed the line

GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"

to

GRUB_CMDLINE_LINUX_DEFAULT=""

Remade my /boot/grub/grub.cfg by running grub-mkconfig

Result is that when I boot I get the dynamic resizing.

Ran the following in the guest

Code:
cd /usr/local/src
wget https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_6.0.1-127639.iso
mount VBoxGuestAdditions_6.0.1-127639.iso /mnt/cdrom/
cd /mnt/cdrom
./VBoxLinuxAdditions.run

vboxsf failed


Rebooted the guest and everything worked as expected get dynamic resizing and shared folders. Both at the same time. Good result.

When I first started with alienbob's ktown I had a problem with a black screen following a startx. See https://www.linuxquestions.org/quest...en-4175631078/

The solution was to introduce a nomodeset when starting linux.

Six months further down the line that problem's gone away and the introduction of the nomodeset has invoked a new problem of virtualbox being unable to dynamically resize.

Just to be clear I no longer using nomodeset to boot linux.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Can't compile virtualbox-addons with gcc 8.2.0 aikempshall Slackware 3 08-11-2018 04:26 AM
Does Deepin Desktop Environment support addons that can heavily modify the desktop environment? Joe232 Linux - Software 1 02-07-2018 08:43 AM
Can't download addons Firefox 2.0.04 Suse 10.2 vladi4az Linux - Newbie 1 06-15-2007 11:27 PM
ipcop addons rtr Linux - Security 1 12-10-2003 11:43 AM
RADIO / TV TUNER ADDONS Stephanie Linux - General 3 05-11-2001 01:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:37 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration