Discuss the 4.2.18 release

[Techno.Scavenger]

Another retry....

Enable 2D Acceleration, re-installed guest additions now auto-size is working. Go figure.

[Techno.Scavenger]

Ok, got time again to play around with it.

It seems like that with default settings (no 3D/2D acceleration) I have to install guest additions *twice* and it works!!!

[miqim]

I have a problem with the auto capture mouse on windows guest.
after a time using out of windows 8 guest the mouse don't capture auto and i need to resized the screen of guest to get it work again.

my host is a Mac OS X 10.8.5
and my guest is a Windows 8 64Bits
how can i resolve this?

[frank]

Just replaced the 4.2.18 *el4, *el5 and .run packages on the server due to this bug.

[bluwing1]

(Originally posted in VB on Mac OSX hosts forum)

Failed to determine accessibility state of the medium

Postby bluwing1 » 17. Sep 2013, 19:25
Context:

Host: OSX 10.8.4, Vbox 4.2.18-8870 , guest: XP SP3

When attempting to create a linked clone of a Windows XP system, VirtualBox manager generated the following error:

Failed to determine the accessibility state of the medium .
Property 'Special/GUI/Hints' does not exist.
Callee RC: NS_ERROR_ABORT (0x80004004)

When OK was pressed, several more identical errors happened in quick succession. The VB manager window opened, but all information (supported VM type lists, existing VMs, etc.) were missing.

All subsequent attempts to run VB result in the same problem. Have tried deinstall (with script from VB package) and reinstall - no effect on problem.

?? Any idea what's missing? is this an OSX component that's died?

bluwing1

Posts: 1
Joined: 17. Sep 2013, 19:16

[idrozd]

Something was in the broken 4.2.18 as compared to 4.2.16:
Host - x64 Windows 7 sp1 (VirtualBox 4.2.18)
Guest - x32 Windows 8 pro (+VBoxGuestAdditions 4.2.18)

1. Problem with switching to full screen, if not activated enable 2D/3D
2. Problem when minimizing / maximizing windows to tray. When you deploy the contents of the screen is not
displayed. Once the screen, click on the VM - is redraw.
3. Broken network. Does not work through a proxy addon Xmarks Firefox (in virtualbox 4.2.16 - running).

Rolled back to 4.2.16...
Sorry.

[Amidamaru]

Something was in the broken 4.2.18 as compared to 4.2.16:
Host - x64 Windows 7 sp1 (VirtualBox 4.2.18)
Guest - x32 Windows 8 pro (+VBoxGuestAdditions 4.2.18)

1. Problems with switching to full screen, if not activated enable 2D/3D
2. Problem when minimizing / maximizing windows to tray. When you deploy the contents of the screen is not
displayed. Once the screen, click on the VM - is redraw.
3. Broken network. Does not work through a proxy addon Xmarks Firefox (in virtualbox 4.2.16 - running).

Rolled back to 4.2.16...
Sorry.

Same problem over here, host is a debian 7, and the guest flavors which are experiencing the issue are:

1. Win 8 64bit -> unable to full screen, blue screen image behaviour. Solution: Rolled back to 4.2.16.

2. Debian 7 -> unable to full screen, Solution: Rolled back to 4.2.16.

3. Windows XP SP3 -> unable to full screen, Solution: Rolled back to 4.2.16.

Enabling 2d / 3d acceleration ain't an option because the virtual machine would eating all the time 40-50% of my guest virtual processors power. I've lived that and I don't want to go trough once again.

Thanks.

[stimpy77]

I'm having a problem with the mouse integration failing after Windows times out and goes to the lock screen. The mouse no longer captures mouse-move events, but does capture click events. So when I'm away and I come back and alt-tab into the VM and see it black, and I mouse into it and click, revealing the lock screen and I am prompted for a password, if I move the mouse over the password field and click, the password field loses focus. If I right-click, a context menu appears way off to the right of the desktop, where my mouse was last known to be before it went off the screen and mouse integration gave the mouse back to the host. The only way I am able to get the mouse to function within the VM after this point is to either turn off mouse integration or reboot the VM. When the VM comes back up, the mouse works, until I come back to it and it has locked. Also, not only does the mouse not respond, the whole VM is super sluggish for a time.

I have a Windows 7 host and two Windows Server 2012 R2 (RTM) VMs, each separately installed (not copied), each with the guest tools installed, and each with 2D and 3D acceleration enabled. They both behave the same way.

[Tele]

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).

I got the same problem. BSOD/coredump with DRIVER_IRQL_NOT_LESS_OR_EQUAL , VBoxUSBMon.sys adjudged to be guilty. I run Linux Ubuntu x64 guest on Win7x64 host.
My 4.2.16 worked, and all versions before that, but not this new one. My problematic driver is a most common USB Mass Storage Device (an SD card reader) with a Microsoft driver (driver date 6/21/2006 ver:6.1.7601.17577)
If I unplug the MMC/SD reader, VBox works again, no BSOD anymore. Unfortunately I need that device, because I write SD cards on linux guest.
In this viewtopic.php?t=57410 topic, people have different USB devices, they worked in the previous 4.2.16 but not in 4.2.18 , that's a common symptom
Most probably the problem is in VBoxUSBMon.sys, I guess. What was changed in that driver ?

[MasterSenpai]

(Originally posted in VB on Mac OSX hosts forum)

Failed to determine accessibility state of the medium

Postby bluwing1 » 17. Sep 2013, 19:25
Context:

Host: OSX 10.8.4, Vbox 4.2.18-8870 , guest: XP SP3

When attempting to create a linked clone of a Windows XP system, VirtualBox manager generated the following error:

Failed to determine the accessibility state of the medium .
Property 'Special/GUI/Hints' does not exist.
Callee RC: NS_ERROR_ABORT (0x80004004)

When OK was pressed, several more identical errors happened in quick succession. The VB manager window opened, but all information (supported VM type lists, existing VMs, etc.) were missing.

All subsequent attempts to run VB result in the same problem. Have tried deinstall (with script from VB package) and reinstall - no effect on problem.

?? Any idea what's missing? is this an OSX component that's died?

bluwing1

Posts: 1
Joined: 17. Sep 2013, 19:16

I had been getting that error too except that I am trying to run it on Scientific Linux. I am trying to get the bottom of it. I was able to do a sudo on Virtualbox and it works, but when I use a different user account it happeneds. To me, it sounds like a permission issue or the program is having a difficult time reading the directory with certain privledges.

[Hong]

This is what I posted at Board index ‹ General ‹ VirtualBox on Windows Hosts

I have been suggested to post here. Here is the post:

Is VirtualBox 4.2.18 compatible with Windows 8?

I have only one Windows 8 machine, and I have installed VirtualBox 4.2.18 on it three times, and the machine could not start every time after the installation. At one time, I had resort to a hard drive image to revive the PC. For the other two times, I resorted to restore points of Windows recover the PC. This is a very time consuming test. I hesitate to do it again. I am wondering if anyone else with similar experiences.

VirtualBox 4.2.16 has been working fine.

[bluwing1]

Moved from VBox on OSX

Postby bluwing1 » 17. Sep 2013, 19:25
Context:

Context: OSX 10.8.4, Vbox 4.2.18-8870 , guest: XP SP3

When attempting to create a linked clone of a Windows XP system, VirtualBox manager generated the following error:

Failed to determine the accessibility state of the medium .
Property 'Special/GUI/Hints' does not exist.
Callee RC: NS_ERROR_ABORT (0x80004004)

When OK is pressed, several more identical errors happened in quick succession. The VB manager window opened, but all information (supported VM type lists, existing VMs, etc.) were missing.

All subsequent attempts to run VB result in the same problem. Have tried deinstall (with script from VB package) and reinstall - no effect on problem.

?? Any idea what's missing? is this an OSX component that's died?

[rousseauhk]

Is VirtualBox 4.2.18 compatible with Windows 8?

We've had dozens of installs on Windows 8 and no reported problems. Given the symptoms I wonder if you just have machine that is about to have a hardware (e.g. disk) failure?

[Hong]

VirtualBox 4.3 works fine on my machine running Windows 8.1 now. I do not know whether upgrading from Windows 8.0 to Windows 8.1 or upgrading VirtualBox from 4.2.18 to VirtualBox 4.3 has fixed the problem.