Question: How do I get CDK to work on the corporate laptop using virtualbox without running into the 'could not find mathcing ip for mac' issue?
environment: Windows7, CDK 3.2.0, Virtualbox 5.0.x/5.1.x various versions tried. Key callout, corporate machine has VPN software (cisco anyconnect) while home pc does not, home pc works fine. Issue happens regardless if using VPN or not. Virtualbox (all versions) proven to work using vagrant.
Key finding:
minishift ssh -> functions, doing an ifconfig returns eth0 with a 10.0.*
network, instead of the expected 192.168.99.* network segments configured
for virtualbox network host adapters. Explicitly using minishift config set
host-only-cidr 192.168.99.1/24 with matching virtualbox host adapters
doesn't change outcome
Details:
c:\devrh\cdk\bin>minishift version
minishift v1.7.0+204ce19 CDK v3.2.0-1
c:\devrh\cdk\bin>minishift start --vm-driver=virtualbox -- Starting local
OpenShift cluster using 'virtualbox'
hypervisor ... -- Starting Minishift VM ............................ FAIL
E1108 10:27:05.991687 3128 start.go:356] Error starting the VM: Error
configuring authorization on host: Could not find matching IP for MAC
address 0800279fa156. Retrying. Error starting
the VM: Error configuring authorization on host: Could not find matching IP
for MAC address 0800279fa156
corporate workstation has the issue, home PC does not.
Minishift delete and restart, same issue (different MAC address, but same issue).
Virtualbox remove all host adapters, minishift delete, restart (which auto-creates new host adapters), same issue.
Minishift --profile approach, same issue.
Uninstalled virtualbox, installed the version from the RHDevSuite installer with the CDK from the installer, all steps tested with that combination as well, same issue.
Additional notes, Virtualbox is working fine with vagrant (static IP’s in vagrant files), virtualbox/vagrant combo works on both corporate and home machine without issues.
Related
I'm doing some Ruby on Rails development on a WSL 2. The rails app connects to a MySQL server running on my Windows host. When I used WSL 1 it as easy to set the host to 127.0.0.1 but on WSL 2 I have to use the nameserver written in /etc/resolv.conf
But I found out that IP address written in resolv.conf changes on reboots.
Is there a way to set a static IP address for WSL 2 ?
You can consider ocroz/wsl2-boot (see INSTALL for installation instructions)
After running wsl-boot command:
The WSL network is configured as per its predefined definition always (Windows side),
All WSL hosts are configured with their predefined static IP always (Linux side),
All WSL hosts and connected Hyper-V VMs can talk to each other always,
The DNS resolution works however you are connected to Internet or VPN,
You can SSH to WSL host without any delay.
Dec. 2022, microsoft/WSL issue 4210 also adds:
With the latest Windows 11 (22621+), you can already specify the network adapter you want to use for WSL2 in .wslconfig:
[wsl2]
networkingMode=bridged
vmSwitch=my-switch
ipv6=true
So, now you can create a Hyper-V external virtual switch for WSL2 and fix the IP address, no other scripts are required. It works out-of-box.
The same thread adds:
Create a vSwitch in Hyper-V，I Use Hyper-V Gui to do this. Hyper-V has three types of virtual switches -- external, internal, and private.
I choose the "external" type , which is bridge type, the same as VMWare workstation.
set this config in .wslconfig
I find the IP change to the network of my home router，which is replace the old of eth0.
You can set DHCP in you home router, then Fix the IP of the bridge.
To sum up, in the case of bridge, it is essentially DHCP , and whether it is fixed or not depends on the DHCP server.
If you don't want /etc/hosts, /etc/resolv.conf to change after restart, you can create
/etc/wsl.conf
[network]
generateHosts = false
generateResolvConf = false
I'm trying to 'start' a minishift cluster on a remote machine (not the standard way on a virtualized machine). Both my machines (the control node and the target) reside in AWS, have access to internet but do not have public IP's. The installation passes through but in the end an error is printed:
'Error during post cluster up configuration: Unable to add sudoer role: The connection to the server 127.0.0.1:8443 was refused - did you specify the right host or port ?'
The start command is as follows:
minishift config set vm-driver generic
minishift start --remote-ipaddress 10.112.33.85 --remote-ssh-user root --remote-ssh-key path_to_key
I tested the installation with public IP's and it passed through without any problems. Does it mean that remote machine installation is not supported for non public IP's ? Firewalls on both machines are fully open, the machines can connect via ssh, control node runs RHEL 7, target Centos 7 (RHEL before, makes no difference). I tried the usual delete ~/.minishift and stuff, nothing works.
Remote machine installation works fine within a private network. The problem was in proxy configuration which is rather tedious.
I have downloaded Genymotion and installed it with Oracle Virtualbox 5.0.10 on Windows 10/64bit.
I keep getting the errors:
Virtualization engine not found.
Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.
I've tried uninstall/reinstall, deleted unused network adapters in device manager. I'm at loss.
Thank you all in advance for any help/idea.
You must go the VirtualMachine preferences under File in the menu. Then choose the Network setting, then Host-only Networks.
You can use the - button to delete all of the Ethernet Adapters that you have there.
Then create a new one and use the following settings:
IPv4 Address : 192.168.1.201
IPv4 network mask : 255.255.255.0
Then in the DHCP server tab:
Address: 192.168.1.100
mask: 255.255.255.0
Lower address: 192.168.1.101
Upper address : 192.168.1.199
Check to see which Ethernet adapter # you have now set up - this might be important later on.
Click OK for all the open boxes or save whatever you have.
Then try and run genyMotion again.
This worked for me.
There is one more thing you may have to do if this still doesnt work.
Go to Network and sharing centre . Change adapter settings and disable all the Ethernet connections EXCEPT for the Ethernet adapter you have just created.
I hope that helps
Daniel
For Ubuntu
Almost every GNU/Linux system comes with an installer package for Oracle VM VirtualBox.
Browse for the Oracle VM VirtualBox installer in your directories.
If you do not have the installer or if you need to install a specific version, download and install VirtualBox for Linux hosts from the Download VirtualBox page.
When installing VirtualBox, in the Custom setup window, make sure VirtualBox Networking is enabled.
Go to the Genymotion download page and download the Linux package corresponding to your system.
Run the following commands:
chmod +x <Genymotion installer path>/genymotion-<version>_<arch>.bin
cd <Genymotion installer path>
./genymotion-<version>_<arch>.bin -d <Genymotion installer path>
Run Genymotion using the following command:
cd <Genymotion installer path>
./genymotion
I am using Vagrant 1.1.2 on Mac OS X 10.7.5
I am running into an issue with the default networking setup. The network seems to be configured to use a DHCP server providing IPs from 10.0.2.? network, with the gateway being set to 10.0.2.2
Sadly, in the organization I work for, there actually exists a server at 10.0.2.2, which causes huge network communication delays.
How can I configure Vagrant's VirtualBox to use DHCP server providing IPs from a different network? The documentation at http://www.vagrantup.com/ completely ignores this issue, which unfortunately renders my Vagrant useless.
When I disconnect from the corporate network, Vagrant works as expected. So I am quite sure the issue is in the IP collision.
That's more a VirtualBox issue so should have to get Vagrant to set a VirtualBox option for a different DHCP subnet like so:
config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--natnet1", "192.168/16"]
end
everyone.
I try to configure network adapter of my freebsd on virtualbox machine. At first setting up, I got it right. However, after a couple of reboots, my VM gives me a error message: says "em1:Watchdog timeout -- resetting"
I tried to google it, and there is no solution that works for me.
The following is my network adapter of my VM:
Apapter1: NAT
Adapter2: Host-only Adapter vboxnet0
On my Virtualbox setting:
Host-only networks:
Adapter:
IPv4 address: 192.168.56.10
IPv4 network mask: 255.255.255.0
On my FreeBSD VM /etc/rc.conf
ifconfig_em0="DHCP"
ifconfig_em1="inet 192.168.56.11 netmask 255.255.255.0"
Moreover, strange thing is that,
for example, if timeout error message show at ttyv0 ,
when I log in at different ttyv[1-9], the error message will not be shown.
but in ttyv0, it still gives me the message.
And, in term of functionality of em1, it does work.
I have no clue about this problem. Hoping any one can give me a solution or suggestion.
That will be great! Thanks a lot.
Freebsd version: 9.0-RELEASE FreeBSD 9.0-RELEASE i386
Virtual box: 4.1.2 r73507
I have had the same problem in the past. It wasn't to do with FreeBSD it was an issue with the Virtualbox adapters supplied to the guest. FreeBSD is just showing you that there is an inconsistency between systems.
Initially I was using the Intel adapters in Virtualbox.
I simply changed the driver for each adapter under settings > network > adapter to "PCnet-PCI II". Then the networking was stable and consistent.