Is there a fix for 4.3.20 yet?

[BasilRathbone]

None of my VM's* work under VirtualBox 4.3.18-96516 or 4.3.20-96997. They all abort shortly after startup (log files attached). All of these VM's work just fine under 4.3.16-95972 and everything coughs back to life when I re-install 4.3.16-95972.

Does Windows Vista Home Premium x64 have the same issue(s) that Windows 7 has?
Are the Nvidia drivers causing the issue?

I keep hoping for answers but none seem to be coming.

Host: Windows Vista Home Premium x64 SP 2 Patched.
Video: Nvidia GeForce GTX 460 v2 w/320.49 Driver
Anti-Virus: Microsoft Security Essentials
Firewall: Microsoft Windows Firewall

* Ubuntu 32, Linux Mint 32 Mate, Windows XP, Windows 7, Windows 10

[frank]

Does disabling 3D in the VM settings prevent your VMs from crashing?

[BasilRathbone]

Frank Mehnert - Oracle Corporation

Removing 3D didn't seem to change the outcome, Frank. VirtualBox 4.3.16 95972 is the last version of VirtualBox that works with my system. I don't know what's been broken but what ever it is is well broken.

Log files attached

[Perryg]

Code: Select all

00:00:02.849063 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_UNSUPPORTED_ARCH fImage=1 fProtect=0x0 fAccess=0x0 cHits=7 \Device\HarddiskVolume1\Program Files\WIDCOMM\Bluetooth Software\BtMmHook.dll
00:00:02.849308 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\WIDCOMM\Bluetooth Software\btmmhook.dll' (C:\Program Files\WIDCOMM\Bluetooth Software\btmmhook.dll): rcNt=0xc0000190

It looks like the offending software package is WIDCOMM bluetooth? Do you know if the dll is signed? Do you actually need/use it? I would try removing and see if it allows VirtualBox to work and report back.

[BasilRathbone]

I removed the WIDCOMM bluetooth as well as the 3D and no joy. Virtualbox still won't run my VM's. I remember adding the bluetooth adapter on Christmas day so I could check out some wireless headphones but the problems with my VM's started on November 24th when I tried to upgrade 4.3.16-95972 to 4.3.18-96516. I dropped back to 4.3.16 and waited for the next release, 4.3.20. Whatever is going on started back then.

Are the UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. events the problem. Someone is trying to resize the user interface frame buffer with invalid data?

All three log files are attached for all the versions I've run

[BasilRathbone]

I upgraded my host to Windows 7 Home Premium hoping that would help but it didn't. Log files are posted.

[geoffh]

I upgraded to 4.3.20 late in 2014 and since then many of my VMs have randomly aborted

I built a new VM this morning and am attaching the log files (VBox.log.3, VBox.log.2, VBox.log.1, VBox.log) as one log file
This VM aborted this morning

Here are the guest and host details:
VirtualBox V 4.3.20 96997
Guest Additions VirtualBox-4.3.20-96997-Win.exe installed
Extension pack Oracle_VM_VirtualBox_Extension_Pack-4.3.20-96996.vbox-extpack installed
Host
Windows 7 Enterprise Service Pack 1, 32Gb memory, 64 bit
Guest
RHEL Linux, 64 bit, 6Gb memory, 3D acceleration NOT enabled

I think I was running on 4.3.12 prior to the upgrade and don't recall any aborts
The aborts have only happened since I upgraded to 4.3.20
Any insight as to how to prevent this would be welcome

Thanks
Geoff

[geoffh]

Once again, one of my VMs has aborted - VirtualBox 4.3.20
I started the VM on arrival at work and used it until later in the day when I attended a meeting
On arrival at work this morning, the VM has aborted
The log is attached

[geoffh]

This morning I have 3 VMs in the 'Aborted' state - the picture shows 3 RHEL aborts (scroll down to the bottom)

[img]

VBox Manager showing aborted VMs

VMAborts150127.png (111.51 KiB) Viewed 2200 times

[/img]

I've looked through the logs for each one, but I have no idea what I'm looking for
I'm guessing that near the end would be something that would help indicate why I'm getting these regular aborts
The common log entries seems to be something along the lines

Code: Select all

10:43:40.778744 )AioMgr0-N: Request 0x0000000b41e150 failed with rc=VERR_UNRESOLVED_ERROR, migrating endpoint E:\VirtualBox VMs\Linux\RedHat\RHEL 64 VMs\RHEL Dev and Install VMs\RHEL V4 Inst VM2\Snapshots\{ddb6f647-09e1-45e4-9db6-71d3ce5e177f}.vdi to failsafe manager.
10:43:40.778889 AIO/win: Request 0x0000002554ced0 returned rc=VERR_UNRESOLVED_ERROR (native 1117
10:43:40.778891 )AIO/win: Request 0x0000000baa78d0 returned rc=VERR_UNRESOLVED_ERROR (native 1117
10:43:40.778904 )AHCI#0P0: Flush returned rc=VERR_UNRESOLVED_ERROR

Can anyone suggest what might be happening to cause the VMs to abort given the above lines seem to occur in each VM that aborts (very) close to the end of the log
Thanks for any help
Geoff

[mhanor]

geoffh, configure your VMs to use a SAS, a SCSI or an IDE controller. Some of your crashes might be related to a know bug with the SATA controller, see bug report 13105. As why your VMs are experiencing I/O delays/cancellations, it's another matter.