The exercise system doesn't start correctly in Oracle VM VirtualBox
I've downloaded the exercise system and unziped (using 7-zip). I've added to the latest release of VirtualBox - 5.1.16 r113841 (Qt5.6.2) - but it won't start correctly - get the message "Waiting for network configuration...". I have other VMs "installed", eg. Pega Marketing Enablement 7.13 ML9 which run fine. I've tried re-installing many times with different Network and operating system setups, but without success. Any ideas?
Pegasystems Inc.
US
There are two issues at play here and, as it happens, I am working this issue for another user of the Marketing VMs.
1. The device manager in Ubuntu (Udev - standard device manager for the Linux 2.6 kernel) is getting stuck and will not update the network config file w/ the current network adapter configuration on your pc (the host).
2. The Marketing VMs are configured differently. One seems to have a host-only network configuration, the other seems to have a NAT network configuration.
So, when you boot up one VM, Ubuntu tries to reconcile what Udev thinks it knows about the host network adapter, and what the host network adapter really is.
For now, the easiest solution is to boot up the VM, let the network setup fail, then login to the VM console w/ root / password. If "password" does not work as the password, try: install.
Then, enter the following commands:
rm -f /etc/udev/rules.d/70-persistent-net.rules
rm -f /lib/udev/write_net_rules
shutdown -r 0
You will need to do this each time you boot up a different VM. If you boot up say, VM one, then boot up VM one again, you will not have to rerun the commands. However, if you boot up VM one, the decide to boot up VM two, you will need to run the commands.
There are two issues at play here and, as it happens, I am working this issue for another user of the Marketing VMs.
1. The device manager in Ubuntu (Udev - standard device manager for the Linux 2.6 kernel) is getting stuck and will not update the network config file w/ the current network adapter configuration on your pc (the host).
2. The Marketing VMs are configured differently. One seems to have a host-only network configuration, the other seems to have a NAT network configuration.
So, when you boot up one VM, Ubuntu tries to reconcile what Udev thinks it knows about the host network adapter, and what the host network adapter really is.
For now, the easiest solution is to boot up the VM, let the network setup fail, then login to the VM console w/ root / password. If "password" does not work as the password, try: install.
Then, enter the following commands:
rm -f /etc/udev/rules.d/70-persistent-net.rules
rm -f /lib/udev/write_net_rules
shutdown -r 0
You will need to do this each time you boot up a different VM. If you boot up say, VM one, then boot up VM one again, you will not have to rerun the commands. However, if you boot up VM one, the decide to boot up VM two, you will need to run the commands.
The other, more long term solution, is to set the network adapter settings on the VM to the same: either both VMs use NAT, or both VMs use Host-only network configurations.
We are trying to get all VMs released to the public to use the same network configuration, so pardon our construction dust while we work that out ;)
if you need more help, please feel free to reach out to me at [email protected]
eddie