<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" id="owaParaStyle" style="display: none;">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body dir="ltr" fpstyle="1" aria-label="Message body" tabindex="0">
<div name="divtagdefaultwrapper" id="divtagdefaultwrapper" style="font-family: Calibri,Arial,Helvetica,sans-serif;font-size: 12pt;color: #000000;margin: 0;">
Hello Colleagues,<br>
<br>
I have made some progress with passing through a 'raw' scsi disk from an openstack hypervisor<br>
to one of its guests. However, I've now hit a libvirt problem and am wondering whether others may<br>
have dealt with this already in the ubuntu world (I believe it is resolved in the centos world).<br>
<br>
On a (recently built) openstack-ansible 15.1.6 environment where one compute node is<br>
also a storage node I do the following:<br>
<br>
1. define an image of xenial-server with the following properties set:<br>
<br>
hw_disk_bus='scsi'<br>
hw_scsi_model='virtio-scsi'<br>
<br>
2. create a volume on a given compute node:<br>
<br>
# openstack volume create --size 269 --availability-zone special v0<br>
# openstack volume show v0 -f json | jq .id<br>
"6dc7de73-7d5b-4410-8c62-a06e722187e9"<br>
<br>
3. create an instance on the same compute node:<br>
<br>
# nova boot --flavor xenial-server --image xenial --key-name test-key \<br>
--nic net-id=0395285e-b548-458b-9db5-f8d869e49a06 --availability-zone nova:compute1 \<br>
--block-device id=6dc7de73-7d5b-4410-8c62-a06e722187e9,source=volume,dest=volume,bus=scsi,type=lun \<br>
xenial0<br>
<br>
4. Step 3 attempts to build the instance but errors out with the following in the<br>
nova-compute.log on compute1:<br>
<br>
[instance: 97b87f5e-b146-4c40-8128-44446c996b8e] libvirtError: unsupported configuration: \<br>
scsi-block 'lun' devices do not support the serial property<br>
<br>
(nb: this is the expected instance id)<br>
<br>
It seems that this is a bug in libvirt that is fixed in the centos/rhel world.<br>
<br>
The hypervisor 'compute1' is built with 16.04.2 LTS and fully updated.<br>
<br>
Does anyone know of a fix in the ubuntu/debian world?<br>
<br>
Or should I be raising this on a xenial forum?<br>
<br>
Kind regards, Lawrence<br>
<br>
Lawrence J Albinson<br>
</div>
</body>
</html>