virtualbox.org

Discuss the 5.1.16 release here.
You can download the release here.

Trying to install using the -msiparams NETWORKTYPE=NDIS5 switch and getting the following error: Edit: Using Cmd run as Administrator as well.

Why are you installing NDIS5 drivers on Windows 7?

aleksey-vb wrote:Why are you installing NDIS5 drivers on Windows 7?

Because every time I don't, I receive the following error and am unable to boot any VM's unless I remove the Host-Only Adapter:

Could you install VirtualBox with NDIS6 drivers and then run 'VBoxBugReport <failing_vm_name>' and mail the resulting archive to aleksey dot ilyushin at oracle dot com? This is most likely a configuration issue and the information collected by VBoxBugReport may help me to establish the cause.

FWIW, I updated to 5.1.16 and new guest additions, after shutting down the VM, and experienced almost immediate crashes after putting the processor under load. Happened twice so I rolled back to 5.1.14 and everything was fine. I don't have logs since I didn't see anything posted in here about it at the time and needed to get back to work. I used 5.1.14 for weeks with a single app without a crash, 5.1.16 didn't last 2 minutes. Something is wrong with this build, no matter the state at update.

* had version .6, meant .16

I upgraded to 5.1.16 today (to update all my Vagrant boxes—that worked out okay), but noticed that my Drupal builds inside VirtualBox were suddenly 10x slower (or worse!).

I use NFS for my boxes, and it looks like something in the 5.1.16 build has broken the ability to use NFS shares. If I use Vagrant's rsync option, it's blazing fast (just like before), if I use NFS, then it seems that the mount is invisibly switched to a vboxsf mount in the background at some point.

I've confirmed by deleting all my VMs, reinstalling 5.1.14 (no problems), then deleting VMs, reinstalling 5.1.16 (problems), and then going back again.

I haven't tested on windows with SMB yet, just NFS on a macOS host.

Also reported findings here: (drupal vm issue queue) and here: (vagrant issue queue)

(I'm not allowed to post links yet

I've updated to 5.1.16 today and my guest Windows 2008 R2 falls into BSOD 0x0000005a on booting: ACPI BIOS in the system is not fully compliant with the ACPI specification.
Host: FreeBSD 10.3 Release
Rolled back to 5.1.14 - all goes fine again.
Does anybody else meets with ACPI compliant problems with this new version?

Added:
Another test system was updated successfully.
It's funny...

ferndave wrote:I used 5.1.4 for weeks with a single app without a crash, 5.1.6 didn't last 2 minutes. Something is wrong with this build, no matter the state at update.

That may have been so for 5.1.6 (I haven't seen that), but the latest release is 5.1.16. Have you tried that?

Yeah, my mistake, I mean the latest, 5.1.16. I'll change my post to reflect it.

I'm also facing carsh issues after upgrading to 5.1.16 . Can someone help me with steps for downgrading to 5.1.14?

Shut down the VM and download the lower version and installing it will work?

Here I'm attaching the log file for experts who can deep dive into it

I moved ferndave's and prad007's posts from Crashes with Version 5.1.16 r113841 (Qt5.6.2). That thread had to do with crashing while restoring a saved state and the two other posts didn't.

@everyone
Please do not forget to provide any related logs and/or simple testcases.

@prad007
Your crash happens about 5 hours after running the VM. Do you get any error messages or the VM simply vanishes? What are you doing in the time of the crash in the guest and/or in the host?

I also noticed that you have your Guest Additions (GAs) CD inserted, but you're still running the old GAs version:

00:00:11.060391 VMMDev: Guest Additions information report: Version 5.1.10 r112026 '5.1.10'

You should update them to the current VirtualBox version. And don't forget to remove the CD after you're done with the installation, or you're going to have problems in the next update.

Also,

00:00:01.608163   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:01.730467 CPUM: Logical host processors: 4 present, 4 max, 4 online, online mask: 000000000000000f
00:00:01.730472 CPUM: Physical host cores: 2

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors, not logical ones. See: CPU Cores versus threads.

00:00:01.608589   VRamSize         <integer> = 0x0000000002000000 (33 554 432, 32 MB)

You should increase the vRAM size under the Display, especially if you're going full screen (which you are). Also you should consider enabling 2D and 3D acceleration, it would definitely help you.

Please take a look at: "VirtualBox 5.1.16 problem with UNC paths as shared folders ?" and the related re-opened ticket #14651: Shared folders with long path are not mounted properly.

I am running Solaris 11.3 as a host, and Win7 Enterprise as a VM. With this release I notice sound regressions. The sound stutters a bit every now and then. Version 5.1.10 was fine, the sound played smoothly. Now the sound plays smoothly, and then it stutters, and then smoothly, etc.