virtualbox.org

My virtualbox guests bridged networking broke after upgrading to v.5.0.8 and also simultaneously upgrading my OS from Win 7 to Win 10. I've rolled back both changes.

Vbox now back to 4.3.32 / OS back to Win 7.

I am getting this error when trying to open my guests. How to I recover?

Result Code:
VBOX_E_VM_ERROR (0x80BB0003)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Callee RC:
E_FAIL (0x80004005)

I would suggest reverting the changes in the VMs too, e.g. from a backup. Or, upgrade VirtualBox to the current version on the existing host OS and we'll see where we are from there.

I'm back to v.5.0.8 and I'm back to the beginning with the same networking problem. VM_A is fine, but on VM_B bridged networking does not work. I think the guest additions is also toast because I cannot view in full screen mode. In virtualbox settings, I am only seeing one of my physical LAN NICs under the drop down menu in "Networking".

Now all we need is a log for the non-functioning VM. Zipped please.

Here it is!

Ok, so the issue is bridged networking with an Ubuntu guest. I believe that issue has already been discussed quite a lot recently. See :-

https://www.google.com/search?hl=en&as_ ... hts=#cns=0

Only one of my two VMs has a problem.

Both are essentially the same, but may have different hotfixes applied. They are both running the same kernel:
Linux Mint 17 Qiana
Linux mint64lan 3.13.0-24-generic #47-Ubuntu


So what do I need to roll back to get things working as they were before?

Would it help if I provided logs from my working VM?

Update: I rolled back to v.4.3.30 and I can see all my physical NICs. Bridged networking is working on all my VMs again. Folks - This is a case of, if it ain't broke, don't fix it!!!