cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <rohit.ya...@citrix.com>
Subject Re: CloudStack running in Virtualbox
Date Thu, 25 Oct 2012 06:43:31 GMT

On 24-Oct-2012, at 6:58 PM, Charles Moulliard <ch007m@gmail.com> wrote:

> Hi Rohit,
> 
> I have followed instructions here ((
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup)
> but I cannot ping the DevCloud VM machine at this address 192.168.56.2 from
> the machine where VB is running.

The IPs don't matter, the guide uses 192.168.56.x; if you're using 192.168.1.x, you've to
change all the IPs you will be using as needed.
Make sure you restart your devcloud.

> Host = LinuxMint running VirtualBox
> 
> ping 192.168.56.2
> PING 192.168.56.2 (192.168.56.2) 56(84) bytes of data.
> From 192.168.56.1 icmp_seq=1 Destination Host Unreachable
> 
> ifconfig
> eth0      Link encap:Ethernet  HWaddr 5c:26:0a:02:87:e9
>          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
>          inet6 addr: fe80::5e26:aff:fe02:87e9/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:1464812 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:804617 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:2152292686 (2.1 GB)  TX bytes:60443043 (60.4 MB)
>          Interrupt:20 Memory:e9600000-e9620000
> 
> vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00
>          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0
>          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:149 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 B)  TX bytes:24294 (24.2 KB)
> 
> Guest = DevCloud VM

Looking at your ifconfig, eth0 is 192.168.1.5 and then after religion xenbr0 is 192.168.56.2,
this is suspicious, something went wrong here.

> 
> After logging using root / password
> 
> ifconfig -->
> xenbr0 = 192.168.56.2/255.255.255.0
> eth0 is not configured
> eth1 has a MAC address but no IP address
> xenbr1 has a MAC address but no IP address
> 
> So something is missing in the config presented at the link ?

I'm not sure, can you recheck your /etc/network/interfaces? And fix eth0, xenbr0 as needed.

Probably, Edison can check?

Regards.

> 
> Regards,
> 
> Charles
> 
> On Wed, Oct 24, 2012 at 2:24 PM, Charles Moulliard <ch007m@gmail.com> wrote:
> 
>> Hi Rohit,
>> 
>> Thx for the update.
>> Additional questions :
>> - If the machine containing the VB is linked by example to the following
>> network 192.168.1.x/255.255.255.0 and has access to internet using a DHCP
>> server, do you think that the network to be used for the host only adapter
>> should be 192.168.56.x as defined here (
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup)
>> ?
>> - How will it be possible for the DevCloud VM machine to have access to
>> internet if we use only between VB and cloud machine the host only adapter
>> and not NAT or Bridge adapter as second adapter ?
>> 
>> There is a missing piece in the wiki page : You should tell to the user
>> how it should configure the vboxnet0 adapter in VB that we will use with
>> the host only adapter ! The existing page explains only how to configure
>> the DevCloud VM (/etc/hosts file)
>> 
>> Regards,
>> 
>> Charles
>> 
>> 
>> On Wed, Oct 24, 2012 at 1:37 PM, Rohit Yadav <rohit.yadav@citrix.com>wrote:
>> 
>>> I think the bridge mode may not be a good idea, as it may pollute your
>>> LAN.
>>> I suggest you try the host-only adapter:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup
>>> 
>>> Note: this for the latest asf master where we use maven and ant is only
>>> used till 4.0 (checkout 4.0 branch and do ant <stuff> after you setup the
>>> network in devcloud for host-only adapter).
>>> 
>>> Regards.
>>> ________________________________________
>>> From: Charles Moulliard [ch007m@gmail.com]
>>> Sent: Wednesday, October 24, 2012 4:34 PM
>>> To: cloudstack-users@incubator.apache.org
>>> Subject: Re: CloudStack running in Virtualbox
>>> 
>>> Damned. By changing the network adapter from NAT to bridge adapter in VB,
>>> I
>>> cannot anymore connect to the management server from the browser running
>>> in
>>> the host machine (= ubuntu machine) using localhost or 192.168.1.3 or
>>> 10.0.2.15 followed by 8080/client
>>> 
>>> ssh works well from ubuntu to the VB image (CloudStack) like you can see
>>> hereafter
>>> 
>>> ssh root@192.168.1.3
>>> root@192.168.1.3's password:
>>> Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic-pae i686)
>>> 
>>> * Documentation:  https://help.ubuntu.com/
>>> 
>>>  System information as of Wed Oct 24 04:01:34 PDT 2012
>>> 
>>>  System load:  0.07              Processes:             112
>>>  Usage of /:   31.3% of 5.57GB   Users logged in:       1
>>>  Memory usage: 22%               IP address for eth0:   192.168.1.3
>>>  Swap usage:   0%                IP address for xenbr0: 192.168.1.3
>>> 
>>> 
>>> On Wed, Oct 24, 2012 at 12:47 PM, Charles Moulliard <ch007m@gmail.com
>>>> wrote:
>>> 
>>>> I will change from NAT to bridge adapter.
>>>> DHCP is configured on the DSL router (= LAN where the machine is
>>> plugged)
>>>> 
>>>> 
>>>> On Wed, Oct 24, 2012 at 12:18 PM, Donal Lafferty <
>>>> donal.lafferty@citrix.com> wrote:
>>>> 
>>>>> This seems to explain the problem you are seeing.
>>>>> 
>>>>> "The disadvantage of NAT mode is that, much like a private network
>>> behind
>>>>> a router, the virtual machine is invisible and unreachable from the
>>> outside
>>>>> internet; you cannot run a server this way unless you set up port
>>>>> forwarding (described below)."
>>>>> 
>>>>> See http://www.virtualbox.org/manual/ch06.html#network_nat
>>>>> 
>>>>> 
>>>>> If you want to stick with NAT, you should create a VM in the virtual
>>> box
>>>>> install that can run your browser.  Alternatively, use a bridge
>>> adapter.
>>>>> 
>>>>> 
>>>>> BTW, where is the DHCP daemon that is allocating addresses to your VMs?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Charles Moulliard [mailto:ch007m@gmail.com]
>>>>> Sent: 24 October 2012 10:37
>>>>> To: cloudstack-users@incubator.apache.org
>>>>> Subject: Re: CloudStack running in Virtualbox
>>>>> 
>>>>> Are you connecting from the host running virtual box to the VM running
>>> the
>>>>> management server over SSH or HTTP?
>>>>>> No.
>>>>> 
>>>>> 10.0.2.50 = VirtualBox IP address
>>>>> 10.0.2.15 = CloudStack management server
>>>>> 10.0.2.179 = an instance created using the console (
>>>>> http://localhost:8080/client/). I can connect to the web console from
>>> the
>>>>> ubuntu machine where VirtualBox has been installed and running the
>>> image
>>>>> CloudStack
>>>>> 
>>>>> I cannot connect to the management server using address
>>>>> http://10.0.2.15:8080/client
>>>>> 
>>>>> On Wed, Oct 24, 2012 at 11:07 AM, Donal Lafferty
>>>>> <donal.lafferty@citrix.com>wrote:
>>>>> 
>>>>>> Hi Charles,
>>>>>> 
>>>>>> Need more information.
>>>>>> 
>>>>>> Are you connecting from the host running virtual box to the VM
>>> running
>>>>> the
>>>>>> management server over SSH or HTTP?
>>>>>> 
>>>>>> For HTTP, AFAIK you not to include the port and virtual path.  E.g.
>>>>>> http://10.0.2.179:8080/client
>>>>>> 
>>>>>> Also, can you confirm what IP addresses you have?  10.0.2.50 seems
>>> to be
>>>>>> the VirtualBox gateway and 10.0.2.179 the management server.  So
>>> what is
>>>>>> 10.0.2.15?
>>>>>> 
>>>>>> DL
>>>>>> 
>>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Charles Moulliard [mailto:ch007m@gmail.com]
>>>>>> Sent: 24 October 2012 09:49
>>>>>> To: cloudstack-users@incubator.apache.org
>>>>>> Subject: CloudStack running in Virtualbox
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> Hi. I have installed successfully the following image in virtualbox
(
>>>>>> http://download.cloud.com/templates/devcloud/DevCloud.ova) and
>>> created
>>>>> an
>>>>>> instance. Unfortunately, I cannot connect to it with its IP address
>>>>>> (10.0.2.179). VirtualBox uses NAT and a host only adapter + vboxnet
>>>>>> (10.0.2.50). Is there something else to configure ?
>>>>>> When I log to the Unix machine (where CloudStack has been deployed),
>>> I
>>>>> can
>>>>>> ping 10.0.2.15 address but not 10.0.2.179.
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> --
>>>>>> Charles Moulliard
>>>>>> Apache Committer / Sr. Enterprise Architect (RedHat)
>>>>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Charles Moulliard
>>>>> Apache Committer / Sr. Enterprise Architect (RedHat)
>>>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Charles Moulliard
>>>> Apache Committer / Sr. Enterprise Architect (RedHat)
>>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Charles Moulliard
>>> Apache Committer / Sr. Enterprise Architect (RedHat)
>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>>> 
>> 
>> 
>> 
>> --
>> Charles Moulliard
>> Apache Committer / Sr. Enterprise Architect (RedHat)
>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>> 
>> 
>> 
> 
> 
> --
> Charles Moulliard
> Apache Committer / Sr. Enterprise Architect (RedHat)
> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com


Mime
View raw message