On Wed, Oct 02, 2019 at 02:04:28PM +0200, Michal Privoznik wrote:
> On 10/2/19 1:11 PM, Daniel P. Berrangé wrote:
> > On Wed, Oct 02, 2019 at 10:45:28AM +0200, Michal Privoznik wrote:
> > > On 9/30/19 3:41 PM, Pavel Mores wrote:
> > > > The way in which the qemu driver generates aliases for disks
On 10/2/19 1:11 PM, Daniel P. Berrangé wrote:
On Wed, Oct 02, 2019 at 10:45:28AM +0200, Michal Privoznik wrote:
On 9/30/19 3:41 PM, Pavel Mores wrote:
The way in which the qemu driver generates aliases for disks involves
ignoring the partition number part of a target dev name. This means that
On Wed, Oct 02, 2019 at 10:45:28AM +0200, Michal Privoznik wrote:
> On 9/30/19 3:41 PM, Pavel Mores wrote:
> > The way in which the qemu driver generates aliases for disks involves
> > ignoring the partition number part of a target dev name. This means that
> > all partitions of a block device
On 9/30/19 3:41 PM, Pavel Mores wrote:
The way in which the qemu driver generates aliases for disks involves
ignoring the partition number part of a target dev name. This means that
all partitions of a block device and the device itself all end up with the
same alias. If multiple such disks
On Mon, Sep 30, 2019 at 03:41:00PM +0200, Pavel Mores wrote:
> The way in which the qemu driver generates aliases for disks involves
> ignoring the partition number part of a target dev name. This means that
> all partitions of a block device and the device itself all end up with the
> same
The way in which the qemu driver generates aliases for disks involves
ignoring the partition number part of a target dev name. This means that
all partitions of a block device and the device itself all end up with the
same alias. If multiple such disks are specified in XML, the resulting
name
