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
Accepted Solution
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
Hello Pradeep
First of all, I really like the way you have described all the steps that you have followed and the issue you are facing; it really helps when providing assistance.
I have a Mac running OS X Yosemite 10.10.5 and VirtualBox 5.0.10. However, I really do not think the versions matter here.
In addition to the instructions provided in the PVS Quick Start Guide, for Mac, you will need these settings:
Launch VirtualBox and remove the Pega Marketing/Decisioning virtual machine from the library. You can it again later (this is not absolutely necessary, but just a cleaner approach).
1. Go to VirtualBox -> Preferences (in the Mac top menu bar)
2. Go to Network tab.
3. Add a NAT Network under the NAT Networks tab (just click the + button on the right). It will be named NatNetwork by default.
4. Verify that there is a vboxnet0 network under the Host-only Networks tab. Edit and examine the settings. For your reference, my settings are as follows:
Adapter Tab:
IPv4 Address: Proprietary information hidden
IPv4 Network Mask: Proprietary information hidden
IPv6 Address: blank
IPv6 Network Mask Length: 0
Hello Pradeep
First of all, I really like the way you have described all the steps that you have followed and the issue you are facing; it really helps when providing assistance.
I have a Mac running OS X Yosemite 10.10.5 and VirtualBox 5.0.10. However, I really do not think the versions matter here.
In addition to the instructions provided in the PVS Quick Start Guide, for Mac, you will need these settings:
Launch VirtualBox and remove the Pega Marketing/Decisioning virtual machine from the library. You can it again later (this is not absolutely necessary, but just a cleaner approach).
1. Go to VirtualBox -> Preferences (in the Mac top menu bar)
2. Go to Network tab.
3. Add a NAT Network under the NAT Networks tab (just click the + button on the right). It will be named NatNetwork by default.
4. Verify that there is a vboxnet0 network under the Host-only Networks tab. Edit and examine the settings. For your reference, my settings are as follows:
Adapter Tab:
IPv4 Address: Proprietary information hidden
IPv4 Network Mask: Proprietary information hidden
IPv6 Address: blank
IPv6 Network Mask Length: 0
DHCP Server
Enable Server: Checked
Server Address: Proprietary information hidden
Server Mask: Proprietary information hidden
Lower Address Bound: Proprietary information hidden00
Upper Address Bound: Proprietary information hidden49
5. Save and exit from the preferences.
6. Now, add the virtual machine back.
7. Go to Settings > Network. If you have made any changes here, revert them to the way it was when you downloaded the VM. If you do not remember what changes you made, it’s best that you discard the VM, un-compress the VM afresh and add it to the library. Ideally, you will not need to make any changes to the network settings at the VM level.
Start the VM and let us know how it goes.
Good luck!
Regards
Guru
Accepted Solution
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
Thank you so much for the help Guru. I just verified at home and able to access the URL: http://prpc.local:8080/prweb/PRServlet. It was due to firewall at client location that blocked the access.
I would like to also thanks Eddie Moczygemba who helped me offline initially.
Hello Guru,
I am having similar issue where the VM image and/or the VirtualBox network settings are not correctly configured. Can you please help?
I have tried following all of the steps outlined in this forum topic.
I will attach my configuration screens below as attachments.
Please let me know what I need to change on my configuration in order to get this exercise system up and running. I can do a screen share if you have time.
Nilesh Jariwala
Hi,
I have Oracle Virtusa Box installed on my computer and is working fine. But after i keep the system idle for long time, then the pega server is not reachable. i will have do stop the virtual box and start it again.
is there any setting that i need enable to access pega server after my laptop wakes up/after a long period that i access pega server?
Shiva,
Thanks a lot for your post.
Please be aware that the Pega Decision Management Essentials course comes with it's own downloadable exercise system. You can download it from the Downloading the Exercise System lesson.
Marco.