virt-manager/tests/cli-test-xml/compare/virt-xml-edit-all.xml

         <vendor id="0x04b3"/>
         <product id="0x4485"/>
       </source>
+      <driver name="vfio"/>
     </hostdev>
     <hostdev mode="subsystem" type="pci" managed="yes">
       <source>
         <address domain="0x0000" bus="0x00" slot="0x19" function="0x0"/>
       </source>
       <rom bar="off"/>
+      <driver name="vfio"/>
     </hostdev>
     <redirdev bus="usb" type="tcp">
       <source mode="connect" host="localhost" service="4000"/>

Domain 'test-for-virtxml' defined successfully.
Changes will take effect after the domain is fully powered off.
virt-xml: Initial commit, basic set of tests 2014-01-19 10:37:14 -05:00			`<vendor id="0x04b3"/>`
			`<product id="0x4485"/>`
			`</source>`
			`+ <driver name="vfio"/>`
			`</hostdev>`
			`<hostdev mode="subsystem" type="pci" managed="yes">`
			`<source>`
			`<address domain="0x0000" bus="0x00" slot="0x19" function="0x0"/>`
			`</source>`
Expose hostdev rombar in UI and cli (bz 768857) 2014-02-10 14:24:22 -05:00			`<rom bar="off"/>`
virt-xml: Initial commit, basic set of tests 2014-01-19 10:37:14 -05:00			`+ <driver name="vfio"/>`
			`</hostdev>`
			`<redirdev bus="usb" type="tcp">`
			`<source mode="connect" host="localhost" service="4000"/>`

tests: Add specific VM for virtxml tests Decouple it from test-many-devices which is really about manual testing of virt-manager UI. It's annoying that every time test-many-devices is extended we need to regenerate all the virtxml tests. 2015-04-21 19:37:01 -04:00			`Domain 'test-for-virtxml' defined successfully.`
virt-xml: Make it more clear when changes take effect shutdown could be interpreted as a soft reboot, which won't apply the changes 2018-03-25 19:22:28 -04:00			`Changes will take effect after the domain is fully powered off.`