Hello Justin, On Wed, Apr 25, 2012 at 1:22 PM, Justin Cinkelj <justin.cink...@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@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org