Virtualbox suddenly stopped working

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Mark Schumann
Posts: 2
Joined: 21. Dec 2015, 01:45
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Linux/Oracle
Location: Texas

Virtualbox suddenly stopped working

Post by Mark Schumann »

I have Windows 10 and first installed VirtualBox version 5.0.10 r104061 a couple weeks ago and installed PeopleSoft HCM, HCMDB-SES-854-14. It has been running flawlessly for about 2 weeks.

I received automatic Windows updates overnight, and since then PeopleSoft will no longer start on the VirtualBox. I get the errors below:

Could not start the machine HCMDB-SES-854-14_1 because the following physical network interfaces were not found:
VirtualBox Host-Only Ethernet Adapter (adapter 1)
You can either change the machine's network settings or stop the machine.

Failed to open a session for the virtual machine HCMDB-SES-854-14_1.
Nonexistent host networking interface, name 'VirtualBox Host-Only Ethernet Adapter' (VERR_INTERNAL_ERROR).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have tried changing the settings and was able to get what appeared to be a successful start up, but after that I cannot log in to the PeopleSoft HCM application, nor to Application Designer and cannot connect to the database using SQL Developer.

It appears that the settings for the Network tab for Adapter 1 are no longer valid. When I open that tab, there is a message at the bottom of the page "Invalid settings detected". The settings are:

Enable Network Adapter: checked
Attached to: Host-only Adapter
Name: Not selected (and no choices are available)
Advanced
Adapter Type: PCnet-FAST III (Am79C973)
Promiscuous Mode: Deny
MAC Address: xxxxxxxxxxxx
Cable Connected: checked
Attachments
VBox.log
VBox.log
(3.57 KiB) Downloaded 38 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Virtualbox suddenly stopped working

Post by socratis »

Uninstall 5.0.10 (don't worry, your VMs are going to be fine) and update to 5.0.12. See if that fixes it...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Mark Schumann
Posts: 2
Joined: 21. Dec 2015, 01:45
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Linux/Oracle
Location: Texas

Re: Virtualbox suddenly stopped working

Post by Mark Schumann »

Thanks for the suggestion to reinstall/upgrade the Virtualbox and that it would not affect my VMs. I had been considering that, but was concerned about losing my data.

In the meantime, I have gotten my PeopleSoft application to work again. These were the steps that fixed it:

1. For some unknown reason, my Virtualbox Network settings had become invalid. They were set to "Host-only Adapter", with the Name "Not selected", which causes an invalid condition. I don't recall if these were the original settings or if they somehow got changed by a software update. I changed this to "Bridged Adapter" with the Name "Intel(R) Dual Band Wireless-AC 3160", and this caused the invalid condition to go away.

2. I restarted the VM. This time, every process started, but I was still unable to access the web application, Application Designer or Oracle database (using Oracle SQL Developer).

3. On the VM, after all processes started, I logged into Unix as root, ran the ifconfig command to get the inet address and discovered that it had changed since the initial installation. I took the new inet address, updated my tnsnames for the database and updated the U R L used to access the web application. After this, everything was successful and back to normal.

The inet address had never changed since my initial installation and restarting the VM several times, so I assume that the change was related to the Network settings change.

My issue is resolved now, but if anyone can explain what might have caused this issue to happen in the first place,that would be good to know.
Post Reply