Ask Your Question

Unable to see the attached cinder volume in instance

asked 2015-05-18 08:11:32 -0500

Nereo gravatar image

updated 2015-05-18 08:14:49 -0500

Hello, I have successfully installed OpenStack kilo + legacy networking + horizon + keystone + glance + XenServer 6.5, I have added a Cinder service it seems to be working because I can connect to my horizon (also by command line) and create volumes and attach them to my instances, this is a print screen from my horizon:

image description

Taking a look on XenCenter connected to my XenServer, seems like the ISCSI mapping is working fine, this is a print screen:

image description

The tempSR-5069766c... is the mmaping of the UbuntuDemoVolume to my UbuntuServerDemo. According to the cinder mapping information the device is mapped to xvdb, but I cant find this volume (dmesg or fdisk -l doesn't show anything), I have noticed two strange behaviors

  1. After attach the volume, boot the instance takes a lot of time.
  2. After attach the volume and after restart it (and wait a lot) the dmesg contains this:

    [ 1.243352] blkfront: xvda: barrier: enabled; persistent grants: disabled; indirect descriptors: disabled; [ 1.246056] xvda: xvda1 xvda2 xvda3 < xvda5 > [ 6.340079] xenbus_probe_frontend: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s... [ 115.140037] random: nonblocking pool is initialized [ 36.340063] 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...

If I remove the volume and reboot this is not present.

Any idea? I have read several posts some of them says that the issue is related to the type of virtualization (PV or HVM) or PV drivers (PVHVM), I don't have any error log.

Thanks in advance for your help.

edit retag flag offensive close merge delete


/var/log/messages @ XenServer 6.5 shows

May 18 13:01:04 stlab-xen03 tapback[14370]: backend.c:329 51728 error looking for tapdisk: No such process May 18 13:01:04 stlab-xen03 tapback[14370]: tapback.c:132 failed to process XenStore watch on backend/vbd3/51/51728/physical-device: No such process

Nereo gravatar imageNereo ( 2015-05-18 12:10:14 -0500 )edit

can you print your /var/log/cinder/cinder-volume.log the tempSR gets created for me but it gets deleted seconds later and the volume becomes available again. My Ubuntu controller\compute\storage nodes are running in PV mode. My instance is running HVM mode since windows only runs on HVM mode.

BuildGuru gravatar imageBuildGuru ( 2015-07-29 10:12:59 -0500 )edit

are you using CHAP auth ?

BuildGuru gravatar imageBuildGuru ( 2015-07-29 14:38:04 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-08-07 17:23:50 -0500

Nereo gravatar image

Hello, I have solved the issue:

  1. Configure cinder according to this link
  2. Login to each XenServer and do the following rm -rf /opt/xensource/sm/ISCSISR.pyo rm -rf /opt/xensource/sm/ISCSISR.pyc
  3. Open the file nano /opt/xensource/sm/

I have modified the line 110, the original line is

self.sr_vditype = 'phy'

The modified line is

self.sr_vditype = 'aio'

Now it is working perfect!

I have also update this one:

edit flag offensive delete link more


Also you have to execute cat /etc/iscsi/initiatorname.iscsi Write down all after InitiatorName= Go to XenCenter>Select the desire server>tab general> Properties and write this value in the field iSCSI IQN: Press Ok

Nereo gravatar imageNereo ( 2015-08-10 09:17:33 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-05-18 08:11:32 -0500

Seen: 721 times

Last updated: Aug 07 '15