Update:
It's a SELinux labeling problem and seems to be introduced by the
QEMU namespace patches.
On Tue, Jan 17, 2017 at 11:18 AM +0100, Marc Hartmayer <mhartmay(a)linux.vnet.ibm.com>
wrote:
Hey,
I have tried to live hot plug a disk backed on a qcow2 disk (see XML
snippet below) on a s390 system and I've got the following error
message:
<error_message>
internal error: unable to execute QEMU command 'device_add': Property
'scsi-hd.drive' can't find value 'drive-scsi0-0-0-0'
</error_message>
<xml_snippet>
<disk type="file">
<driver name="qemu" type="qcow2"/>
<source file="/tmp/virtd-test_e3hnhh5/disk1.qcow2" />
<target bus="scsi" dev="sda" />
</disk>
</xml_snippet>
With v2.5.0 everything has worked. I'll take a closer look to it today.
Thanks,
Marc
On Sat, Jan 14, 2017 at 11:02 PM +0100, Daniel Veillard <veillard(a)redhat.com>
wrote:
> I missed the Friday deadline ot push it, so did it today. It's now tagged
> in git, signed tarball and rpms are at the usual place:
>
ftp://libvirt.org/libvirt/
>
> As a result I think GA should happen on Tuesday to give at least one
> working day to raise critical issues. Nothing seems to have been reported
> on rc1 neither positive nor negative, so please give it some testing.
>
> thanks in advance,
>
> Daniel
>
> --
> Daniel Veillard | Open Source and Standards, Red Hat
> veillard(a)redhat.com | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
>
http://veillard.com/ | virtualization library
http://libvirt.org/
>
> --
> libvir-list mailing list
> libvir-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/libvir-list