Ask Your Question

vathanlal's profile - activity

2019-12-02 11:29:12 -0600 received badge  Popular Question (source)
2019-11-05 08:54:43 -0600 asked a question How to prevent migration of vm??

Hello all,

I don't want couple of my VM's to be migrated to other hosts. Is there any option such that it prevents the VM from migrating to any other hosts from the current host it is residing??

That is even if I tried to migrate the VM it should stay on the current host it is residing without doing the migration.

2019-09-17 09:25:27 -0600 received badge  Popular Question (source)
2019-08-11 22:45:22 -0600 received badge  Famous Question (source)
2019-02-26 11:03:16 -0600 commented question Openstack create instance failing

Could you please post the contents of your linuxbridge_agent.ini fie??

2019-02-22 11:05:25 -0600 commented question Openstack create instance failing

Are you using OVS or Linux-bridge?? I hope your network type is provider + self service network. Are you trying to host the VM in self service network?? or Are you directly hosting the VM on provider network??

2019-02-22 10:52:27 -0600 commented question Snapshots taking long time

Could you please give me more details about how do you upload your docker image to the instance??

2019-02-21 05:09:11 -0600 commented question Snapshots taking long time

Please check the nova logs while doing the snapshot. Then are you trying to upload your Docker image to a public registry??

2019-02-21 05:06:02 -0600 commented question high kernel space cpu usage

Did you check whether some process is running in background all the time which causes this behavior of the cpu??

2019-02-05 23:29:33 -0600 received badge  Notable Question (source)
2019-02-05 10:05:53 -0600 commented question OpenStack cloud

Yes. You need to choose the infrastructure in which you need to setup the OpenStack cloud.

2019-02-05 08:04:52 -0600 received badge  Popular Question (source)
2019-02-05 02:47:10 -0600 commented answer How to get the ID of the router to which the VM is attached?

The problem is in step two it is difficult to find the correct router ID for openstack router show because I have plenty of routers in the project I am troubleshooting. I dont want to do openstack router show on all routers one by one to see the correct router.

2019-02-04 08:50:23 -0600 asked a question How to get the ID of the router to which the VM is attached?

Hello,

In a project in our OpenStack environment we have lot of VM's and there are couple of virtual routers also. From Horizon looking at the Network topology I can identify the ID of the router to which the VM I am trouble shooting is attached. But I want to do it from command line. Guys what is the easiest method to do this??

2019-01-25 02:04:31 -0600 commented question Not getting full bandwidth VXLAN DVR

Currently I didn't configure Jumbo frames in Neutron because the applications running inside the VM uses only 1500MTU. VM to VM(using internal IP not floating) i am getting around 2.5G/sec. The above scenario only happens when I do the test with floating ip.

2019-01-24 11:28:54 -0600 asked a question Not getting full bandwidth VXLAN DVR

Hello,

In our OpenStack environment(Newton) we are using 10G network in all our nodes. We are using OVS bridging with VXLAN tunneling and DVR. We also enabled Jumbo frames in NIC and also in physical switches. We also enabled VXLAN offloading in our NIC. irqbalance is running which suppose to distribute the network irqs to all cores of the CPU. But unfortunately we are only getting below 1G bandwidth when communicate with our VM's with floating IP's from compute hosts. We tested it using iperf and results are like below

Connecting to host 10.96.48.29, port 5201
[  4] local 10.96.32.16 port 48464 connected to 10.96.48.29 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   105 MBytes   878 Mbits/sec   14   1.14 MBytes       
[  4]   1.00-2.00   sec   102 MBytes   860 Mbits/sec    0   1.25 MBytes       
[  4]   2.00-3.00   sec   102 MBytes   860 Mbits/sec    0   1.34 MBytes       
[  4]   3.00-4.00   sec   104 MBytes   870 Mbits/sec    0   1.40 MBytes       
[  4]   4.00-5.00   sec   104 MBytes   870 Mbits/sec    0   1.45 MBytes       
[  4]   5.00-6.00   sec   104 MBytes   870 Mbits/sec    3   1.07 MBytes       
[  4]   6.00-7.00   sec   104 MBytes   870 Mbits/sec    0   1.14 MBytes       
[  4]   7.00-8.00   sec   104 MBytes   870 Mbits/sec    0   1.20 MBytes       
[  4]   8.00-9.00   sec   104 MBytes   870 Mbits/sec    0   1.26 MBytes       
[  4]   9.00-10.00  sec   104 MBytes   870 Mbits/sec    0   1.32 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.01 GBytes   869 Mbits/sec   17             sender
[  4]   0.00-10.00  sec  1.01 GBytes   867 Mbits/sec                  receiver

Host to host communication is giving about 9.5G as bandwidth. VM to VM(using internal IP not floating) i am getting around 2.5G/sec. The above scenario only happens when I do the test with floating ip. Any idea to solve this issue is much appreciated. Thanks.

2018-11-13 22:44:37 -0600 received badge  Popular Question (source)
2018-11-13 09:56:57 -0600 commented question Is it possible to create VMs with ppc64el architecture on OpenStack running on x86_64 nodes??

My qemu version is 2.10.0 and it supports power architecture (https://wiki.qemu.org/ChangeLog/2.10#...) . But I am not able to launch the VM with ppc64el architecture.

2018-11-09 09:18:08 -0600 asked a question Is it possible to create VMs with ppc64el architecture on OpenStack running on x86_64 nodes??

Hello All,

I have some use-cases which I want to test in ppc64el arch that is PowerPC architecture. As I dont have one I would like to try it with ppc64el VM's. Is it possible to run these kind of VM's on my OpenStack cluster(Queens) which runs on X86_64 architecture nodes??

I downloaded a ubuntu ppc64el image uploaded it to glance and set the image property as below.

openstack image set --property architecture=ppc64el --property hypervisor_type=qemu eb9a8c31-fa90-4714-b4c6-24ffc3ef50

Then I tried to create an instance from that image but I got the error as below

Invalid image metadata. Error: Architecture name 'ppc64el' is not valid (HTTP 400) (Request-ID: req-94dc6d64-532b-44a5-919d-b0e60a8b7010)

Then I changed the image property to architecture=ppc64 and try to launch an instance but iam getting

No valid host was found. There are not enough hosts available.

Iam using KVM as hypervisor(qemu 2.10.0). Could you please guide me to some OpenStack documentation which helps me to solve this issue??

2018-10-10 03:30:24 -0600 received badge  Famous Question (source)
2018-10-09 07:17:22 -0600 received badge  Notable Question (source)
2018-10-09 03:51:13 -0600 commented answer Floating ip

Is it possible for you to create a VM directly on the provider network and access it from outside??

2018-10-09 03:39:23 -0600 commented answer How to take snapshot of VM which is booted from volume??

Thanks. I can see that. Is there any option to download it so that it can be uploaded in other environment like normal image snapshot?? or do you know any method which I can use to move this VM snapshot(booted from volume) to a new cloud environment??

2018-10-09 03:37:16 -0600 commented question How to take snapshot of VM which is booted from volume??

openstack image show SNAPSHOT is updated in the question

2018-10-09 03:24:09 -0600 received badge  Popular Question (source)
2018-10-08 07:31:02 -0600 asked a question How to take snapshot of VM which is booted from volume??

Hello All,

In my OpenStack cluster(Newton) I have VM's which are booted from volume(Ceph based). I have one more Openstack cluster(Queens) which is completely separated from the Newton based one. I want to take the snapshot of VM's running in Newton based cluster and upload the snapshots in my Queens based cluster and create VM's out of them. But when I took snapshot of VM's which are booted from volume the snapshot size is showing 0bytes. How can I take snapshot of VM booted from volume so that I can upload it in other cluster??

openstack image show e6b67bd5-aa38-4951-89ec-1fc964f892af

+------------------+------------------------------------------------------------------------------------------------------------------------------------------------+
| Field            | Value                                                                                                                                          |
+------------------+------------------------------------------------------------------------------------------------------------------------------------------------+
| checksum         | d41d8cd98f00b204e9800998ecf8427e                                                                                                               |
| container_format | bare                                                                                                                                           |
| created_at       | 2018-10-08T08:23:18Z                                                                                                                           |
| disk_format      | qcow2                                                                                                                                          |
| file             | /v2/images/e6b67bd5-aa38-4951-89ec-1fc964f892af/file                                                                                           |
| id               | e6b67bd5-aa38-4951-89ec-1fc964f892af                                                                                                           |
| min_disk         | 0                                                                                                                                              |
| min_ram          | 0                                                                                                                                              |
| name             | TEST_Image_Master-2018-10-08-10-23                                                                                                         |
| owner            | d160f4259e2e464ea3f9fb0c7ea39571                                                                                                               |
| properties       | base_image_ref='', bdm_v2='True', block_device_mapping='[{"guest_format": null, "boot_index": 0, "delete_on_termination": false, "no_device":  |
|                  | null, "snapshot_id": "39cfe636-18b8-48aa-be3d-f0e48e135fb8", "device_name": "/dev/vda", "disk_bus": "virtio", "image_id": null, "source_type": |
|                  | "snapshot", "tag": null, "device_type": "disk", "volume_id": null, "destination_type": "volume", "volume_size": 40}]',                         |
|                  | root_device_name='/dev/vda'                                                                                                                    |
| protected        | False                                                                                                                                          |
| schema           | /v2/schemas/image                                                                                                                              |
| size             | 0                                                                                                                                              |
| status           | active                                                                                                                                         |
| tags             |                                                                                                                                                |
| updated_at       | 2018-10-08T08:23:19Z                                                                                                                           |
| virtual_size     | None                                                                                                                                           |
| visibility       | private                                                                                                                                        |
+------------------+------------------------------------------------------------------------------------------------------------------------------------------------+
2018-08-16 01:02:54 -0600 received badge  Notable Question (source)
2018-08-16 01:02:54 -0600 received badge  Famous Question (source)
2018-05-16 17:41:48 -0600 received badge  Famous Question (source)
2018-05-16 17:41:48 -0600 received badge  Popular Question (source)
2018-05-16 17:41:48 -0600 received badge  Notable Question (source)
2018-02-26 23:10:02 -0600 received badge  Famous Question (source)
2018-02-26 07:43:42 -0600 commented answer libvirt not allocating CPU and Disk to VM's after the OS update.

I used this link for customizing .xml https://ask.openstack.org/en/question... . But not working as I mentioned in above comment.

2018-02-26 07:40:25 -0600 commented answer libvirt not allocating CPU and Disk to VM's after the OS update.

But in nova console of that instance there is no error as I mentioned. It got the boot disk and IP and even boots fine then it goes to poweroff state. When I reboot the instance using nova it replaces the .xml file with scsi and again the same error.

2018-02-26 07:39:20 -0600 commented answer libvirt not allocating CPU and Disk to VM's after the OS update.

How can I edit the instance.xml file and start the VM with that xm file?? Because I edited /etc/libvirt/qemu/instance.xml to use virtio and started the VM using 'virsh start' but in horizon VM is showing powering off as task and then goes to shutdown state.

2018-02-26 06:27:56 -0600 commented answer libvirt not allocating CPU and Disk to VM's after the OS update.

I updated the logs in the question please go through it. I dont have any logs related to libvirt because in /var/log/libvirt there is libvirtd.log but nothing is actually written in this log.

2018-02-26 06:25:26 -0600 edited question libvirt not allocating CPU and Disk to VM's after the OS update.

Hello, In my OpenStack cluster(newton) after the OS update(ubuntu 16.04) of compute nodes it is not possible to create new VM's. When I create a new VM it is showing in horizon as active and IP is also shown as allocated to the VM in the horizon. But ssh into the VM is not possible. Then I check the console log of the VMs and I found error related to root disk as below

 Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  LABEL=cloudimg-rootfs does not exist.  Dropping to a shell!


BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) [6n[  963.757213] random: nonblocking pool is initialized

After Inspecting libvirt in compute nodes I found all my newly created VM's are using sda and scsi and all of them have the above same error. All the VM's which I created before the update is working fine and is using vda and virtio. Then I checked the libvirt instance.xml file and I found libvirt is not allocating CPU to the VM's and it always using sda and scsi. I think this happened due to the OS update. How can I solve this issue?? any help is really appreciated. one of the instance.xml is as below

<domain type='kvm'>
  <name>instance-00000081</name>
  <uuid>d7c2feae-ce57-4492-b892-35b86d1559f6</uuid>
  <metadata>
    <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0">
      <nova:package version="14.0.10"/>
      <nova:name>testingimage</nova:name>
      <nova:creationTime>2018-02-13 13:47:56</nova:creationTime>
      <nova:flavor name="m1.small">
        <nova:memory>1024</nova:memory>
        <nova:disk>10</nova:disk>
        <nova:swap>0</nova:swap>
        <nova:ephemeral>0</nova:ephemeral>
        <nova:vcpus>1</nova:vcpus>
      </nova:flavor>
      <nova:owner>
        <nova:user uuid="b378a2ff41af45bc8e458a2f17c30c3f">vmsec</nova:user>
        <nova:project uuid="7814cec0fc1943b6b08a1a052ffeb4f7">vmsec</nova:project>
      </nova:owner>
      <nova:root type="image" uuid="790b87d7-e345-47a8-9d5e-f7bcc6f7202b"/>
    </nova:instance>
  </metadata>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <cputune>
    <shares>1024</shares>
  </cputune>
  <sysinfo type='smbios'>
    <system>
      <entry name='manufacturer'>OpenStack Foundation</entry>
      <entry name='product'>OpenStack Nova</entry>
      <entry name='version'>14.0.10</entry>
      <entry name='serial'>5b8fe22f-532c-4114-b52a-905b91050f9b</entry>
      <entry name='uuid'>d7c2feae-ce57-4492-b892-35b86d1559f6</entry>
      <entry name='family'>Virtual Machine</entry>
    </system>
  </sysinfo>
  <os>
    <type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
    <boot dev='hd'/>
    <smbios mode='sysinfo'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-model'>
    <model fallback='allow'/>
    <topology sockets='1' cores='1' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/kvm-spice</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var ...
(more)