The most strange thing is that:
1) The VM which is running in host A can access the internet and can be
accessed from the outside. But, when I migrate it from host A to host B. I
can neither access the internet nor can be accessed from the outside!
2) The VM which is running in host B can neither access the internet nor
can be accessed from the outside at begging. But, when I migrate it from
host B to host A. I can either access the internet or can be accessed from
the outside!
Is there anyone can help me explain it?
BTW, I think host B is very suspicious, and I would like to provide you
with the information of my host B.
$ ifconfig -a
cloudbr0 Link encap:Ethernet HWaddr e0:db:55:25:fb:14
inet addr:10.10.101.107 Bcast:10.10.101.255 Mask:255.255.255.0
inet6 addr: fe80::e2db:55ff:fe25:fb14/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11114025 errors:0 dropped:35 overruns:0 frame:0
TX packets:9141766 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45818581471 (45.8 GB) TX bytes:23705891021 (23.7 GB)
(ps: host A is also with cloud bridge "cloudbr0", and its IP address is
10.10.101.103)
$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 10.10.101.254 0.0.0.0 UG 100 0 0
cloudbr0
10.10.101.0 0.0.0.0 255.255.255.0 U 0 0 0
cloudbr0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
cloud0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
virbr0
(ps:host B can access the internet)
--
Regards,
Du Jun
2014-03-11 13:30 GMT+08:00 Du Jun <dj199...@gmail.com>:
> Hi Neelarapu,
>
> I am sorry that I did not describe my situation clearly. I am using
> ubuntu, and output of `ifconfig -a` shows
> the name of interface is "eth0", it has mac address.
>
> When I have a look at /etc/network/interfaces, it shows:
> auto eth0
> iface eth0 inet dhcp
>
> What's more, I use the same template in the host A, and the interfaces of
> VM is okay.
>
> BTW, from web UI, I can see the nic of the VM, but the ip address is
> missing when I type `ifconfig -a`. It's so
> strange!
>
> --
> Regards,
> Du Jun
>
>
> 2014-03-11 13:06 GMT+08:00 Sanjeev Neelarapu <sanjeev.neelar...@citrix.com
> >:
>
> Hi Jun,
>>
>> There could be some issue with the template with which you deployed vm.
>> Please check "ifconfig -a" output in vm booted on hostB.
>> This will give the interface name and make sure that network-scripts
>> directory has a file with the interface name.
>>
>> -Sanjeev
>>
>> -----Original Message-----
>> From: Du Jun [mailto:dj199...@gmail.com]
>> Sent: Monday, March 10, 2014 5:05 PM
>> To: users
>> Subject: Re: Fail to configure network interface when booting VM
>>
>> BTW, the /etc/cloudstack/agent/agent.properties is shown below:
>> #Storage
>> #Mon Mar 10 16:59:56 CST 2014
>> guest.network.device=cloudbr0
>> workers=5
>> private.network.device=cloudbr0
>> port=8250
>> resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
>> pod=1
>> zone=1
>> guid=e2e402df-6e65-3e08-a680-35ecfb39716b
>> public.network.device=cloudbr0
>> cluster=1
>> local.storage.uuid=05d6ad68-fdd0-4041-8371-a592727d57d4
>> domr.scripts.dir=scripts/network/domr/kvm
>> LibvirtComputingResource.id=10
>> host=10.10.101.103
>>
>> We can see that, guest, private and public all use the network bridge
>> "cloudbr0". And, route table in my agent host(B) is like that:
>> root@ubuntu-7:~# route -n
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref Use
>> Iface
>> 0.0.0.0 10.10.101.254 0.0.0.0 UG 100 0 0
>> cloudbr0
>> 10.10.101.0 0.0.0.0 255.255.255.0 U 0 0 0
>> cloudbr0
>> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
>> cloud0
>> 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
>> virbr0
>>
>> It seems all okay. I wonder what I have missed?
>>
>> --
>> Best Regards,
>> Du Jun
>>
>>
>>
>> 2014-03-10 19:26 GMT+08:00 Du Jun <dj199...@gmail.com>:
>>
>> > Hi Bharat,
>> >
>> > Thank you for your prompt reply. As I am new to CloudStack, I have 2
>> > questions to consult you.
>> >
>> > >check if host B has the systemvm.iso in it. if not copy it manually
>> > >from
>> > host A.
>> > Where can I check if host B has the systemvm.iso?
>> >
>> > >before adding the host make sure the host tags are cleared.
>> > When I add the host B, the tag of the host is empty. After adding the
>> > host, I add a tag for host B so that I can always put the VM to host B
>> > for testing purpose. Does it matter?
>> >
>> > Thanks!
>> > --
>> > Best Regards,
>> > Du Jun
>> >
>> >
>> > 2014-03-10 19:10 GMT+08:00 Bharat Kumar <bharat.ku...@citrix.com>:
>> >
>> > Hi Jun,
>> >>
>> >> check if host B has the systemvm.iso in it. if not copy it manually
>> >> from host A.
>> >>
>> >> cloudstack generally dose this for you when you add a host for the
>> >> first time.
>> >> before adding the host make sure the host tags are cleared.
>> >>
>> >> Regards,
>> >> Bharat.
>> >> On 10-Mar-2014, at 4:35 pm, Du Jun <dj199...@gmail.com> wrote:
>> >>
>> >> > Hi all,
>> >> >
>> >> > I am using CloudStack4.2 advanced zone in Ubuntu12.04. I use host
>> >> > A(10.10.101.103) as my management server, and use host
>> >> > B(10.10.101.107)
>> >> as
>> >> > my agent host. I meet a problem that the VM booted in host B fail
>> >> > to configure network interface when boot up. In other words, when I
>> >> > type `ifconfig` in VM booted in host B, I find the IP address is
>> missing!
>> >> > However, there is no problem with the VM booted in host A.
>> >> >
>> >> > BTW, I both add a network bridge "cloudbr0" in management server(A)
>> >> > and agent host(B). Both server A and B can access the internet and
>> >> > I can
>> >> access
>> >> > them from outside. So, I have no idea now. Can anyone tell me how
>> >> > to
>> >> debug
>> >> > or provide me with some clue? Thanks!
>> >> >
>> >> > --
>> >> > Best Regards,
>> >> > Frank
>> >>
>> >>
>> >
>>
>
>
