...
>> After looking through the code and thinking more about this - using
>> virDomainDefPostParse won't work for the hotplug case since it's only
>> going through virDomainDeviceDefParse and virDomainDeviceDefPostParse
>> code in order to validate whether the address (whether provided or
>> gen
On Tue, Aug 04, 2015 at 10:21:29AM -0400, John Ferlan wrote:
>
>
> On 08/03/2015 09:57 AM, Ján Tomko wrote:
> > On Wed, Jul 22, 2015 at 10:54:34AM -0400, John Ferlan wrote:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1210587 (completed)
> >>
> >> When generating the default drive address fo
On 08/03/2015 09:57 AM, Ján Tomko wrote:
> On Wed, Jul 22, 2015 at 10:54:34AM -0400, John Ferlan wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1210587 (completed)
>>
>> When generating the default drive address for a SCSI device,
>> check the generated address to ensure it doesn't confl
On Wed, Jul 22, 2015 at 10:54:34AM -0400, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1210587 (completed)
>
> When generating the default drive address for a SCSI device,
> check the generated address to ensure it doesn't conflict with a SCSI
> address. The address generat
https://bugzilla.redhat.com/show_bug.cgi?id=1210587 (completed)
When generating the default drive address for a SCSI device,
check the generated address to ensure it doesn't conflict with a SCSI
address. The address generation algorithm uses the
"dev" name in order to determine which controll
