Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Unable to see the attached cinder volume in instance

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.

Unable to see the attached cinder volume in instance

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 descriptionimage 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.