Bug 1455814

Summary:	RFE: <disk> <target dev=...> should really be optional in new XML
Product:	[Community] Virtualization Tools	Reporter:	Richard W.M. Jones <rjones>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	crobinso, libvirt-maint, rbalakri
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-30 13:54:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Richard W.M. Jones 2017-05-26 08:06:02 UTC

Description of problem:

I'm trying to create a guest with 500 disks for testing, writing
the XML by hand.

I got to:

    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/home/rjones/disk1.img'/>
      <target bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/home/rjones/disk2.img'/>
      <target bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
(etc)

but then libvirt complains:

error: missing target information for device /home/rjones/disk1.img

which is technically true, but honestly couldn't libvirt just
generate those target device names?  Writing 500 of them by
hand is impossible.

Version-Release number of selected component (if applicable):

libvirt-3.2.0-3.el7.x86_64

Steps to Reproduce:
1. See above.

Comment 1 Cole Robinson 2017-05-30 13:54:04 UTC


*** This bug has been marked as a duplicate of bug 1326526 ***