Ask Your Question

rohitist's profile - activity

2014-09-23 08:55:26 -0500 received badge  Famous Question (source)
2014-07-10 06:29:20 -0500 received badge  Famous Question (source)
2014-05-07 09:31:38 -0500 received badge  Famous Question (source)
2014-04-21 00:22:14 -0500 received badge  Notable Question (source)
2014-04-21 00:22:10 -0500 received badge  Famous Question (source)
2014-04-14 04:55:48 -0500 received badge  Notable Question (source)
2014-04-11 00:25:54 -0500 commented answer Could not find hda disk attached: installed VM begins with setup again

Have you tried to take the snapshot of the instance while the total setup process completes? If not, then do this and launch a new instance from the snapshot image. see whether this reinstallation appears again or not.

2014-04-10 01:35:26 -0500 received badge  Notable Question (source)
2014-04-09 05:08:18 -0500 received badge  Popular Question (source)
2014-04-09 03:17:51 -0500 received badge  Self-Learner (source)
2014-04-09 00:46:30 -0500 answered a question openstack: instance cannot connect to internet

My bad... like most of my questions, I again resolved this. I was too careless to check my organizations's firewall rules ;)

Anyway, thanks for your input. :)

2014-04-08 06:55:10 -0500 commented question openstack: instance cannot connect to internet

Yes, I am able to hit DNS (private and public also).

Below is the trace from the problem instance:

[root@host-10-0-0-2 ~]# ping 10.0.0.3 PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. 64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.219 ms 64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.174 ms ^C --- 10.0.0.3 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1870ms rtt min/avg/max/mdev = 0.174/0.196/0.219/0.026 ms [root@host-10-0-0-2 ~]# [root@host-10-0-0-2 ~]#

[root@host-10-0-0-2 ~]# ping 192.168.125.10 PING 192.168.125.10 (192.168.125.10) 56(84) bytes of data. 64 bytes from 192.168.125.10: icmp_seq=1 ttl=126 time=0.497 ms 64 bytes from 192.168.125.10: icmp_seq=2 ... (more)

2014-04-08 06:40:06 -0500 commented question openstack: instance cannot connect to internet

@mpetason: Yes, I am able to do all :( Any more suggestion please.

2014-04-08 01:27:21 -0500 asked a question openstack: instance cannot connect to internet

Hi,

I have one confusing question here and i could not find related question on the internet.

I am trying Openstack all in one installation using Packstack. Everything is fine. I can create an instance and connect on the internet. But the peculiarity arises when i create an another instance. The other instance cannot connect or ping to the internet (say google.com ). From the other instance, i can ping the host machine, the private and public IP of the virtual router, the other instance, our infrastructure DNS, gateway, etc.

you can see my network topology below:

image description

Can anyone please help me out in this case?

Thanks in advance.

2014-04-08 01:00:18 -0500 received badge  Popular Question (source)
2014-04-07 00:31:10 -0500 received badge  Popular Question (source)
2014-04-07 00:29:44 -0500 commented answer How to use storage of another machine to add volume in openstack

I'm glad it helped you @Anand TS :)

2014-04-04 04:12:34 -0500 received badge  Self-Learner (source)
2014-04-04 04:12:34 -0500 received badge  Teacher (source)
2014-04-04 03:33:10 -0500 answered a question How to use storage of another machine to add volume in openstack

Fortunately, I have found the answer, which can help others also:

image description

image description

image description

Regards, Rohit

2014-04-03 06:37:29 -0500 received badge  Notable Question (source)
2014-04-03 06:35:56 -0500 answered a question Could not find hda disk attached: installed VM begins with setup again

I couldn't make this happen in the way I discussed above:

I mean, 1. create an instance. 2. complete the setup and let the instance running. 3. detach the ISO file from the instance and attach a hda device. 4. restart the VM. 5. shut off the VM and start it again to check whether it has become persistent.

These 5 steps always lead me to reinstallation of the guest OS.

However, I observed one peculiar scenario.

Just after Step 4, I took the snapshot of the running VM. Then, I terminated the instance and launched a fresh VM from the snapshot.

Strange but this time the VM created from the snapshot was persistent. I mean, i shut this new VM and started it. Unlike the "boot from ISO" case, I was not anymore prompted for reinstallation of guest OS.

Thus, anyhow, I assume, my problem is resolved but left me wonder why couldn't i get success from the former 5 steps procedure.

2014-04-03 06:34:01 -0500 answered a question Couldn't create instance from Snapshot

I assume this is a bug in Openstack because I reinstalled openstack from the scratch and found that I could create a snapshot and also launch an instance from the snapshot.

2014-04-03 05:38:23 -0500 asked a question How to use storage of another machine to add volume in openstack

Hi,

I have done all in one installation of openstack using packstack on a machine and everything works fine. But I have a requirement now.

The host machine (on which openstack has been installed) is running out of storage and I, therofore, would like to use the storage of another physical machine connected with a network and assign it as a volume to an instance.

Is there a possibility to mount a NFS filesystem on the host machine and make use of the mounted point to assign a volume to an instance?

Or, please suggest me if there is another way?

Thanks, Rohit

2014-04-01 08:19:10 -0500 received badge  Popular Question (source)
2014-03-30 23:17:06 -0500 received badge  Notable Question
2014-03-24 02:31:26 -0500 commented question Could not find hda disk attached: installed VM begins with setup again

@mpetason: Thanks for your reply. I have already uploaded image (RHEL) to openstack. Actually, I am trying to create an instance from the uploaded image. After successful setup of the image to create the instance, I am supposed to detach the image and attach an empty disk to the instance. The command shown above to achieve this showed success but when i shut off the instance and restarted it, i found that the setup of the instance began again. This indicates that the image was still attached to the instance and thus, the instance was always booting up from the image.

Later, i found strange behavior. I took the snapshot of the instance when the image was setup for the first time. And I terminated the instance (knowing the fact that this instance would never be persistent) and I created a new instance from the snapshot. This new instance created ... (more)

2014-03-21 07:06:18 -0500 asked a question Could not find hda disk attached: installed VM begins with setup again

HI,

I am using Packstack to try Openstack in a single node.

It is documented in Openstack installation instructions that one should attach a cdrom (named as hdc) in the place of vda to complete the setup of an instance.

I followed the exact procedures, as shown below:

Step 1: display the xml of the instance installed and get the target device, source of the running instance.

[root@localhost ~]# virsh dumpxml instance-0000001a
...
 <devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/nova/instances/8dd3023b-d61c-4394-b8d5-40a2e66985fa/disk'/>
      <target dev='hda' bus='ide' tray='open'/>
      <readonly/>
      <alias name='ide0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
...

Step 2: attach the source disk obtained from above into hda device(also obtained from above).

[root@localhost ~]# virsh attach-disk --type cdrom instance-0000001a --source /var/lib/nova/instances/8dd3023b-d61c-4394-b8d5-40a2e66985fa/disk --target hda
Disk attached successfully

And thus, the attached device should reflect as a partition. But, its nowhere. Please see below again.

[root@localhost ~]# cat /proc/partitions
major minor  #blocks  name

   7        0   21600256 loop0
   7        1    2097152 loop1
   8        0  488386584 sda
   8        1     512000 sda1
   8        2  487873536 sda2
 253        0   52428800 dm-0
 253        1    3932160 dm-1
 253        2  431509504 dm-2

I also noticed that vdb patitions are not there. Thus, when I shutdown the instance and start it again, the same setup process starts.

Please note that there is nothing worth in log files.

Please suggest me things that are taking this wrong and workarounds for the same.

Thanks in advance.

2014-03-21 00:18:01 -0500 received badge  Enthusiast
2014-03-19 01:01:09 -0500 received badge  Editor (source)
2014-03-19 00:57:22 -0500 commented question Couldn't create instance from Snapshot

@smaffulli: Thanks for replying. I have put a trace of the log above. There's nothing other than this.

2014-03-18 14:48:14 -0500 received badge  Popular Question
2014-03-18 11:38:45 -0500 received badge  Student (source)
2014-03-18 04:43:37 -0500 asked a question Couldn't create instance from Snapshot

Hi,

I am using following for testing Openstack:

  1. Packstack for single node deployment of openstack.
  2. RHEL 6.4 64bit OS
  3. 4 GB of RAM.
  4. Quad core processor
  5. 500 GB of HDD.

I have successfully deployed openstack using packstack on a single node. And I am able to add an image of RHEL 6.4 and create its instance. I could also take live snapshot of the same instance. But when I try to create instance of the snapshot taken, it begins the installation of RHEL from scratch.

PS: This problem doesn't occur with the default OS provided as cirrOS in the Openstack. In other words, I could launch an instance from snapshot of cirrOS.

As I understand, an instance created from snapshot should start like an installed OS with all its files preserved. Please note that, I have not created/attached any volume in the process.

Am i going wrong anywhere?

I would like to inform one more thing: the flavor i chose during instance creation had root disk of 40 Gb, ephemeral disk of 40gb and swap of 20 gb. But during the installation of RHEL (in VM), root disk is not listed. I mean, only ephemeral disk and swap disk is only listed. Is this a problem?

While shutting off the instance, I found that the instance is immediately destroyed. Please see below:

nova.virt.libvirt.driver [-] [instance: e7a17821-1aae-45f9-8977-a3a61e6e077b] Instance destroyed successfully.

My question, If an instance is destroyed after each shut off, then how can someone start the installed VM?

I would be very glad to know the answers of my queries.

Thanks in advance.