Re: [Openstack] How to mount ISO file to a openstack instance ?

2017-05-07 Thread Warad, Manjunath (Nokia - SG/Singapore)
Hi,

Yes, Glance can be used to manage ISO file and this can be configured to shared 
by multiple instances as is.

But as far as I know, this ISO image cannot be used to boot an instance.

Regards,
Manjunath

From: don...@ahope.com.cn [mailto:don...@ahope.com.cn]
Sent: Sunday, 7 May, 2017 10:12 PM
To: openstack 
Subject: [Openstack] How to mount ISO file to a openstack instance ?

Hi all,

i want to know how to mount ISO file to a openstack instance ? Can it be 
managed by Glance ? And can an iso image be shared by multiple instances?


=
董 建 华
地址:杭州滨江区南环路3766号新世纪办公楼
邮编:310053
手机:13857132818
总机:0571-28996000
传真:0571-28996001
热线:4006728686
网址:www.ahope.com.cn
Email:don...@ahope.com.cn
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Limit Summary not update

2017-04-21 Thread Warad, Manjunath (Nokia - SG/Singapore)
Are all the project / tenant same in these cases?

From: Adhi Priharmanto [mailto:adhi@gmail.com]
Sent: Friday, 21 April, 2017 3:33 PM
To: openstack 
Subject: [Openstack] Limit Summary not update


Hi All,
I'm in ocata release, had 2 running instance
(openstack) server list
+--+++---++
| ID   | Name   | Status | Networks 
 | Image Name |
+--+++---++
| 94d63b55-1dd8-4e9e-a471-58c14defccd1 | test13 | ACTIVE | public119=119.x.x.x 
| Cirros-3-5-xen |
| 40d68c6e-6678-4a64-9309-2302a201bc09 | test11 | ACTIVE | admin-int=15.15.1.13 
 | Cirros-3-5-xen |
+--+++---++

but why when I open in the horizon at "Project / Compute / Overview" page it's 
show "Instances Used 3 of 10"
and when I check from usage list it show 4 instance used ?
(openstack) usage list
Usage from 2017-03-24 to 2017-04-22:
+-+-+--+---+---+
| Project | Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+-+-+--+---+---+
| admin   |   4 | 52560.71 |102.66 |102.66 |
+-+-+--+---+---+

even I deleted all instance, the value in  "Project / Compute / Overview" page 
horizon won't be refresh/update.
any suggestion for this case ?


--
Cheers,


Error! Filename not specified.
Adhi Priharmanto
Error! Filename not specified.about.me/a_dhi






+62-812-82121584

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Fwd: [Fuel] Fuel installation stuck in "Waiting for product VM to download files. Please do NOT abort the script"

2017-04-12 Thread Warad, Manjunath (Nokia - SG/Singapore)
It appears to be network issue. Please check installation logs for more details:

Can your host system reach internet?
If so, is it behind any firewall?

> On 13 Apr 2017, at 05:28, Ravikumar R  wrote:
> 
> 
> HI,
> 
> I'm trying to install Mirantis fuel in Ubuntu 14.04 VM running in ESXi. I 
> have hadware virtualization enabled in the VM settings..
> 
> The installation stuck at "Waiting for product VM to download files. Please 
> do NOT abort the script"
> 
> + ./actions/master-node-create-and-install.sh
> Virtual machine 'fuel-master' is created and registered.
> UUID: fcc56d72-b054-4c6b-801e-a2348221911c
> Settings file: '/root/VirtualBox VMs/fuel-master/fuel-master.vbox'
> Adding hostonly adapter to fuel-master and bridging with host NIC vboxnet0...
> Adding disk to fuel-master, with size 65535 Mb...
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Medium created. UUID: 9f0c385c-c855-432a-a16b-e45ea1591b61
> Adding serial numbers of disks to fuel-master...
> Adding hostonly adapter to fuel-master and bridging with host NIC vboxnet1...
> Adding NAT adapter to fuel-master for outbound network access through the 
> host system...
> 
> Waiting for VM "fuel-master" to power on...
> VM "fuel-master" has been successfully started.
> 
> Waiting for product VM to download files. Please do NOT abort the script...
> 
> 
> The installation never moved out of this point and times out of 3000 seconds.
> 
> Is it supported to run the Fuel in a EXSi based VM as host?
> 
> If yes, please let me know how to troubleshoot this issue.
> 
> Thanks,
> Ravi
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] DNS problem when multiple subnets

2017-03-27 Thread Warad, Manjunath (Nokia - SG/Singapore)
Hi,

Do you see dns address in /etc/resolv.conf?

Regards,
Manjunath

> On 27 Mar 2017, at 19:45, Georgios Dimitrakakis  wrote:
> 
> Hi!
> 
> I have an OpenStack Ocata installation where I have one "selfservice" network 
> and one "provider" network (with 1 external subnet).
> 
> This configuration was set using the default installation guide and is 
> working fine.
> 
> Now I 've bought a second external subnet from my provider and I 've added it 
> as a second subnet to the previously "provider" network.
> 
> I can spawn VMs without a problem and VMs can get an IP from the secondly 
> (newly) configured subnet without a problem.
> 
> I can access the VMs to their IP address and from the VMs I can ping anb ssh 
> to other hosts without a problem.
> 
> My problem is that the VM when on the new subnet cannot resolve names. 
> Although it has the correct DNS server (which is the same as the previous 
> one) and can ping the DNS server cannot resolve any name.
> 
> Any ideas what might be the problem???
> 
> Regards,
> 
> 
> G.
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] DHCP Request Failed on Ocata

2017-03-20 Thread Warad, Manjunath (Nokia - SG)
I have installed on Ubuntu, so I don't files as /etc/sysconfig/iptables.

Apart from the listed below DROP/REJECT rules there are no more of such rules.

Regards,
Manjunath

-Original Message-
From: Georgios Dimitrakakis [mailto:gior...@acmac.uoc.gr] 
Sent: Monday, 20 March, 2017 6:32 PM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] DHCP Request Failed on Ocata

 Hello and thanks for providing the detailed iptables output.

 I don't believe that having initially "firewalld" enabled had any  impact 
because (to my understanding)  all rules are added when the services are 
restarted.

 So by rebooting the nodes everything should be OK which isn't.

 Can you tell me if in your "/etc/sysconfig/iptables" you have any other  rules 
that DROP or REJECT packages?


 Best,

 G.


 On Mon, 20 Mar 2017 03:08:09 +0000, Warad, Manjunath (Nokia - SG) 
 wrote:
> Here are my filter tables...
> I did a default installation of 1 controller and 1 compute following
> openstack install docs.
>
> I read through that the firewalld was not stopped during
> installation. I'm not sure if that could have cause some invalid
> insertions/deletions into iptables.
> Probably, you may want to consider re-installing controller and
> compute nodes with firewalld disabled in the beginning unless you
> have enough time to troubleshoot the problem.
>
> Controller Filter Table:
>
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> neutron-linuxbri-INPUT  all  --  anywhere anywhere
> nova-api-INPUT  all  --  anywhere anywhere
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
> neutron-filter-top  all  --  anywhere anywhere
> neutron-linuxbri-FORWARD  all  --  anywhere anywhere
> nova-filter-top  all  --  anywhere anywhere
> nova-api-FORWARD  all  --  anywhere anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
> neutron-filter-top  all  --  anywhere anywhere
> neutron-linuxbri-OUTPUT  all  --  anywhere anywhere
> nova-filter-top  all  --  anywhere anywhere
> nova-api-OUTPUT  all  --  anywhere anywhere
>
> Chain neutron-filter-top (2 references)
> target prot opt source   destination
> neutron-linuxbri-local  all  --  anywhere anywhere
>
> Chain neutron-linuxbri-FORWARD (1 references)
> target prot opt source   destination
>
> Chain neutron-linuxbri-INPUT (1 references)
> target prot opt source   destination
>
> Chain neutron-linuxbri-OUTPUT (1 references)
> target prot opt source   destination
>
> Chain neutron-linuxbri-local (1 references)
> target prot opt source   destination
>
> Chain neutron-linuxbri-sg-chain (0 references)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere
>
> Chain neutron-linuxbri-sg-fallback (0 references)
> target prot opt source   destination
> DROP   all  --  anywhere anywhere /*
> Default drop rule for unmatched traffic. */
>
> Chain nova-api-FORWARD (1 references)
> target prot opt source   destination
>
> Chain nova-api-INPUT (1 references)
> target prot opt source   destination
> ACCEPT tcp  --  anywhere controller   tcp 
> dpt:8775
>
> Chain nova-api-OUTPUT (1 references)
> target prot opt source   destination
>
> Chain nova-api-local (1 references)
> target prot opt source   destination
>
> Chain nova-filter-top (2 references)
> target prot opt source   destination
> nova-api-local  all  --  anywhere anywhere
>
> Compute Filter Table:
>
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> neutron-linuxbri-INPUT  all  --  anywhere anywhere
> nova-compute-INPUT  all  --  anywhere anywhere
> ACCEPT udp  --  anywhere anywhere udp 
> dpt:domain
> ACCEPT tcp  --  anywhere anywhere tcp 
> dpt:domain
> ACCEPT udp  --  anywhere anywhere udp 
> dpt:bootps
> ACCEPT tcp  --  anywhere anywhere tcp 
> dpt:bootps
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
> neutron-filter-top  all  --  anywhere anywhere
> neutron-linuxbri-FORWARD  all  --  anywhere anywhere
> nova-filter-top  all  --  anywhere anywhere
> nova-comput

Re: [Openstack] DHCP Request Failed on Ocata

2017-03-19 Thread Warad, Manjunath (Nokia - SG)
Here are my filter tables... 
I did a default installation of 1 controller and 1 compute following openstack 
install docs.

I read through that the firewalld was not stopped during installation. I'm not 
sure if that could have cause some invalid insertions/deletions into iptables.
Probably, you may want to consider re-installing controller and compute nodes 
with firewalld disabled in the beginning unless you
have enough time to troubleshoot the problem.

Controller Filter Table:

Chain INPUT (policy ACCEPT)
target prot opt source   destination 
neutron-linuxbri-INPUT  all  --  anywhere anywhere
nova-api-INPUT  all  --  anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 
neutron-filter-top  all  --  anywhere anywhere
neutron-linuxbri-FORWARD  all  --  anywhere anywhere
nova-filter-top  all  --  anywhere anywhere
nova-api-FORWARD  all  --  anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 
neutron-filter-top  all  --  anywhere anywhere
neutron-linuxbri-OUTPUT  all  --  anywhere anywhere
nova-filter-top  all  --  anywhere anywhere
nova-api-OUTPUT  all  --  anywhere anywhere

Chain neutron-filter-top (2 references)
target prot opt source   destination 
neutron-linuxbri-local  all  --  anywhere anywhere

Chain neutron-linuxbri-FORWARD (1 references)
target prot opt source   destination 

Chain neutron-linuxbri-INPUT (1 references)
target prot opt source   destination 

Chain neutron-linuxbri-OUTPUT (1 references)
target prot opt source   destination 

Chain neutron-linuxbri-local (1 references)
target prot opt source   destination 

Chain neutron-linuxbri-sg-chain (0 references)
target prot opt source   destination 
ACCEPT all  --  anywhere anywhere

Chain neutron-linuxbri-sg-fallback (0 references)
target prot opt source   destination 
DROP   all  --  anywhere anywhere /* Default drop 
rule for unmatched traffic. */

Chain nova-api-FORWARD (1 references)
target prot opt source   destination 

Chain nova-api-INPUT (1 references)
target prot opt source   destination 
ACCEPT tcp  --  anywhere controller   tcp dpt:8775

Chain nova-api-OUTPUT (1 references)
target prot opt source   destination 

Chain nova-api-local (1 references)
target prot opt source   destination 

Chain nova-filter-top (2 references)
target prot opt source   destination 
nova-api-local  all  --  anywhere anywhere  

Compute Filter Table:

Chain INPUT (policy ACCEPT)
target prot opt source   destination 
neutron-linuxbri-INPUT  all  --  anywhere anywhere
nova-compute-INPUT  all  --  anywhere anywhere
ACCEPT udp  --  anywhere anywhere udp dpt:domain
ACCEPT tcp  --  anywhere anywhere tcp dpt:domain
ACCEPT udp  --  anywhere anywhere udp dpt:bootps
ACCEPT tcp  --  anywhere anywhere tcp dpt:bootps

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 
neutron-filter-top  all  --  anywhere anywhere
neutron-linuxbri-FORWARD  all  --  anywhere anywhere
nova-filter-top  all  --  anywhere anywhere
nova-compute-FORWARD  all  --  anywhere anywhere
ACCEPT all  --  anywhere 192.168.122.0/24 ctstate 
RELATED,ESTABLISHED
ACCEPT all  --  192.168.122.0/24 anywhere
ACCEPT all  --  anywhere anywhere
REJECT all  --  anywhere anywhere reject-with 
icmp-port-unreachable
REJECT all  --  anywhere anywhere reject-with 
icmp-port-unreachable

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 
neutron-filter-top  all  --  anywhere anywhere
neutron-linuxbri-OUTPUT  all  --  anywhere anywhere
nova-filter-top  all  --  anywhere anywhere
nova-compute-OUTPUT  all  --  anywhere anywhere
ACCEPT udp  --  anywhere anywhere udp dpt:bootpc

Chain neutron-filter-top (2 references)
target prot opt source 

Re: [Openstack-operators] [Nova] Unable to login to instance

2016-09-15 Thread Warad, Manjunath (Nokia - SG)
Any workarounds to overcome this issue? I am basically stuck with this...

I cannot access via ssh as well, tried with private and public network to 
launch instance...

1. With private network:

- dhcp can assign an IP address successfully, but the subnet doesn't exist on 
host so I'm unable to access the instance.
Logs from instance launch...

no results found for mode=local. up 15.72. searched: nocloud configdrive ec2
Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending select for 10.0.0.3...
Lease of 10.0.0.3 obtained, lease time 86400
route: SIOCADDRT: File exists
WARN: failed: route add -net "0.0.0.0/0" gw "10.0.0.1"
cirros-ds 'net' up at 17.90
checking http://169.254.169.254/2009-04-04/instance-id
successful after 1/20 tries: up 18.65. iid=i-0003
failed to get http://169.254.169.254/2009-04-04/meta-data/public-keys
warning: no ec2 metadata for public-keys
failed to get http://169.254.169.254/2009-04-04/user-data
warning: no ec2 metadata for user-data


=== network info ===
if-info: lo,up,127.0.0.1,8,::1
if-info: eth0,up,10.0.0.3,24,fe80::f816:3eff:fe44:7613
ip-route:default via 10.0.0.1 dev eth0 
ip-route:10.0.0.0/24 dev eth0  src 10.0.0.3 
ip-route:169.254.169.254 via 10.0.0.1 dev eth0 
=== datasource: ec2 net ===
 -

IP addresses on the host machine (devstack)
Interface   IP Addr
br-ex   172.24.4.1 
enp0s3  172.16.1.71
virbr0  192.168.122.1

devstack@devstack:~/devstack$ route
Kernel IP routing table
Destination Gateway Genmask Flags   
Metric  Ref Use Iface
default home0.0.0.0 UG  
0   0   0   enp0s3
10.0.0.0172.24.4.4  255.255.255.0   UG  
0   0   0   br-ex
172.16.0.0  *   255.255.0.0 U   
0   0   0   enp0s3
172.24.4.0  *   255.255.255.0   U   
0   0   0   br-ex
192.168.122.0   *   255.255.255.0   U   
0   0   0   virbr0

2. With public network:

- failed to get dhcp IP address assigned..

Logs from instance launch...
--
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
Usage: /sbin/cirros-dhcpc 
No lease, failing
WARN: /etc/rc3.d/S40-network failed


=== network info ===
if-info: lo,up,127.0.0.1,8,::1
if-info: eth0,up,,8,fe80::f816:3eff:fe74:3c4b
=== datasource: None None ===
=== cirros: current=0.3.4 uptime=250.37 ===
route: fscanf
=== pinging gateway failed, debugging connection ===
 debug start ##
### /etc/init.d/sshd start
Starting dropbear sshd: OK
route: fscanf
### ifconfig -a
eth0  Link encap:Ethernet  HWaddr FA:16:3E:74:3C:4B  
  inet6 addr: fe80::f816:3eff:fe74:3c4b/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:6 errors:0 dropped:0 overruns:0 frame:0
  TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:608 (608.0 B)  TX bytes:1132 (1.1 KiB)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:12 errors:0 dropped:0 overruns:0 frame:0
  TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:1020 (1020.0 B)  TX bytes:1020 (1020.0 B)

### route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
route: fscanf
### cat /etc/resolv.conf
cat: can't open '/etc/resolv.conf': No such file or directory
### gateway not found
/sbin/cirros-status: line 1: can't open /etc/resolv.conf: no such file
### pinging nameservers
### uname -a
Linux cirros 3.2.0-80-virtual #116-Ubuntu SMP Mon Mar 23 17:28:52 UTC 2015 
x86_64 GNU/Linux
### lsmod
Module  Size  Used byNot tainted
nls_iso8859_1  12713  0 
nls_cp437  16991  0 
vfat   17585  0 
fat61512  1 vfat
isofs  40259  0 
ip_tables  27473  0 
x_tables   29891  1 ip_tables
pcnet3242119  0 
8139cp 27360  0 
ne2k_pci   13691  0 
8390   18856  1 ne2k_pci
e1000 108589  0 
acpiphp24231  0 
### dmesg | tail
[4.426901] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[4.476572] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbog...@alpha.franken.de
[4.525105] ip_tables: (C) 2000-2006 Netfilter Core Team
[5.966370] 

Re: [Openstack-operators] [Nova] Unable to login to instance

2016-09-13 Thread Warad, Manjunath (Nokia - SG)
Tried with this image and unfortunately have the same problem.

> To follow what Vincent said - maybe you can -download 
> cirros-0.3.4-x86_64-disk.img [3] and see.

I think 0.3.4 also has the bug, but you could try with one from:

http://download.cirros-cloud.net/daily/20160722/

The password may have changed to letsplay2, c.f.:

https://code.launchpad.net/~smoser/cirros/trunk.letsplay2/+merge/298652

Regards,
M
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


Re: [Openstack-operators] [Nova] Unable to login to instance

2016-09-13 Thread Warad, Manjunath (Nokia - SG)
Thanks for quick revert!

Symptoms of the problem and reported in bug appears to be same except that I 
have Eng-US keyboard.

I haven't tried different image nor ssh login, I am a newbie and was looking 
ways to login using SSH.

I will go through documentation and try ssh login.

Regards,
Manjunath

From: Vincent Legoll (IdGC) [vincent.leg...@idgrilles.fr]
Sent: Tuesday, September 13, 2016 10:42 PM
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [Nova] Unable to login to instance

Hello,

Le 13/09/2016 à 16:32, Warad, Manjunath (Nokia - SG) a écrit :
> Tried to look in different forums but I don't see conclusive answer though 
> many have faced/posted this problem.
>
> Upon the login prompt, if I try to press any key I get following error...
>
> [   98.191753] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 
> on isa0060/serio0).
> [   98.193100] atkbd serio0: Use 'setkeycodes 00 ' to make it known.
> [   98.258209] atkbd serio0: Unknown key released (translated set 2, code 0x0 
> on isa0060/serio0).
> [   98.259119] atkbd serio0: Use 'setkeycodes 00 ' to make it known.
>
> Attached is the logs of the instance.
>
> - I have Eng-US keyboard.
> - Tried with enable_service q-dhcp in localrc (referring to some other forum)
>
> Any help is much appreciated.

Is that an instance of this bug :

https://bugs.launchpad.net/cirros/+bug/1454144

Did you try with another image (ubuntu, centos...), or tried SSH login ?

--
Vincent Legoll
EGI FedCloud task force
Cloud Computing at IdGC
France Grilles / CNRS / IPHC

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


[Openstack-operators] [Nova] Unable to login to instance

2016-09-13 Thread Warad, Manjunath (Nokia - SG)
Hi All,

I have deployed openstack dev environment using devstack.

Upon creating an instance, instance comes up but unable to take any keyboard 
entry.

Tried to look in different forums but I don't see conclusive answer though many 
have faced/posted this problem.

Upon the login prompt, if I try to press any key I get following error...

[   98.191753] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on 
isa0060/serio0).
[   98.193100] atkbd serio0: Use 'setkeycodes 00 ' to make it known.
[   98.258209] atkbd serio0: Unknown key released (translated set 2, code 0x0 
on isa0060/serio0).
[   98.259119] atkbd serio0: Use 'setkeycodes 00 ' to make it known.

Attached is the logs of the instance.

- I have Eng-US keyboard.
- Tried with enable_service q-dhcp in localrc (referring to some other forum)

Any help is much appreciated.

Regards,
Manjunath
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.0-80-virtual (buildd@batsu) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #116-Ubuntu SMP Mon Mar 23 17:28:52 UTC 2015 
(Ubuntu 3.2.0-80.116-virtual 3.2.68)
[0.00] Command line: root=/dev/vda console=tty0 console=ttyS0 
no_timer_check
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009fc00 (usable)
[0.00]  BIOS-e820: 0009fc00 - 000a (reserved)
[0.00]  BIOS-e820: 000f - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 1ffe (usable)
[0.00]  BIOS-e820: 1ffe - 2000 (reserved)
[0.00]  BIOS-e820: fffc - 0001 (reserved)
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.8 present.
[0.00] No AGP bridge found
[0.00] last_pfn = 0x1ffe0 max_arch_pfn = 0x4
[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[0.00] found SMP MP-table at [880f6620] f6620
[0.00] init_memory_mapping: -1ffe
[0.00] RAMDISK: 1fc4e000 - 1ffe
[0.00] ACPI: RSDP 000f6420 00014 (v00 BOCHS )
[0.00] ACPI: RSDT 1ffe16ee 00034 (v01 BOCHS  BXPCRSDT 0001 
BXPC 0001)
[0.00] ACPI: FACP 1ffe0c14 00074 (v01 BOCHS  BXPCFACP 0001 
BXPC 0001)
[0.00] ACPI: DSDT 1ffe0040 00BD4 (v01 BOCHS  BXPCDSDT 0001 
BXPC 0001)
[0.00] ACPI: FACS 1ffe 00040
[0.00] ACPI: SSDT 1ffe0c88 009B6 (v01 BOCHS  BXPCSSDT 0001 
BXPC 0001)
[0.00] ACPI: APIC 1ffe163e 00078 (v01 BOCHS  BXPCAPIC 0001 
BXPC 0001)
[0.00] ACPI: HPET 1ffe16b6 00038 (v01 BOCHS  BXPCHPET 0001 
BXPC 0001)
[0.00] No NUMA configuration found
[0.00] Faking a node at -1ffe
[0.00] Initmem setup node 0 -1ffe
[0.00]   NODE_DATA [1fc46000 - 1fc4afff]
[0.00] Zone PFN ranges:
[0.00]   DMA  0x0010 -> 0x1000
[0.00]   DMA320x1000 -> 0x0010
[0.00]   Normal   empty
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[2] active PFN ranges
[0.00] 0: 0x0010 -> 0x009f
[0.00] 0: 0x0100 -> 0x0001ffe0
[0.00] ACPI: PM-Timer IO Port: 0x608
[0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[0.00] ACPI: IOAPIC (id[0x00] address[0xfec0] gsi_base[0])
[0.00] IOAPIC[0]: apic_id 0, version 17, address 0xfec0, GSI 0-23
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[0.00] Using ACPI (MADT) for SMP configuration information
[0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0
[0.00] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[0.00] PM: Registered nosave memory: 0009f000 - 000a
[0.00] PM: Registered nosave memory: 000a - 000f
[0.00] PM: Registered nosave memory: 000f - 0010
[0.00] Allocating PCI resources starting at 2000 (gap: 
2000:dffc)
[0.00] Booting paravirtualized kernel on bare hardware
[0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:1 
nr_node_ids:1
[0.00] PERCPU: