virtualbox.org

Now the file is loaded normal. The checksum matches.

I have no uploaded the package with a different name. Please check the download page, this package should be intact.

Solaris hosts: fixed a potential kernel panic caused due to unexpected preemption due to logging.

This was a major issue for me and appears to be fixed. Many, many thanks!

Installation of Virtualbox Guest Additions on Windows 8 64 (guest on Windows 8 64 host) results in the following error message: Details:

Hi,

Installed 4.2.18 r88780 today (upgraded from 4.2.16) and the Auto-Resize Guest Display no longer works:

Windows 7 Pro host
Windows 8 Pro guest

Stormwalker wrote:Hi,

Installed 4.2.18 r88780 today (upgraded from 4.2.16) and the Auto-Resize Guest Display no longer works:

Windows 7 Pro host
Windows 8 Pro guest

Did you also update the guest additions (in the guest)?

Hi Perry,

Yes - all installed and reporting as 4.2.18

Thanks

Think I've found it - the Enable 3D and 2D Display settings were not enabled - I've enabled them and restarted the VM and the Auto-resize Guest Display now works.

Hi everybody.

I found strange problem: when I mount random ISO to DVD drive, it's not shown as that disk. It is shown as disk which I mounted before last reboot. For example, if I mount Guest Additions (select "Install Guest Additions" from main menu) and then mount Windows 8 Installation DVD, I have to reboot (sometimes twice) before I can start Setup.exe.

Good afternoon.
Updated virtualbox v 4.2.18 r88780
run
vboxmanage startvm vxpro
take a snapshot
vboxmanage snapshot vxpro take snap1
0% ... 10% ... 20% ... 30% ... 40% ... 50% ... 60% ... 70% ... 80% ... 90% ... 100%
I try to delete the snapshot
vboxmanage snapshot vxpro delete snap1
0% ...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Snapshot operation failed
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: "int handleSnapshot (HandlerArg *)" at line 431 of file VBoxManageSnapshot.cpp
snapshot is not retired
turn off
vboxmanage controlvm vxpro acpipowerbutton
vboxmanage snapshot vxpro delete snap1
0% ... 10% ... 20% ... 30% ... 40% ... 50% ... 60% ... 70% ... 80% ... 90% ... 100%
passes

in version 4.2.16 everything runs smoothly

I get a blue screen crash in windows 8 64 bits host when connect an USB device to virtual machine. Get DRIVER_IRQL_NOT_LESS_OR_EQUAL(VBoxUSBMon.sys) error and host reboot. VirtualBox 4.2.18. All guests: Xp, Ubuntu, Windows 7, empty guest, ... . The problem is when connect usb in menu "Devices - USB Devices".
No trace in log. To get an example of log file, I create a new Virtual Machine with empty disk and turn it on (obviously I get a No bootable medium found error), then I conect to it a usb printer in "Devices - USB Devices" and I get a Windows blue screen crash and host reboot. The problema ocurs with all guests operating systems.

seinfe wrote:I get a blue screen crash in windows 8 64 bits host when connect an USB device to virtual machine. Get DRIVER_IRQL_NOT_LESS_OR_EQUAL(VBoxUSBMon.sys) error and host reboot. VirtualBox 4.2.18. All guests: Xp, Ubuntu, Windows 7, empty guest, ... . The problem is when connect usb in menu "Devices - USB Devices".
No trace in log. To get an example of log file, I create a new Virtual Machine with empty disk and turn it on (obviously I get a No bootable medium found error), then I conect to it a usb printer in "Devices - USB Devices" and I get a Windows blue screen crash and host reboot. The problema ocurs with all guests operating systems.

I'm seeing the same behavior. Connect any USB 2.0 (or 3.0 for that matter) device to any VM: host system freezes and then BSOD/coredump with DRIVER_IRQL_NOT_LESS_OR_EQUAL. Also running Win 8 x64 (AMD). Doesn't always report that it's in VBoxUSBMon.sys; I've had reports of USBXHCI.SYS, Npfs.SYS, and lvbflt64.sys as well. Worked fine with 4.2.16; haven't tried downgrading yet to see if the problem goes away. Update: Downgrading to 4.2.16 cures the problem (just making sure it wasn't anything else I did to the system in the interim).

Update 09/15/13
I uninstalled version 4.2.18 and reinstalled version 4.2.16 along with a downgrade of Guest Additions to version 4.2.16 and that resolved my USB printer BSOD issue. With 4.2.16 I can now enable and print from the XP guest running on a Windows 8 host without problems.

Reposted here by direction from PerryG in windows hosts forum...
Hello,
Host system is Windows 8 and guest system is Windows XP. Running current VirtualBox version 4.2.18 r88780 with same update Guest Additions. I use a Brother MFC220 USB printer on both host and guest systems which has been working fine until this latest new version of VB. When I want to print something from inside the guest, I disable the printer control software on the host and then right click on the USB devices VB icon and enable the printer on the guest. This has worked well since I started using VB. Today, when I went through that process as soon as I enabled the printer in VB, I got a BSOD on the host system with a message like "IRLQ not less than or equal vboxmanage.exe" with an automatic restart of the host system in just a few seconds. After the Windows 8 host restarted and I started the VB manager and clicked Start to reopen my Windows XP guest. The XP guest went through a CHKDSK routine before rebooting which indicates to me the XP system crashed too along with VB. After the XP guest restarted, I was able to transfer the document I want to print via the shared folder to the Windows 8 host and, after closing the guest system & VB manager program, print the document successfully from the host to the MFC220. Evidently, there is something in the 4.2.18 version of VB/guest additions that is causing this system crash. Any ideas on a fix? Thank you.
OmaSteak
PS - Since I was able to successfully restart the Guest, I didn't think a log file would capture what happened in the previous crash so no log file attached.

Auto guest resize does not work for me. Checked the size of the download, it seems OK.

Host: Windows 7 64-bit, 8GB
Guest: Windows 8.1 32-bit RTM.

Note that auto-resize was working in Windows 8.1 Preview using Virtualbox 4.2.16.

Enabling both 2D and 3D acceleration will cause the VM guest for me to crash (Windows 8.1 32-bit).