Thanks. Maybe I'm missing something but when I try virt-install --dry-run
--print-xml it generates this snippet of XML:
<interface type="bridge">
<source bridge="ge_0_0_0_77"/>
<mac address="52:54:00:01:00:4e"/>
<model type="virtio"/>
</interface>
but what i need (and get from virsh dumpxml) has this extra PCI line.
<interface type='bridge'>
<mac address='52:54:00:01:00:4e'/>
<source bridge='ge_0_0_0_77'/>
<target dev='vnet78'/>
<model type='virtio'/>
<alias name='net78'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x0a'
function='0x6' />
</interface>
Did I miss something? Do you see PCI in the XML when you do the
virt-install --dryrun approach?
Thanks
On Wed, Dec 26, 2018 at 2:57 PM Peter Crowther <peter.crowt...@melandra.com>
wrote:
> On Wed, 26 Dec 2018 at 16:26, b f31415 <bf31...@gmail.com> wrote:
>
>> If not, is there a way with one of the virt command line tools to create
>> the XML (with the PCI addresses specified) so that I can process that XML
>> and re-write the PCI addressing values? Right now the only way I’ve been
>> able to get that detailed XML file is to 1) virt-install and let the VM
>> begin the boot process and then do a 2) virsh dumpxml and then 3) virsh
>> destroy/undefine that VM, 4) modify the XML and then 5) virsh create
>> ./modified.xml. Is there a cleaner way to do this?
>>
>
> It won't do everything you want, but check out virt-install --print-step
> --dry-run. This should at least allow you to get at the XML for the
> intermediate steps and remove the brittleness of defining, destroying,
> undefining the VM.
>
> Cheers,
>
> - Peter
>
_______________________________________________
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
