MY VM DOES NOT SEEM TO HAVE A NETWORK ADAPTER, EVEN THOUGH IT IS CONNECTED TO A NETWORK.

For the following steps, you need to connect to your VM using the Cyclades connection guide . If your VM cannot be reached though the Internet, we suggest you use the console, as described in the above guide.

First, you need to check if your adapter is present but inactive. Try the following command if you have a Linux VM:

ifconfig -a

or this command if have a Windows VM:

ipconfig /all

These commands list the network interfaces of your VM, regardless of their state, and should include your new interface (e.g. eth1), provided that it is registered by your OS. If your interface is listed but inactive, then we suggest you read this Network Manager FAQ.

If your interface is not listed, then there are two possible causes for this behavior:

Case 1: Disabled hot-plugging in old (K)Ubuntu/Debian ~okeanos images

If you have an old (K)Ubuntu/Debian VM, i.e. a VM that was created before 31/08/2012, odds are that you may need to enable hot-plugging manually. Simply, run the following command:

sudo modprobe acpiphp pci_hotplug

and check again if your adapter has been registered. If yes, run the following commands to have hot-plugging always enabled:

echo acpiphp >> /etc/modules
echo pci_hotplug >> /etc/modules

Case 2: *BSD images do not support hot-plugging

Unfortunately, *BSD images do not have this feature and thus, it is essential to reboot your VM from the Cyclades UI. A reboot from inside the VM will not suffice, as explained in the reboot FAQ.

If neither of the above cases applies to your situation, please contact us to look more into your problem.

CYCLADES QUESTIONS

General

Connectivity

Custom images