Issues with Oracle Virtual Box VM
Hi There,
I am facing problems with starting VirtualBox VM on MAC OS X EI Capitan (10.11.4). Followed the following instruction as per PVS quick guide in the course.
1. Downloaded the Pega Decision Management Essentials (7.13) exercise system.
2. Unzipped using keka software. folder contains 2 files one with vmdk and another with vbox extensions.
3. Downloaded VirtualBox. Tried both 5.0.10 and 5.0.16 versions.
4. Updated VirtualBox preferences as per PVS quick start guide.
5. Added VM by selecting vmdk file from un-zipped downloaded folder.
6. Tried with following network settings on VM.
a. setting Attached To with options
i. NAT
ii. Bridged Adapter
iii. Host-only Adapter.
b. for Adapter type in Advanced settings with options
i. Intel PRO/1000 MT Desktop (82540EM)
ii. Intel Pro/1000 T Server(82543GC)
iii. Intel Pro/1000 MT Server(82545EM)
iv. PCnet-FAST III (Am79C973)
Hi There,
I am facing problems with starting VirtualBox VM on MAC OS X EI Capitan (10.11.4). Followed the following instruction as per PVS quick guide in the course.
1. Downloaded the Pega Decision Management Essentials (7.13) exercise system.
2. Unzipped using keka software. folder contains 2 files one with vmdk and another with vbox extensions.
3. Downloaded VirtualBox. Tried both 5.0.10 and 5.0.16 versions.
4. Updated VirtualBox preferences as per PVS quick start guide.
5. Added VM by selecting vmdk file from un-zipped downloaded folder.
6. Tried with following network settings on VM.
a. setting Attached To with options
i. NAT
ii. Bridged Adapter
iii. Host-only Adapter.
b. for Adapter type in Advanced settings with options
i. Intel PRO/1000 MT Desktop (82540EM)
ii. Intel Pro/1000 T Server(82543GC)
iii. Intel Pro/1000 MT Server(82545EM)
iv. PCnet-FAST III (Am79C973)
for all the above combinations when I start the VM and it is showing following messages
waiting for network configuration....
waiting up to 60 more seconds for network configuration....
after some time showing Ubutu Command prompt with out IP address to log into PRPC system
I thought file was corrupted and tried to download again did the same with no luck.
Any help on this would be appriciated.
Regards
Pradeep
Hi Pradeep
As discussed on the call, the VM started after making the following changes:
1. Add the VM to the VirtualBox library
2. Go to the VM Settings > Network.
3. Set the following:
Adapter 1: Enable. Attached to NAT
Adapter 2: Enable. Attached to Host-only Adapter. (Name: vboxnet0)
4. Start the VM. This got you past the Waiting for Network issue. The VM started successfully and Tomcat started (verified from /usr/share/tomcat7/logs). However you were not able to reach either prpc.local or the IP address of the VM ( Proprietary information hidden) from the browser or ping from the terminal.
Then, the following steps were taken:
5. Go to VirtualBox > Preferences > Network > Host-only Networks.
6. Edit the vboxnet0 and change the following:
Adapter tab:
IPv4 Address: Proprietary information hidden
DHCP Server tab:
Server Address: Proprietary information hidden
Lower Address Bound: Proprietary information hidden
After this, you were able to ping Proprietary information hidden from the terminal.
Hi Pradeep
As discussed on the call, the VM started after making the following changes:
1. Add the VM to the VirtualBox library
2. Go to the VM Settings > Network.
3. Set the following:
Adapter 1: Enable. Attached to NAT
Adapter 2: Enable. Attached to Host-only Adapter. (Name: vboxnet0)
4. Start the VM. This got you past the Waiting for Network issue. The VM started successfully and Tomcat started (verified from /usr/share/tomcat7/logs). However you were not able to reach either prpc.local or the IP address of the VM ( Proprietary information hidden) from the browser or ping from the terminal.
Then, the following steps were taken:
5. Go to VirtualBox > Preferences > Network > Host-only Networks.
6. Edit the vboxnet0 and change the following:
Adapter tab:
IPv4 Address: Proprietary information hidden
DHCP Server tab:
Server Address: Proprietary information hidden
Lower Address Bound: Proprietary information hidden
After this, you were able to ping Proprietary information hidden from the terminal.
Please update the status once you restart the VM.
Regards
Guru