Page 1 of 5

Discuss the 6.0.0 release

PostPosted: 18. Dec 2018, 22:27
by michael
Discuss the 6.0.0 release here.
You can download the release here.
VirtualBox 6.0.0 is a new major release.

VirtualBox 6.0.14 has been released. Please try that before continuing the discussion in this thread.

Known new issues/regressions
These are new and confirmed tickets about issues with 6.0.0:

Re: Discuss the 6.0.0 release

PostPosted: 18. Dec 2018, 22:29
by JSquared71
Added support for using Hyper-V as the fallback execution core on Windows host, to avoid inability to run VMs at the price of reduced performance

Does this mean we can use VirtualBox fully on a computer with Hyper-V installed?

Re: Discuss the 6.0.0 release

PostPosted: 18. Dec 2018, 22:39
by rpmurray
MacOS Guest Additions: initial support

OhBoy, OhBoy, OhBoy. :lol:

Re: Discuss the 6.0.0 release

PostPosted: 19. Dec 2018, 01:30
by Henk717
I see that Nested Virtualization is added to this release, something i have been hoping for for quite some time.
On my Ryzen system i can not use Hyper-V for nested virtualization and this is a much desired feature to test out virtualization software or build entire labs including virtual hosts (For example to test fail over configuration in a test environment).

Unfortunately i am struggling to get this feature to work properly, Hyper-V can not be installed because SLAT support is missing from this feature, using Virtualbox inside of the guest crashes the VM instantly with maximum CPU usage.

I am also not getting any screen refreshes when using the software trough Remote Desktop with VBoxSVGA when the guest additions are installed.
This problem is not present when i revert to the VBoxVGA adapter which is what i now do by default for these guests, it may be limited to AMD GPU's.

It would be great if someone can help me get Hyper-V properly virtualized as this will be of great use for my upcoming microsoft exams.

Re: Discuss the 6.0.0 release

PostPosted: 19. Dec 2018, 02:25
by socratis
JSquared71 wrote:Does this mean we can use VirtualBox fully on a computer with Hyper-V installed?
In theory, yes. I haven't tried it (on OSX myself), but be aware of "at the price of reduced performance". I haven't seen any benchmarks, it's too early for that.

rpmurray wrote:
MacOS Guest Additions: initial support
OhBoy, OhBoy, OhBoy. :lol:
I know, right? It's a start! There's not that much yet, and I'm still trying to figure out which parts work and which are not. I had a thread opened in the "Beta" section of the forums: OSX GAs (VBoxDarwinAdditions.pkg): what to expect?. I'm going to lock that and open a new one in the "OSX Guests" section.

EDIT: I did something even better! I moved the thread, much simpler! It's not like I've been testing it for weeks and the info is outdated...

So far, only limited Copy/Paste and VBoxControl (from the guest) / VBoxManage guestcontrol (from the host) work. No Shared Folders, Drag'n'Drop or enhanced graphics. Still a really great start from nothing to something!

Henk717 wrote:Hyper-V can not be installed because SLAT support is missing from this feature
What are you trying to do? I would suggest starting with something simple, and then move to bigger and more complicated setups. Don't go straight for the Cray or the BigBlue one... ;)

A lot of problems with Ubuntu guest after upgrade to VirtualBox 6

PostPosted: 19. Dec 2018, 08:47
by Anakunda
Hello,
alot things broken in VBox6
- desktop shortcuts for VMs are invalid as still linking VirtualBox manager and not launcher
- Ubuntu guest - virtualbox addons instalation interrupted for missing packages to build kernel modules, but actually they are installed (make, gcc and perl)
- Ubuntu guest - network not working at all (including internet and shared folders accesibility)
Having bridged connection to host's physical ethernet adapter, firstly I noticed the network card was reset to paravirtualized network (reverted back to Intel) - still not working

I need some help how to fix, or wait for another VirtualBox update?

Re: A lot of problems with Ubuntu guest after upgrade to VirtualBox 6

PostPosted: 19. Dec 2018, 09:35
by socratis
Anakunda wrote:- desktop shortcuts for VMs are invalid as still linking VirtualBox manager and not launcher
Yes, that can happen. An update doesn't go though each and every shortcut on your desktop. You'll have to adjust them manually. Side-effect of a better security model...

Anakunda wrote:- Ubuntu guest - virtualbox addons instalation interrupted for missing packages to build kernel modules, but actually they are installed (make, gcc and perl)
"Ubuntu guest" is a really generic statement. You need to provide the exact distro version, the kernel, and the complete output of the building process.

Anakunda wrote:- Ubuntu guest - network not working at all (including internet and shared folders accesibility)
Again, versions and proof. Did you reboot the guest after the GAs installation?

Anakunda wrote:I need some help how to fix, or wait for another VirtualBox update?
It's up to you if you're going to wait for an update or not, but with the details given, and no ZIPPED VBox.log of a complete session that shows the problems, no help is going to come.

BTW, please remember that there's a sort of unwritten rule in the forums: 1 thread per issue, 1 issue per thread. The title "A lot of problems..." is going to be a candidate for every known problem in the known universe, not a good thing to have in a thread.

So, please open a new thread per problem, with an appropriate title. And since the title that you chose is bound to attract every problem withe those that upgraded, I'm going to have to lock the thread to prevent that. There is the "Discuss the 6.0.0 release" thread for such generic statements.

Actually, thinking about it, I'm not going to lock your thread, I'm going to merge it with the "Discuss the 6.0.0 release" one.

Re: Discuss the 6.0.0 release

PostPosted: 19. Dec 2018, 10:24
by Anakunda
So, the distro is 18.04.1 LTS
The kernel is 4.15.0-42-generic
Did you reboot the guest after the GAs installation?

Sure I did.

Btw. the issue seems solved after more reboots.

Re: Discuss the 6.0.0 release

PostPosted: 19. Dec 2018, 11:01
by socratis
Anakunda wrote:Btw. the issue seems solved after more reboots.

So, it's working now? All it needed was more than 1 reboots? Hey, I've always said, if your computer is troubling you, first step is always a reboot. Or two, or more in your case... ;)

Re: Discuss the 6.0.0 release

PostPosted: 19. Dec 2018, 20:12
by Tuta
Linux host (Slackware-current)
guests: Linux Mint, MX Linux, Slackware, CRUX, Windows 8.1

note all worked with VB-5.2.22

1) broken desktop shortcuts:
removed old shortcuts and created new ones:
- Oracle VM VirtualBox Manager
--Machine
--- Create Shortucut on Desktop

When clicked on shortucut, got the error:
--startvm is an option for the VirtualBox VM runner (VirtualBoxVM) application, not the VirtualBox Manager.

Sound:
garbled sound in debian based Linux Mint and MX Linux
no sound in Slackware guest
Sound works in Windows

None of the issues fixed by rebooting host and quests

Re: Discuss the 6.0.0 release

PostPosted: 19. Dec 2018, 23:27
by Tuta
well, also latest VirtualBox has slower disk access:
unpacking kernel stops few times before finishing.

Reverted to 5.2.22 and ALL is working (that is sound, desktop shortcuts, disk access) well again.

I guess typical issue with x.0 versions.
Will wait for 6.1 or something.

Thank you anyway, I really like VirtualBox.

Re: Discuss the 6.0.0 release

PostPosted: 20. Dec 2018, 11:35
by tonny
After upgrading to 6.0 restoring from saved state no longer works for one of my VMs - seems to be related to the lsilogicsas controller.
err.png
err.png (28.84 KiB) Viewed 11713 times


The VM was cleanly shut down before upgrade to 6.0 and also has the latest guest additions installed.
Host is Windows 10 1803
Guest is Windows 7

The only change on the host between the saved state and attempted restore is Windows applying KB4483234 overnight.
VBox log is attached.

LE: did a discard, saved state again and restore is still crashing, so it should be reproducible

Re: Discuss the 6.0.0 release

PostPosted: 20. Dec 2018, 12:05
by socratis
@tonny
Wait a minute, I'm confused...
tonny wrote:restoring from saved state no longer works
tonny wrote:The VM was cleanly shut down
Was the VM in saved-state, or completely shutdown? Can't be both, these two statements of yours are rather contradictory...

When upgrading VirtualBox, it's strongly (really strongly) suggested to shut down all the VMs. Not paused, not saved, completetly shut down from within the guest. Especially in major versions.

If you can't start the VM from a saved state, either discard the saved state, or downgrade to the last VirtualBox version, the one you saved the state with, shutdown the VM, then upgrade to the latest VirtualBox version.

Re: Discuss the 6.0.0 release

PostPosted: 20. Dec 2018, 12:13
by tonny
What I ment is that the saved state was done using 6.0, it was not carried over from 5.22, which I know is highly not recommended.

Re: Discuss the 6.0.0 release

PostPosted: 20. Dec 2018, 12:36
by tonny
I did some further testing with two other VMs (a Debian and a Windows 10).
Save state works ok for these (they are using a regular SATA controller), but as soon as I change their settings and add an additional SAS controller, booting and doing a save state, restore no longer works.

So it might be just as easy to reproduce, add an SAS controller to a VM and see if save state/restore still works.

Same problem also happens if I add an Lsilogic SCSI controller, but it works ok with a Buslogic SCSI controller.