virtualbox.org

Thank you all for testing and providing feedback. Please continue to use the test build (it's 4.3 + fixes backported and not bleeding edge trunk) until we release the next maintenance version which would contain this fix.

4.3.1 fixes the BSOD issue for me (with 6 virtual CPUs), but bridged networking is still causing network dropouts. With the VirtualBox Bridged Networking Driver disabled all seems OK though.

It looks like I am unable to install Guest Additions with this 4.3.1-90058 build. How would you recommend I tackle reinstalling a stable version @Ramshankar?

Error when installing:

Verifying archive integrity... All good.
Uncompressing VirtualBox 4.3.1 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 4.3.1 of VirtualBox Guest Additions...
Copying additional installer modules ...
add_symlink: link file /usr/lib/VBoxGuestAdditions already exists
add_symlink: link file /usr/share/VBoxGuestAdditions already exists
Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules ...done.
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used

Installing the Window System drivers
Installing X.Org Server 1.11 modules ...done.
Setting up the Window System to use the Guest Additions ...done.
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.

Installing graphics libraries and desktop services components ...fail!
(See the log file /var/log/vboxadd-install-x11.log for more information.)
Press Return to close this window...

In the log file...

VirtualBox  Guest Additions installation, Window System and desk‐
top setup install_x11_startup_app: no script given

Thanks for all your support!

aknutson wrote:It looks like I am unable to install Guest Additions with this 4.3.1-90058 build. How would you recommend I tackle reinstalling a stable version @Ramshankar?

In this case, I would recommend staying on whatever guest additions you have installed in your VM. There is no need to update to the one included in the test build, although it should work but I didn't test it. What does /var/log/vboxadd-install-x11.log have?

Thanks Ramshankar for the quick fix. Any idea when the maintenance version will come out - are we talking days, weeks, or months?

Steve Prior wrote:Thanks Ramshankar for the quick fix. Any idea when the maintenance version will come out - are we talking days, weeks, or months?

Since the other burning issue is the Net Filter stuff on Windows 8.1, we want put one out as soon as it gets fixed, as it's also a high-priority bug. I'm not the one working on it so I have no real ETA or progress on that fix but hopefully days/week not months.

I am experiencing the same error.

I disable I/O APIC for the machine and used for 3 hours with no crash.

Acceptable until more permanent fix found.

Host: Windows 8.1 Pro
Guest: ubuntu 13.10 (64bit)

Well..stumbled upon your thread and let me add my 3 cents:

1) Upgraded an AMD based machine last week to 8.1. I'm not at it right now so not 100% sure it was on the latest vbox. No problems.

2) Upgraded a Xeon machine last night (3 months old) and am getting the problem but what may be of most interest - not in virtualbox but in the Android AVD emulator.

Beezle wrote:Well..stumbled upon your thread and let me add my 3 cents:

1) Upgraded an AMD based machine last week to 8.1. I'm not at it right now so not 100% sure it was on the latest vbox. No problems.

2) Upgraded a Xeon machine last night (3 months old) and am getting the problem but what may be of most interest - not in virtualbox but in the Android AVD emulator.

This bug should not affect AMD systems, the bug is in our Intel VT-x code.

This bug should not affect AMD systems, the bug is in our Intel VT-x code.

Ok .. I guess good to know? I'll head on over to the Google Android forums as it would appear to be a similar problem wiht AVD as I've just crashed again in their emulator. No point then in running the x86-droid inside vbox at this time.

Tested on a Core i7-3632QM Socket 988B rPGA - ID1E59 SB Win 8.1 x64

Oracle Enterprise Linux x64 - booted from saved state, stable
-oracle db ran fine.

Linux Mint x64 - booted fresh, seemed stable

Windows XP x86 - Booted from saved state, Blue screened guest OS after sending acpi shutdown b/c of hang
-Booted from fresh, freezes at welcome
-disabling vt-x, dropping to one core and it booted.
-Re-enabled vt-x, seems stable. I will let it run awhile.

OpenBSD - booted fresh, seemed stable

Ubuntu x86 - booted fresh, seemed stable

Win Server 2008R2 - Booted fresh, seemed stable

All versions using bridged network, vt-x enabled
No crashes, issues, on the host during testing.
*before updating to the test build, host blue screened.

Draco wrote: Windows XP x86 - Booted from saved state, Blue screened guest OS after sending acpi shutdown b/c of hang
-Booted from fresh, freezes at welcome
-disabling vt-x, dropping to one core and it booted.
-Re-enabled vt-x, seems stable. I will let it run awhile.

Smells like https://www.virtualbox.org/ticket/12227 Should be fixed.

I receive the same exact CRITICAL_STRUCTURE_CORRUPTION on Windows Server 2012 R2 whenever I run Oracle VM Virtual Box. The machine never crashes unless I use this program. Is there an earlier version that doesn't crash all the time?

Dave Ryan

Ramshankar wrote: Smells like https://www.virtualbox.org/ticket/12227 Should be fixed.

That is exactly what happened on the XP VM. I was getting ready to simply blame it on the fact that it was XP too! Thanks for the heads up.

Hi,
I also upgrade windows 8.1 and fix the above errors.
Are all my snapshots before the upgrade still useful?
Thanks