IN WHICH CASE WOULD I NEED TO CONNECT TO MY VM THROUGH THE CONSOLE?
Connecting to a Virtual Machine through the console does not provide the optimal experience to the user. However, it is useful for troubleshooting and resolving issues regarding the proper function of the VM. Through the console, you are able to see useful information while the VM is loading the operating system (just like sitting in front of a VGA panel connected to the VM).
- Can I modify the technical specifications of an already created VM?
- How can I recover my data from a VM that has been destroyed? Is there any way to restore my VM back to its previous state?
- If I disconnect from my account, do my Virtual Machines stop working?
- Why does my VM's image show up as "Deleted" in its details?
- Why was my VM deleted?
- What is the username and password of my VM?
- Can I change the provided domain name of my VM?
- How can I connect to the Windows/Linux VM that I have created?
- How can I access all my VMs using one public IP?
- Why X2Go does not work when trying to connect to my VM?
- Why X2Go does not work on MacOS X?
- Is there a way of creating a local network using my Virtual Machines?
- Is it possible to create a local network between Virtual Machines that have been created by different users?
- In which case would I need to connect to my VM through the console?
- My Windows machine is "Running" but I cannot connect to it.
- My VM does not seem to have a network adapter, even though it is connected to a network.
- My VM does not have a floating IP, even though Cyclades report so.
- My VM does not work properly with IPv6.
- I'm getting confused about IPv4/IPv6, floating IPs and hot-plugging. Can you provide a simple explanation for all these?
- Can I shutdown/reboot my VM internally?
- Why is port X closed? Is it blocked by design?
- How can I add my public SSH key in an existing VM?