I up the Centos image using VirtualBox ,clone image and convert it into Qcow2 format and tried up using Virt-manager. But i found interface not available in VM.
It displays
"Bringing up interface eth0: Device eth0 does not seems to be present,"
I also tried removing the presistance rules , chkconfig network on and rebooting VM.
But could not able to achieving the interface in VM.
Please advice me with any ideas.
This issue was due to NIC Device model ,
Base machine NIC driver was e1000 and VM it was set as rtl8139. Beacuse of which eth ports are not displayed.
Once i changed to correct e1000 driver. it works.
New learning. Things that can be added into checklist. :)
Related
I've created a virtualbox via docker-machine:
$ docker-machine create --driver virtualbox default
Within the Guest-OS I'd like to access my USB-Serial device, which is a Nordic nRF52840 DevKit, which is listed in macos as /dev/tty.usbmodem144241.
However, this device is not listed as USB device by virtualbox. I've also tried adding the devices as a Serial Port with the Port Mode "Host-Device" as described in this link, but without any success:
If I add the Serial Port as .tty-usbmodem the virtualbox will hang in 'Starting', I have to kill all virtualbox processes or disconnect the serial cable in order to start again. If I use .cu-usbmodem the virtualbox starts up but immediately crashes.
I'm running out of ideas here. I'm stuck at this issues since docker for mac does not support the --devices mapping without virtual machine, and for the virtual machine I somehow can't manage to add the port.
Any ideas on what else I could try?
So as it turns out virtualbox is quite picky about when a device is actually connected and does not work as seamlessly as I'm used from using VMWare:
The device I was using really just shows up as SEGGER J-Link in the USB menu
It must be added as filter (filter is really confusing > first I thought it would ignore the device)
The device cannot be added to the virtualbox 'on the fly' (using the USB-icon in the 'Show' window, see screenshot), it must not be connected before the virtualbox starts up.
The serial-tab is irrelevant > it's all handled via the USB tab.
The important fact is that the device must not be connected wenn the virtualbox fires up. So the steps to add a device are the following:
Power down the virtualbox
Make sure the USB controller is enabled
Connect the USB/serial device to the computer (host)
Add it to the filter in the virtual box
Now every time you want to use the device with the virtualbox:
Make sure the virtualbox is down (e.g. docker-machine stop default)
Disconnect the USB/serial device from the computer
Start up the virtualbox (e.g., docker-machine start default)
Virtualbox should now be able to "intercept" the device and list it under /dev, e.g., as /dev/ttyACM0
Un-/Plugging a filtered device once the box is up also works (you don't have to power down the virtualbox again if you forgot to disconnect the device before starting it up. Just wait for the box to be up, unplug, plug in, should be good).
I am building a sample vagrant box to install Jenkins and push it to atlas cloud.Please find below the steps that I followed.
Vagrant init ubuntu/trusty64
and the normal command to initialize the vagrant machine.
vagrant up
After this if i type command to ssh into the machine
vagrant ssh
It gives me error saying please increase timeout and so.
The main question is how can I ssh into the newly created vagrant machine.
To understand this, I have to go through all the basics. Please find below my findings.
Not attached
In this mode, VirtualBox reports to the guest that a network card is present, but that there is no connection -- as if no
Ethernet cable was plugged into the card. This way it is possible to "pull" the virtual Ethernet cable and disrupt the connection, which can be useful to inform a guest operating system that no network connection is available and enforce a reconfiguration.
Network Address Translation (NAT)
If all you want is to browse the Web, download files and view e-mail inside the guest, then this
default mode should be sufficient for you, and you can safely skip the rest of this section. Please note that there are certain limitations when using Windows file sharing (see Section 6.3.3, “NAT limitations” for details).
NAT Network
The NAT network is a new NAT flavour introduced in VirtualBox latest versions.
Bridged networking
This is for more advanced networking needs such as network simulations and running servers
in a guest. When enabled, VirtualBox connects to one of your installed network cards and exchanges network packets directly, circumventing your host operating system's network stack.
Internal networking
This can be used to create a different kind of software-based network which is visible to selected virtual machines, but not to applications running on the host or to the outside world.
Host-only networking
This can be used to create a network containing the host and a set of virtual machines, without the need for the host's physical network interface. Instead, a virtual network interface (similar to a loopback interface) is created on the host, providing connectivity among virtual machines and the host.
Generic networking
Rarely used modes share the same generic network interface, by allowing the user to select a driver which can be included with VirtualBox or be distributed in an extension pack.
At the moment there are potentially two available sub-modes:
UDP Tunnel
This can be used to interconnect virtual machines running on different hosts directly, easily and transparently, over existing network infrastructure.
VDE (Virtual Distributed Ethernet) networking
This option can be used to connect to a Virtual Distributed Ethernet switch on a Linux or a FreeBSD host. At the moment this needs compiling VirtualBox from sources, as the Oracle packages do not include it.
Out of these, only NAT and Host-only network is important.So, to solve this issue, I modified the predefined Vagrant file with the following code.
jenkins.vm.provider "virtualbox" do |vb|
jenkins.vm.network "private_network",ip:'192.168.56.5',:adapter => 2
jenkins.vm.hostname = 'jenkins.ci'
vb.name = "Jenkins"
end
Here, I have created a private network with static Ip and also, I specified the adapters count to use 2. The Private adapter is Host-only adapter and 1st adapter which is default one is NAT.
I'm not quit sure if I'm on the right site for this, but I'll give it a try. I have a couple of usb devices plugged in my Raspberry Pi model B. But when I plug in a WiFi dongle, it just shuts down all the other usb devices, and the dongle itself doesn't even work. Has anyone any idea what moght solve my problem? Thanks a lot!
I guess the problem is the amount of current that your Raspberry Pi is able to source. If you are not using a Hub it makes sense that when you connect your WiFi dongle the USB ports are disable to avoid getting to much current from your Raspberry Pi.
WiFi dongle consumes lot of USB power. You need external powered USB hub, or you can maximize the input current for your pi
Based on its documentation, Pi 2 can be powered up to 2A current
I had this problem too. It was easy to fix for me, but this may not help. This turned out to be a settings / driver error for me. If this does not work, you should try a different power source with a 2A current.
I have an answer for this. If you can run the command 'lsusb' okay, and it shows your wifi dongle is attached, you will need to edit your /etc/network/interfaces file.
First, find your ip and gateway settings
ifconfig
That should display your ip address. Write down the default gateway and this IP address.
Now, enter this into the command line:
Sudo nano /etc/network/interfaces
So, that has opened the interfaces file. Completely rewrite the file to the following (YOU SHOULD TAKE A PICTURE OF THE CURRENT FILE IN CASE THIS GOES WRONG):
auto lo
iface lo inet loopback
#auto eth0
#allow-hotplug eth0
#iface eth0 inet dhcp
allow hotplug wlan0
iface wlan0 inet static
address you_got_this_in_step_1
network 192.168.0.225 #Change this to your setting.
gateway default_gateway_from_step_1
dns-nameservers 8.8.8.8
wpa-ssid YOUR_NETWORK_SSID
wpa-psk YOUT_NETWORK_PASSKEY
allow-hotpug wlan1
iface wlan1 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
ctrl+x and save the file, yes on overwrite
sudo service networking restart
The pi should do some things and restart okay. If not, please set the file back to the original (should have screenshotted the file).
I also recommend that you do this locally and not through SSH.
Thanks for reading my answer and I hope it helps.
I have a AM335X ARM processor on a custom board. I am running angstrom linux 3.2.0 on it.
My build environment is a 64 bit laptop running Ubuntu 12.0.4.
I was hoping (I am a newbie), someone could explain what I need to do to configure the board (and host desktop) to run SSH over USB.
Any help would be greatly appreciated
It depends whether you have OTG port or not. If yes, you should configure it to emulate a network device. Connect your board to your laptop and you should see a new networking device (usb0 or something like this). Configure IP addresses for both host usb0 and one on your board and you're done having an extra IP subnet, where you can ping, SSH etc.
i have try many solutions in internet and all solutions does not work to me. i set the usb filter of usb setting in virtual box, but it keep to pop-up error for me.
Here is the errors:
Failed to attach the USB device Ralink 54M.USB....... [0001] to the virtual machine BT5.
USB device 'Ralink 54M.USB.......' with UUID {ID} is in use by someone else.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: HostUSBDevice
Interface: IHostUSBDevice
Callee: IConsole
can someone help me?
thank you for any suggestions.
Your extensions for Ralink are not allowing VirtualBox to attach to it. I found out that the Ralink wireless utility or the driver won't release it to the guest OS on VirtualBox. I deleted the kext (making sure I backed it up first) and rebooted. Now the VirtualBox guest OS (bt5 r3 in my case) sees it under lsusb after recompiling the driver for it, using modprobe rt5370sta, and blacklisting the other rt2x00 and rt2800.