<font size=2 face="sans-serif">Also, "for the archives", the
reason you won't need rpadlpar_io module (and </font><tt><font size=2>linux-image-extra</font></tt><font size=2 face="sans-serif">-*)
on 16.10 and onwards is because ppc64-diag no longer requires it in more
recent versions.</font><br><font size=2 face="sans-serif"><br>Saudações / Best Regards,<br>--<br>Ricardo Marin Matinata<br>STSM, Linux, KVM and Cloud on POWER</font><br><font size=2 face="sans-serif">IBM Linux Technology Center | Open Systems
Development | IBM Systems</font><br><br><tt><font size=2>"Linuxppc-users" <linuxppc-users-bounces+rmm=br.ibm.com@lists.ozlabs.org>
wrote on 06/29/2017 04:08:34 PM:<br><br>> From: "Samuel D Matzek" <smatzek@us.ibm.com></font></tt><br><tt><font size=2>> To: furmanek@linux.vnet.ibm.com</font></tt><br><tt><font size=2>> Cc: linuxppc-users@lists.ozlabs.org</font></tt><br><tt><font size=2>> Date: 06/29/2017 04:15 PM</font></tt><br><tt><font size=2>> Subject: Re: [Linuxppc-users] Live VM disk removal
failure</font></tt><br><tt><font size=2>> Sent by: "Linuxppc-users" <linuxppc-users-bounces<br>> +rmm=br.ibm.com@lists.ozlabs.org></font></tt><br><tt><font size=2>> <br>> Thanks Leo, Rafael, and Jason.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Following your pointers I was able to get the
hot plug of volumes <br>> working through OpenStack.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> For the record, and mail archive searching purposes,
the Ubuntu 16.<br>> 04 cloud image from Canonical did not have ppc64-diag nor linux-<br>> image-extra-<version>-generic installed.</font></tt><br><tt><font size=2>> The cloud image already had librtas2 and powerpc-utils.
I simply <br>> did an apt-get update followed by the install of those two packages,<br>> a reboot, and live attach/detach worked.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Also of interest is that the 16.10 Yakkety image
was different:</font></tt><br><tt><font size=2>> ppc64-diag was in main and installed</font></tt><br><tt><font size=2>> linux-image-extra-<version>-generic was
NOT installed</font></tt><br><tt><font size=2>> It did not have the rpadlpar module in the file
system.</font></tt><br><tt><font size=2>> However, given rpadlpar and the linux-image-extra
package was not <br>> installed, live attach/detach works at Yakkety.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> ----- Original message -----<br>> From: Jason Furmanek <furmanek@linux.vnet.ibm.com><br>> Sent by: "Linuxppc-users" <linuxppc-users-bounces<br>> +smatzek=us.ibm.com@lists.ozlabs.org><br>> To: linuxppc-users@lists.ozlabs.org<br>> Cc:<br>> Subject: Re: [Linuxppc-users] Live VM disk removal failure<br>> Date: Thu, Jun 29, 2017 10:30 AM<br>> </font></tt><br><tt><font size=2>> One more thing:</font></tt><br><tt><font size=2>> That rpadlpar module comes along with the linux-image-extra-generic-<version>
<br>> package, so make sure to have that. (credit to Folco again on that
<br>> one - he helped me with a similar issue not long back). A lot of <br>> "minimal" cloud images don't come with the extra package.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> So for hotplug you want:</font></tt><br><tt><font size=2>> - powerpc-utils </font></tt><br><tt><font size=2>> - ppc64_diag</font></tt><br><tt><font size=2>> - librtas</font></tt><br><tt><font size=2>> - linux-image-extra-generic-<version></font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> On 06/28/2017 07:15 PM, Rafael Folco wrote:</font></tt><br><tt><font size=2>> Hi Sam,</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Xenial should hotplug pci afaik.</font></tt><br><tt><font size=2>> If I remember right, the missing package in a
base ubuntu cloud <br>> image (xenial) was ppc64-diag. Just confirm powerpc-utils and <br>> librtas are also installed. So after installing it, make sure <br>> rtas_errd service is up and running inside your guest.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> When you attach / detach using virsh or via openstack,
it will call <br>> drmgr tool under the covers, which in turn will load rpadlpar module<br>> and perform the hotplug operation.</font></tt><br><tt><font size=2>> I am not sure about min versions but latest available
in xenial 16.<br>> 04.X are enough.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Hope this helps.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> That’s All Folco’s =)</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Rafael Folco<br>> OpenStack<br>> IBM Linux Technology Center</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> On Jun 28, 2017, at 8:06 PM, Leonardo Augusto
Guimarães Garcia <<br>> lagarcia@linux.vnet.ibm.com> wrote:</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Samuel,<br>> <br>> From what you described, it doesn't seem to me, at least initially,
<br>> that you have an issue in libvirt. On Power systems, you need some
<br>> user space tools installed in the guest in order to correctly <br>> perform hot plug and hot unplug operations. It may be the case that
<br>> the tools that come installed by default in Ubuntu 14.04 and Ubuntu
<br>> 16.04 are just too old. Please, check the versions of the following
<br>> packages: powerpc-utils, ppc64_diag, and librtas.<br>> <br>> Cheers,<br>> <br>> Leo<br>> </font></tt><br><tt><font size=2>> On 06/28/2017 05:24 PM, Samuel D Matzek wrote:</font></tt><br><tt><font size=2>> I am hitting a silent error while trying to detach
a volume from a <br>> running VM on Ubuntu Xenial KVM. While I am using OpenStack
for <br>> this, the OpenStack code is calling into the libvirt module to do
<br>> the detach from the transient / live domain and libvirt is failing
<br>> to remove the disk from the running domain and is not putting any
<br>> errors in libvirtd logs.</font></tt><br><tt><font size=2>> The OpenStack error is "DeviceDetachFailed:
Device detach failed for<br>> vdb: Unable to detach from guest transient domain."</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> I have discovered this is a guest OS issue. I
tried the following <br>> guest OSes with Ubuntu Xenial as the host OS:</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Silent detach failure / fail to detach:<br>> Ubuntu 14.04 ppc64le daily build of Ubuntu cloud image<br>> Ubuntu 16.04 ppc64le daily build of Ubuntu cloud image</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Live detach succeeds:<br>> Ubuntu 16.10 ppc64le daily build of Ubuntu cloud image<br>> Ubuntu 17.04 ppc64le daily build of Ubuntu cloud image<br>> CentOS 7.3</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> What I am trying to achieve is to get the live
detach to work on <br>> Xenial (16.04) and am at a loss as to what packages or processes may<br>> be involved in the differences between 16.04 and 16.10 where it <br>> works. I have checked the kernel and both 16.04 and 16.10 are
both <br>> using a 4.8.x level.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> In all cases the disk trying to be detached is
not in use. They are<br>> blank with no file system on them. They are not mounted. The
same <br>> set of steps is taken to attach, reboot, detach, between the working<br>> and non-working OS levels above.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Does any one have hints on what could be causing
the silent detach <br>> failure on Xenial? What packages I should look at updating beyond
<br>> what the Ubuntu daily build has? Note I have already tried doing
<br>> upgrade of all packages, including updating from a recent UCA repo.</font></tt><br><tt><font size=2>> </font></tt><br><tt><font size=2>> Additionally, does anyone know what to set (and
where) to get the <br>> reason libvirt is not detaching the volume from the live domain? I
<br>> have already tried enabling the logging documented here [1].</font></tt><br><tt><font size=2>> [1] </font></tt><a href=https://wiki.libvirt.org/page/DebugLogs><tt><font size=2>https://wiki.libvirt.org/page/DebugLogs</font></tt></a><br><tt><font size=2>> </font></tt><br><tt><font size=2>> _______________________________________________<br>> Linuxppc-users mailing list<br>> Linuxppc-users@lists.ozlabs.org<br>> </font></tt><a href="https://lists.ozlabs.org/listinfo/linuxppc-users"><tt><font size=2>https://lists.ozlabs.org/listinfo/linuxppc-users</font></tt></a><br><tt><font size=2>> _______________________________________________<br>> Linuxppc-users mailing list<br>> Linuxppc-users@lists.ozlabs.org<br>> </font></tt><a href="https://lists.ozlabs.org/listinfo/linuxppc-users"><tt><font size=2>https://lists.ozlabs.org/listinfo/linuxppc-users</font></tt></a><br><tt><font size=2>> </font></tt><br><tt><font size=2>> _______________________________________________<br>> Linuxppc-users mailing list<br>> Linuxppc-users@lists.ozlabs.org<br>> </font></tt><a href="https://lists.ozlabs.org/listinfo/linuxppc-users"><tt><font size=2>https://lists.ozlabs.org/listinfo/linuxppc-users</font></tt></a><br><tt><font size=2>> </font></tt><br><tt><font size=2>> _______________________________________________<br>> Linuxppc-users mailing list<br>> Linuxppc-users@lists.ozlabs.org<br>> </font></tt><a href="https://lists.ozlabs.org/listinfo/linuxppc-users"><tt><font size=2>https://lists.ozlabs.org/listinfo/linuxppc-users</font></tt></a><br><tt><font size=2>> </font></tt><br><tt><font size=2>> _______________________________________________<br>> Linuxppc-users mailing list<br>> Linuxppc-users@lists.ozlabs.org<br>> </font></tt><a href="https://lists.ozlabs.org/listinfo/linuxppc-users"><tt><font size=2>https://lists.ozlabs.org/listinfo/linuxppc-users</font></tt></a><tt><font size=2><br></font></tt><BR>