<div dir="ltr">Great, there're working on it, that's good. It's not a big problem. Thanks Andrew!</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/4/10 Andrew Glen-Young <span dir="ltr"><<a href="mailto:andrew.glen-young@canonical.com" target="_blank">andrew.glen-young@canonical.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<div><div class="h5"><br>
On Wed 10-04-2013 14:38 ›, Juan José Pavlik Salles wrote:<br>
> Hi after a couple of problems between tgtd and ited i managed to create and<br>
> attach volumes to the VMs. But i came into something strange, when i attach<br>
> a volume from the dashboard i can select the device, for instance /dev/vdc,<br>
> but after attaching it in the VM, the new device is /dev/vdb. It works<br>
> great i could r/w without any problems. Cheers!<br>
<br>
</div></div>This is a known bug[1] when using KVM/QEMU. I believe that there are<br>
discussions of how to fix this in a hypervisor agnostic way, but I do<br>
not know what the ETA is on a fix.<br>
<br>
[1]: <a href="https://bugs.launchpad.net/nova/+bug/1088430" target="_blank">https://bugs.launchpad.net/nova/+bug/1088430</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Regards.<br>
Andrew Glen-Young<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Pavlik Juan José
</div>