[one-users] Can't connect to "running" vm's
Tino Vazquez
tinova at fdi.ucm.es
Mon Aug 24 08:31:14 PDT 2009
Hi Romaine,
Sure, you will need to configure your router in the same network as
the VMs, set it to do NAT and point the gateway of the VMs to said
router.
Hope it helps,
-Tino
--
Constantino Vázquez, Grid Technology Engineer/Researcher:
http://www.dsa-research.org/tinova
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
On Mon, Aug 24, 2009 at 4:36 PM, Romaine Martin<romeyro at gmail.com> wrote:
> Thanks so much! I got the linux vm running, and by disabling DCHP on
> the Windows vm and giving it the IP from my vnet template, I can now
> connect to it with remote desktop! I only have one last question:
> since I changed the settings and can now connect to both vm's (from
> within the network) now neither vm will connect to the internet. Is
> this likely an issue with the router configuration? Thanks again for
> everything guys, sorry to ask so many questions.
>
>
> On Mon, Aug 24, 2009 at 5:54 AM, Tino Vazquez<tinova at fdi.ucm.es> wrote:
>> Hi Romaine,
>>
>> From what I gather, it seems that your problem is getting the
>> vmcontext.sh script _inside_ your VMs. We only provide it for Un*x
>> machines, so you will need to figure out an equivalent for Windows
>> machines.
>>
>> How to do so is explained in the last section of [1], but in a
>> nutshell you need to
>>
>> * Copy the script$ONE_LOCATION/share/scripts/vmcontext.sh into the
>> /etc/init.d directory in the VM root file system.
>>
>> * Execute the script at boot time before starting any network
>> service, usually runlevel 2 should work:
>>
>> $ ln /etc/init.d/vmcontext.sh /etc/rc2.d/S01vmcontext.sh
>>
>> This script will set the IP from the MAC address of the VM.
>>
>> Hope it helps,
>>
>> -Tino
>>
>> [1] http://opennebula.org/doku.php?id=documentation:rel1.4:vgg
>> --
>> Constantino Vázquez, Grid Technology Engineer/Researcher:
>> http://www.dsa-research.org/tinova
>> DSA Research Group: http://dsa-research.org
>> Globus GridWay Metascheduler: http://www.GridWay.org
>> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>>
>>
>> On Fri, Aug 21, 2009 at 4:15 PM, Romaine Martin <romeyro at gmail.com> wrote:
>>>
>>> Hi Tino,
>>> I must admit, I don't know much at all about setting up the
>>> bridges/virtual network and how that works. I pretty much just used
>>> what was shown in this tutorial
>>> (https://help.ubuntu.com/9.04/serverguide/C/opennebula.html). I'll
>>> paste my virtual network template below. As far as I know, the vm's
>>> are not set to get their IP from the MAC address. So far I've been
>>> trying to ping the IP that it says is assigned to the vm, but this
>>> doesn't work.
>>>
>>> vnet03.template:
>>> NAME = "LAN"
>>> TYPE = FIXED
>>> BRIDGE = br0
>>> LEASES = [IP=192.168.10.112]
>>>
>>> (my home network assigns IP's from 192.168.10.XXX)
>>>
>>>
>>> On Fri, Aug 21, 2009 at 5:56 AM, Tino Vazquez<tinova at fdi.ucm.es> wrote:
>>> > Hi Romaine,
>>> >
>>> > Before we get ourselves down to other possibilities, have you configured
>>> > your VMs to set their IP addresses based on their MAC addresses? I am asking
>>> > this because we provide a script to do so at boot time in Un*x machines
>>> > (vmcontext.sh, take a look at the last section of [1]), but not for Windows
>>> > machines.
>>> >
>>> > Best regards,
>>> >
>>> > -Tino
>>> >
>>> > [1] http://opennebula.org/doku.php?id=documentation:rel1.4:vgg
>>> >
>>> > --
>>> > Constantino Vázquez, Grid Technology Engineer/Researcher:
>>> > http://www.dsa-research.org/tinova
>>> > DSA Research Group: http://dsa-research.org
>>> > Globus GridWay Metascheduler: http://www.GridWay.org
>>> > OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>>> >
>>> >
>>> > On Thu, Aug 20, 2009 at 6:18 PM, Romaine Martin <romeyro at gmail.com> wrote:
>>> >>
>>> >> Hey, so I've gotten my Windows XP and Ububtu vm's to show up as
>>> >> "running" finally, but I cannot ssh or even ping them. Is this a
>>> >> problem with the network setup, or the templates, or perhaps even the
>>> >> disk images? I have them running on Ubuntu boxes with KVM as the
>>> >> virtualizer. Both images boot correctly with kvm on the local machine.
>>> >> Thanks in advance for looking at this stuff, you guys are awesome.
>>> >>
>>> >> root at tsi1-desktop:/# onevm list
>>> >> ID NAME STAT CPU MEM HOSTNAME TIME
>>> >> 5 winvm runn 0 524288 tsi3-desktop 00 21:32:33
>>> >> 6 vm01 runn 0 524288 tsi3-desktop 00 02:56:05
>>> >>
>>> >> root at tsi1-desktop:/# onevnet list
>>> >> NID NAME TYPE BRIDGE
>>> >> 2 Private LAN Fixed virbr0
>>> >> 3 Private LAN 2 Fixed virbr0
>>> >>
>>> >> root at tsi1-desktop:/# onevnet show 2
>>> >> NID : 2
>>> >> UID : 0
>>> >> Network Name : Private LAN
>>> >> Type : Fixed
>>> >> Bridge : virbr0
>>> >>
>>> >> ....: Template :....
>>> >> BRIDGE=virbr0
>>> >> LEASES=IP=192.168.10.105
>>> >> NAME=Private LAN
>>> >> TYPE=FIXED
>>> >>
>>> >> ....: Leases :....
>>> >> IP = 192.168.10.105 MAC = 00:03:c0:a8:0a:69 USED = 1 VID = 5
>>> >>
>>> >> root at tsi1-desktop:/# onevm show winvm
>>> >> VID : 5
>>> >> UID : 0
>>> >> STATE : ACTIVE
>>> >> LCM STATE : RUNNING
>>> >> DEPLOY ID : one-5
>>> >> MEMORY : 524288
>>> >> CPU : 0
>>> >> LAST POLL : 1250784924
>>> >> START TIME : 08/19 14:39:36
>>> >> STOP TIME : 12/31 19:00:00
>>> >> NET TX : 0
>>> >> NET RX : 0
>>> >>
>>> >> ....: Template :....
>>> >> CPU : 0.5
>>> >> DISK :
>>> >> READONLY=no,SOURCE=/var/lib/one/images/windows.img,TARGET=hda
>>> >> GRAPHICS : LISTEN=127.0.0.1,PORT=-1,TYPE=vnc
>>> >> MEMORY : 512
>>> >> NAME : winvm
>>> >> NIC :
>>> >> BRIDGE=virbr0,IP=192.168.10.105,MAC=00:03:c0:a8:0a:69,NETWORK=Private
>>> >> LAN,VNID=2
>>> >> OS : BOOT=hd
>>> >> _______________________________________________
>>> >> Users mailing list
>>> >> Users at lists.opennebula.org
>>> >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>> >
>>> >
>>
>
More information about the Users
mailing list