I have the same installed and I can finally get to my calendar/contacts.I have Palm Desktop and Companionlink in a Win7 VM as I’ve never been able to find a native solution.
Oh… and the software to calculate ingredient amounts to mix my e-juice, too.
The ultimate test for me to see If VB is working is installing Void OS, try it.
I can confirm, Virtual box 6.1.14 is working perfectly on KDE.
Me too…so far!
It fails for me when entering guest ISO
What do you mean when entering guest ISO?
When I apply guest additions.
en where is the guest additions installed? on the host or the guest…
guest-iso need to installed on the host if you install like win10 and has no guest, you can choose from dropout menu thats why guest-iso must be installed, but in a linux situation, you just need guest-dkms and guest-utils on guest system…as vbox extions idk… mine side mostly auto updated…
Maybe that is what he is talking about? I see here on mine this is what shows but i have no problem running virtual box now since the update.
Edit: This has no effect on my ability to use virtualbox.
that is exactly the error I get. I cant go fullscreen because of this.
Okay… so just a few things on virtual box. I’m not sure what you have installed on it and also is virtualbox installed on Linux?
So the settings are important here when you install a vm. When you are setting up a new vm and installing it in the settings tab set 128 MB video memory, graphics controller set VBoxSVGA, and set acceleration check Enable 3D Acceleration box. When you have set all these settings before you start the vm then make sure also in the main window under display that the Graphics Controller is set to VBoxSVGA otherwise click on it and set the box to that also.
These settings will stay once the vm has been launched once as long as you don’t change any settings. Once the vm is installed and you shut it down to boot into the installed vm i always go back into settings, system and remove the check mark from the optical device under boot order. I do that as a habit so that it doesn’t try to launch the vm on the ISO when you start it. Then when you are in settings make sure the Graphics Controller stays set to VBoxSVGA and then when you go to launch the vm from the main window also check it there again & set it because when you go into settings or anywhere else it usually reverts to the default settings. Once you have completed an install all this the settings will stay if you don’t go into anything. Otherwise you have to check.
Also when installing a vm what i do automatically is when you start the ISO i automatically maximize the window and then when it boots on the ISO i click on view in virtualbox at the top left and set virtual screen 1 to the resolution of my monitor. I do that as soon as it’s readily available when booting the ISO and then when the ISO is fully booted it will automatically go to full screen. This is the way i use it and you can also set Full Full screen by clicking on view full screen mode after it’s installed which will cover 100% of the screen so the vm will cover your task bar at the bottom. Then you can minimize and maximize back and forth between host and guest. I have no issues with virtualbox normally. It has only been lately that it became unusable because of freezing trying to install Arch distros. Now with all the updated packages it’s fine for me.
I did all that. I don’t use Windows, the VM is installed on Endeavour. I havent tried maximizing the window during installation, but I tried xrandr -s 1920x1080 and it says this resolution is not supported.
Both settings have to be set to VBoxSVGA and 3D Acceleration set when you launch the vm. Like i say it always reverts back to defaults if you go into anything. It’s just a quirk of Virtualbox. I find the odd anomoly with some distros as far as setting the size but this is the way i do it and it works well 99.9% of the time.
Is your monitor currently set to 1920x1080?
Thanks, I’ll give it another go.
Yes, full HD
It should work fine if you follow this. Try installing another vm and see doing it this way. You have to be quick on getting it maximized and setting the view in Virtualbox to set the virtual screen resolution to your monitor size before it gets booted all the way on the ISO.
Edit: The virtual Screen size is greyed out but becomes available as the ISO boots so watch for it.
Yes, I’ll delete the VM I have and make a new one.
Didn’t read the whole thread, sorry if I say something that was already said.
But the package virtualbox-guest-iso, if needed at all, should be installed in the host system. Then host can provide virtualbox guest additions to a VM, e.g. Windows, or perhaps some non-arch distro. If the VM distro is Arch based, then you don’t need to install package virtualbox-guest-iso anywhere.
Thanks @manuel i thought maybe that what he was referring to and honestly i never really bother much with the guest ISO. Didn’t know that. I just use it. 