On Wed, Mar 17, 2010 at 05:17:38PM +0100, Matthias Bolte wrote:
> 2010/3/15 Daniel P. Berrange <berrange@xxxxxxxxxx>:
>
> So I withdraw this patch and rework the controller type handling to
> use the <controller> element.
>
> There seems to be no documentation about the <controller> element on
> the libvirt website, or do I miss something?
That is correct :-(
As an example, if you had two SCSI controllers & one IDE controller, you'd
get XML like
<controller type='scsi' index='0'/>
<controller type='scsi' index='1'/>
<controller type='ide' index='0'/>
Inside the <disk> element, you link to a controller based on its index,
using the <address> element type. If you omit '<address>' it is calculated
from the target dev name, eg sdj corresponds to controller 1, unit 2. The
automatic calculation assumes only one bus per controller.
<disk type='file' device='disk'>
<source file='/home/berrange/output.img'/>
<target dev='sdj' bus='scsi'/>
<address type='drive' controller='1' bus='0' unit='2'/>
</disk>
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list