<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I once had troubles with Cinder
volumes, mainly due to the fact I forgot to mention iscsi_ip_addr
in cinder.conf.<br>
After restarting Cinder, all new volumes created were fine, but
old present volumes were still pointing to the bad IP address.<br>
<br>
I then cutted with my knife in cinder mysql database ('volumes'
table) to match the right IP address for the existing volumes : <br>
mysql> select id,provider_location from volumes where
deleted=0;<br>
mysql> update volumes set provider_location='XXX' where
uuid=<volume_id><br>
sudo service cinder-api restart<br>
sudo service cinder-volume restart<br>
sudo service cinder-scheduler restart<br>
<br>
Don't also forget to restart tgt to recreate the LUN paths if
necessary.<br>
sudo tgt-admin --show<br>
sudo service tgt restart<br>
<br>
Hope it can help,<br>
-Sylvain<br>
<br>
Le 22/03/2013 01:14, Steven Barnabas a écrit :<br>
</div>
<blockquote
cite="mid:4509CEE9-516A-4C69-B689-4E6A8A84662E@frontporch.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
OK, found out my Cinder volume was not configured correctly.
Fixed that and Cinder is up and running. Created a volume and
everything is great. When i go to create my windows instance now,
I get an error. When i check /var/nova/nova-compute.log I see
this.
<div><b>"ProcessExecutionError: Unexpected error while running
command.\nCommand: sudo nova-rootwrap /etc/nova/rootwrap.conf
iscsiadm -m node -T
iqn.2010-10.org.openstack:volume-74e9c037-a681-48e2-b098-3c76bfb071f3
-p 127.0.0.1:3260 --rescan\nExit code: 255\nStdout:
''\nStderr: 'iscsiadm: No portal found.\\n'\n"]</b></div>
<div><b><br>
</b></div>
<div>The part that I think its messing up on is its trying to
connect to 127.0.0.1. When it should be connecting to the
compute box. Thats why it cannot find the portal. I have
checked my configs and cannot seem to find what I need to edit
to make this thing connect to the compute when attaching a
volume to the instance.</div>
<div><br>
</div>
<div>any ideas?</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div>Steven Barnabas<br>
Network Engineer <br>
Front Porch, Inc.<br>
209-288-5580<br>
209-652-7733 mobile<br>
<a moz-do-not-send="true" href="http://www.frontporch.com/">www.frontporch.com</a></div>
<div><br>
</div>
<br class="Apple-interchange-newline">
</div>
<br>
<div>
<div>On Mar 21, 2013, at 1:39 AM, Sylvain Bauza <<a
moz-do-not-send="true"
href="mailto:sylvain.bauza@digimind.com">sylvain.bauza@digimind.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 20/03/2013 21:11, Steven
Barnabas a écrit :<br>
</div>
<blockquote
cite="mid:B3A6D659-FA83-4228-8678-31AD67E3C58A@frontporch.com"
type="cite">
Ok, I have successfully created a windows image using an
ISO. I am going to try a different VMDK image that I
have to see if it works. If not, then I will convert it
to QCOW2 format using a different machine. I don't want
to mess up my Compute box by trying to upgrade Qemu. I
know I will mess something up :)
<div><br>
</div>
<br>
</blockquote>
<br>
Cool to hear that. Anyway, upgrading to Qemu 1.3 on Ubuntu
12.04 was pretty straight for me and not regressive :
<br>
apt-get install zlib1g-dev libsdl1.2-dev libpcap-dev
texinfo autoconf libtool build-essential<br>
wget <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://wiki.qemu-project.org/download/qemu-1.3.1.tar.bz2">
http://wiki.qemu-project.org/download/qemu-1.3.1.tar.bz2</a><br>
tar jxvf qemu-1.3.1.tar.bz2<br>
cd qemu-1.3.1<br>
./configure --target-list=x86_64-linux-user,x86_64-softmmu
# Depending on your platform of course<br>
make<br>
sudo make install<br>
<br>
It will deploy qemu in /usr/local/bin/ while the Ubuntu
qemu-1.0 package is based in /usr/bin.<br>
<br>
So as to get it work with libvirt and nova, you have to
make sure you have hvm capabilities (check with 'virsh
capabilities'), and if not, this is due to the fact that
libvirt is requesting
/usr/bin/qemu-system.<platform><br>
<br>
In order to fix this, a quick "mv
/usr/bin/qemu-system.<platform>
/usr/bin/qemu-system.<platform>.0 && mv
/usr/local/bin/qemu-system.<platform> /usr/bin' does
the trick.<br>
<br>
Hopefully, nova is following the path for qemu-img, which
makes unnecessary to switch versions as above.<br>
<br>
-Sylvain<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>