Re: [libvirt] [PATCH 2/2] qemu: always generate the same alias for tls-creds-x509 object

On 10/18/2016 10:57 AM, Pavel Hrdina wrote: > On Tue, Oct 18, 2016 at 10:37:37AM -0400, John Ferlan wrote: >> >> >> On 10/18/2016 09:58 AM, Pavel Hrdina wrote: >>> There was inconsistency between alias used to create tls-creds-x509 >>> object and alias used to link that object to chardev while

Re: [libvirt] [PATCH 2/2] qemu: always generate the same alias for tls-creds-x509 object

On Tue, Oct 18, 2016 at 10:37:37AM -0400, John Ferlan wrote: > > > On 10/18/2016 09:58 AM, Pavel Hrdina wrote: > > There was inconsistency between alias used to create tls-creds-x509 > > object and alias used to link that object to chardev while hotpluging. > > > > In XML we have for example

Re: [libvirt] [PATCH 2/2] qemu: always generate the same alias for tls-creds-x509 object

On 10/18/2016 09:58 AM, Pavel Hrdina wrote: > There was inconsistency between alias used to create tls-creds-x509 > object and alias used to link that object to chardev while hotpluging. > > In XML we have for example alias "serial0", but on qemu command line we > generate "charserial0". > >

[libvirt] [PATCH 2/2] qemu: always generate the same alias for tls-creds-x509 object

There was inconsistency between alias used to create tls-creds-x509 object and alias used to link that object to chardev while hotpluging. In XML we have for example alias "serial0", but on qemu command line we generate "charserial0". The issue was that code, that creates QMP command to hotplug