when you mention: I’m not able to log in to them - you probably mean logging in with SSH, right ?
It sounds like you have not added a network to your setup, you can use the standard libvirt virbr0 network (192.168.122.1-254), that you probably already have, and make sure to define the IPs and network in opennebula (add virtual network).
But I could be completely misunderstanding you - hope this helps!
I had problems with Ubuntu14 KVM store. The solution to my case was export my SSH public key of my oneadmin user, the frontend machine, and after that I could log in without a password. After all, from what I understand this Store template (Ubuntu14 KVM) does not come with username and password … Good luck.
Hi Roland, thank for your response. Yes, I meant logging with ssh. I followed the quick tutorial of opennebula as I mentioned in the initial post. In part 3.2 of this tutorial(Adding virtual resources), I create a file called mynetwork.one, following the indications, but I changed the “leases” for my free ip address. Additionally I copy my ssh key, as they mentioned. Maybe you could indicate if the file mynetwork.one was created in a bad way, or you could indicate how to create this file successfully.
Hi cesar, I’m in the same situation. I export my ssh key too, but I think my network configuration is failing. If you have some recommendations or tutorials about how to configure my network correctly, I’d really appreciate it.
could you please post here a copy of the tab called “log” of a VM ? So just deploy a VM, then select it, and post the text of the tab called log. We should be able to tell what doesn/doesn’t get loaded, so we should be able to see if your VM gets a network or not.
If you can, please also log in as oneadmin to your host, and show the output of “onevnet list”,
and the the output of whatever number of networks you have, like “onevnet show 0/1/2”.
Using SSH key adding to VMs automatically is done using contextualization, for that you need the contextualization part configured correctly, that’s for later.
Hi. In time to configure your network the first thing is to configure the bridge properly. After this is set following their DHCP parameters. So must inform DNS, gateway, correct mask. I had problem with gateway because I had to set it manually because the default is end .1 and mine is .254. Remember to use a scope that is not being offered by DHCP. After setting all ping tests with to see if the communication is OK. Good job.
3.2. Adding virtual resources
Once it’s working you need to create a network, an image and a virtual machine template.
To create networks, we need to create first a network template file mynetwork.one that contains:
NAME = "private"
TYPE = FIXED
You should already have a default network created by libvirt, on interface virbr0.
You can use that to give IPs to your VMs, and it already has a NAT rule, so all VMs have access to internet.
In Sunstone, create a new network (click +) and use these details:
name: whateveryouwant
description: whateveryouwant
bridge: virbr0
network model: ebtables
filter mac spoofing: yes
filter IP spoofing: yes
vlan: no
ip start: 192.168.122.2
size: 252
This should give you a working network in opennebula, that you can use in your templates.
Since you are using a single machine anyway, this should work. If you get another node or server, dont use it this way.
What about contextualization?? In my template I encountered ssh and network contextualization boxes, both are checked. In ssh’s textbox, I put the public key of oneadmin user, but I still can’t connect to the machine.
UPDATE: Finally I can connect to my virtual machine via ssh, and VNC in sunstone, but the bad news is that I don’t have connection to Internet, I’m in the network, because I can connect with wathever machine in the network. Well I suppose I’ll deal with it, Thanks for your replies.
Furthermore, I installed the .deb package for contextualization in mi native host. Could you give some advice?
PD: I try to configure the network in the way you mentioned yesterday, but I don’t have all of the options that you mention and the configuration doesn’t work.
This should be installed in the virtual machines that you deploy, not on the hosts.
Setting up the virtual network, with the settings I posted earlier is done in Sunstone. Just go to
Infrastructure > virtual networks > click on the green + and use the settings I posted earlier.
Then deploy a VM, make sure you install the context .deb first and then adjust the template so it will get an IP/netmask/gateway from the virtual network.