4.2.18 update issue

[Serg675Hockey]

I have updated to 4.2.18 recently and I can't run all my Ubuntu 64bit images anymore due to General Failure (see attachment). All images worked fine with 4.2.16 but not anymore. Is it fixable? I meant may be some settings have to be modified. By now I have downgraded back to 4.2.16 to resolve it. Host is Windows 7 64bit.

[mpack]

Please pick an affected VM and provide a VBox.log file (zipped). See the Logs subfolder of the VM.

[Serg675Hockey]

Please pick an affected VM and provide a VBox.log file (zipped). See the Logs subfolder of the VM.

Attached.

[Serg675Hockey]

The problem is with network adaptors. When I disable them then images run fine. I use bridged adapters and it was working fine with 4.2.16 and lower.

[Serg675Hockey]

Another broken thing is 3D acceleration. After update 4.2.18 it says that my system doesn't support 3D acceleration. It was perfectly fine with 4.2.16.

[Serg675Hockey]

The same thing with 4.3 update. It is sad to see that good product becomes sucks.

[Serg675Hockey]

I have tried 4.3.4. Same issues. Looks like I'm stuck with 4.2.16 forever.

[socratis]

- How do you install your different VBox versions? With administrative priviledges?
- Do you have any other VMs that boot successfully?
- Did you try to start a fresh VM with Ubuntu 12.04?
- Finally, can you provide a more recent VBox.log (preferably with 4.3.4)?

[Serg675Hockey]

- How do you install your different VBox versions? With administrative priviledges?
- Do you have any other VMs that boot successfully?
- Did you try to start a fresh VM with Ubuntu 12.04?
- Finally, can you provide a more recent VBox.log (preferably with 4.3.4)?

- Yes, I install it with admin privileges?
- None of VMs boots.
- Yes, the same issue with fresh VM
- Log attached

Starting from 4.2.18 any VM fails to boot if I use "Bridged Adapter" in network setting. According to log some DLL loading problem. But 4.2.16 works well in the same environment. I use NAT as work around for now. But I need my guest Linux to be accessible from network via dedicated IP.

[socratis]

Both logs contain a very suspicious line:

General failure - DON'T USE THIS!!!. (VERR_GENERAL_FAILURE)

I searched on the forums for "DON'T USE THIS!!!" and came up with two threads (51984 and 47508) that don't offer too much information regarding your problem. A similar bugtracker search for VERR_GENERAL_FAILURE did return 16 results, but I didn't have the time to look at them...

[Perryg]

Were the guests shut down before the upgrade or did you leave them in saved state?

[Serg675Hockey]

Were the guests shut down before the upgrade or did you leave them in saved state?

Of course it was shut down. But how does it matter? Even newly created VM has the same error. It can't boot even. The issue is not in the guest OS image. It is in VirtualBox software. It crashes for "bridged network" configuration. I have mentioned it above.

[Perryg]

It was a simple question in an attempt to help you with your problem. The log states that there is a problem with Bridged for sure, but this is more likely a side effect of the real issue. General failure - DON'T USE THIS!!!. (VERR_GENERAL_FAILURE) indicates a more sever issue than just the network adapter. But what do I know.