[one-users] ping between VMs on different hosts ?

[Jaime Melis]

Hello Valerio,

I think you have correctly configured the network. If you can't ssh into
it's because there's something wrong with the contextualization.

As Justin said, when preparing images the best way to go is to access the
VM through VNC, until the contextualization works.

Regarding your question about network restrictions, consider that in the
setup you have right now the VMs are taking real IPs from your network, as
if they were physical hosts. So all the conventional restrictions do apply:
you can't assign the same IP to two different VMs.

However, that's what network drivers are for: isolation. I suggest you use
either open vSwitch or 802.1q:
http://opennebula.org/documentation:rel3.4:nm

If you enable either of those two options you will be able to use the same
IP for different VMs.

cheers,
Jaime

On Wed, Apr 25, 2012 at 3:12 PM, Valerio Schiavoni <
valerio.schiavoni at gmail.com> wrote:

> Hello Justin,
>
> On Wed, Apr 25, 2012 at 1:22 PM, Justin Cinkelj <justin.cinkelj at xlab.si>wrote:
>
>>  Hi
>> Can you connect to the kvm virtual console with virtviewer (e.g., not
>> with sunstone)?
>>
>
> Yes, I managed to connect to the KVM virtual console with virtviewer.
> From the controller machine, I did:
>
> virt-viewer -c qemu+ssh://newcluster-0/system one-55
>
>
> Doing so, I discovered which IP the VM was assigned (for some reasons,
> 192.168.0.110/16) and I could ssh into it from the host.
> The VM was configured to execute the vmcontext.sh script, but apparently
> this is not working correctly. The content of /etc/network/interfaces gets
> modified correctly, as I see there:
>
> auto eth0
> iface eth0 inet static
>   address 10.0.0.1
>   network 10.0.0.0
>   netmask 255.255.255.0
>   gateway 10.0.0.1
>
> (originally, it  is dhcp). NEvertheless, once the VM initializes its
> networking services, it sets eth0 to:
>
> $ifconfig
> eth0      Link encap:Ethernet  HWaddr 02:00:0a:00:00:01
>           inet addr:192.168.0.110  Bcast:192.168.255.255  Mask:255.255.0.0
>           inet6 addr: fe80::aff:fe00:1/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:585 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1389 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>           RX bytes:49880 (49.8 KB)  TX bytes:117184 (117.1 KB)
>           Interrupt:10 Base address:0xe000
>
>
>
> To avoid further confusions due to my questions, I'd like to ask if there
> are 'restrictions' to respect when creating Virtual Networks.
> Do the addresses must be in the same class as the bridged interface ?
>
> Thanks a lot for your support!
>
> valerio
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>


-- 
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org | jmelis at opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120425/24342e1a/attachment-0003.htm>