openkylin
/
virt-manager
mirror of https://gitee.com/openkylin/virt-manager.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity
virt-manager/tests/testdriver.xml

3555 lines
88 KiB
XML
Raw Normal View History

Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<node>
<cpu>
<nodes>1</nodes>
<sockets>4</sockets>
<cores>4</cores>
<threads>1</threads>
<active>4</active>
<mhz>4000</mhz>
<model>i686</model>
</cpu>
<memory>10000000</memory>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- ####### -->
<!-- Domains -->
<!-- ####### -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<domain type='test'>
<name>test</name>
<uuid>4a64cc71-19c4-2fd0-2323-3050941ea3c3</uuid>
<memory>8388608</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='i686'>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
</devices>
</domain>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<domain type='test'>
<name>test-arm-kernel</name>
<memory>8388608</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
testdriver: Add a host-model and host-passthrough usage
2014-09-21 22:17:51 +08:00
<cpu mode='host-passthrough'/>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<os>
<type arch="i686">hvm</type>
<kernel>/dev/default-pool/test-arm-kernel</kernel>
<initrd>/dev/default-pool/test-arm-initrd</initrd>
<dtb>/dev/default-pool/test-arm-dtb</dtb>
<cmdline>console=ttyAMA0 rw root=/dev/vda3</cmdline>
</os>
</domain>
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-22 07:37:01 +08:00
<domain type='test'>
<name>test-many-devices</name>
guest: Encode the cli --os-variant in the XML And add some testdriver examples of it
2018-09-14 03:11:22 +08:00
<metadata>
<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
details: Add OS name view/edit, + oslist rework This is just a big nasty commit. Turn the OS inspection page into an always available page that shows the libosinfo name from the domain metadata XML. Use oslist.py and have it absorb more of the common behavior needed by create.py and details.py. Add UI tests for it all
2018-09-30 04:04:05 +08:00
<libosinfo:os id="http://fedoraproject.org/fedora/unknown"/>
guest: Encode the cli --os-variant in the XML And add some testdriver examples of it
2018-09-14 03:11:22 +08:00
</libosinfo:libosinfo>
</metadata>
testdriver: Add genid example Signed-off-by: Lin Ma <lma@suse.com>
2019-03-26 17:42:34 +08:00
<genid>e90ff655-47a5-4484-9f9c-79a683c2a2e2</genid>
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-22 07:37:01 +08:00
<currentMemory>204800</currentMemory>
<memory>409600</memory>
<blkiotune>
<weight>100</weight>
<device>
<path>/dev/sdd</path>
<weight>200</weight>
</device>
</blkiotune>
<memoryBacking>
<hugepages/>
</memoryBacking>
<uuid>12345678-12F4-1234-1234-A23456A89012</uuid>
tests: testdriver: add <sysinfo> example
2016-07-19 00:13:04 +08:00
<sysinfo type='smbios'>
<bios>
<entry name='vendor'>LENOVO</entry>
<entry name='version'>6FET82WW (3.12 )</entry>
<entry name='date'>01/12/2010</entry>
<entry name='release'>3.18</entry>
</bios>
<system>
<entry name='manufacturer'>Fedora</entry>
<entry name='product'>Virt-Manager</entry>
<entry name='version'>0.8.2-3.fc14</entry>
<entry name='serial'>32dfcb37-5af1-552b-357c-be8c3aa38310</entry>
<entry name='uuid'>12345678-12F4-1234-1234-A23456A89012</entry>
<entry name='sku'>1234567890</entry>
<entry name='family'>Red Hat</entry>
</system>
<baseBoard>
<entry name='manufacturer'>Hewlett-Packard</entry>
<entry name='product'>0B4Ch</entry>
<entry name='version'>D</entry>
<entry name='serial'>CZC1065993</entry>
<entry name='asset'>CZC1065993</entry>
<entry name='location'>Upside down</entry>
</baseBoard>
</sysinfo>
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-22 07:37:01 +08:00
<os>
<type arch='i686'>hvm</type>
uitests: Add details->rename tests
2017-03-09 02:08:22 +08:00
<loader readonly='yes' type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.fd</loader>
<nvram>/nvram/test-many-devices_VARS.fd</nvram>
tests: testdriver: add <sysinfo> example
2016-07-19 00:13:04 +08:00
<smbios mode='sysinfo'/>
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-22 07:37:01 +08:00
</os>
<idmap>
<uid start='0' target='1000' count='10'/>
<gid start='0' target='1000' count='10'/>
</idmap>
<description>Test VM for virt-manager details UI testing
Foo bar baz &amp; yeah boii &lt; &gt; yeahfoo
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</description>
<features>
virt-xml: Initial commit, basic set of tests
2014-01-19 23:37:14 +08:00
<acpi/>
<apic eoi='off'/>
<hyperv>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='12287'/>
</hyperv>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</features>
virt-xml: Initial commit, basic set of tests
2014-01-19 23:37:14 +08:00
<clock offset="utc">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
</clock>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
guest: Don't set any defaults for on_* Currently we hardcode these defaults for installing VMs: <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> And these for post-install config: <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> But this has some issues. on_crash=restart is problematic in that most configs don't support it, and some like virtuozzo actively reject it. Additionally this we should leave as much to libvirt defaults as we can, which are more sensible in this case. Drop everything except setting on_reboot=destroy for the install time case (which is required for our config changes). Since on_poweroff and on_crash already default to 'destroy', the install time config is unchanged, and the post-install config now on_crash=destroy instead of 'restart'. The s390 on_crash=preserve workaround is dropped, which was intended to avoid a reboot loop caused by on_crash=reboot
2017-02-21 22:27:56 +08:00
<on_crash>destroy</on_crash>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<vcpu cpuset="1,2,5-9,11,13-14">9</vcpu>
virt-xml: Initial commit, basic set of tests
2014-01-19 23:37:14 +08:00
<numatune>
<memory mode='interleave' placement='auto'/>
</numatune>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<cpu match="exact">
<model>core2duo</model>
<vendor>Intel</vendor>
<feature policy="require" name="pbe"/>
<feature policy="require" name="tm2"/>
<feature policy="require" name="est"/>
<feature policy="require" name="ss"/>
<feature policy="require" name="ht"/>
<feature policy="require" name="ds"/>
<feature policy="require" name="lahf_lm"/>
<feature policy="require" name="tm"/>
<feature policy="require" name="cx16"/>
<feature policy="require" name="vmx"/>
<feature policy="require" name="ds_cpl"/>
<feature policy="require" name="xtpr"/>
<feature policy="require" name="acpi"/>
</cpu>
virt-install: Add --pm option
2014-02-03 05:12:29 +08:00
<pm>
<suspend-to-mem enabled='no'/>
</pm>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<!-- disk devices
Keep these ordered in the same order as libvirt. Which
is by bus: fdc, ide, scsi, virtio, usb, xen
-->
<!-- bus fdc -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='block' device='floppy'>
Remove 'Choose CD', rework details and create media change The new UI is handled in mediacombo. It's a combobox+entry. The combobox is prepopulated with host cdrom/floppy devices, and previously used media paths from gsettings The new VM wizard no longer has separate UI for cdrom device vs ISO media. The choosecd dialog is gone all together, and media is changed with the 'apply' button like all other details changes
2018-10-07 02:26:31 +08:00
<source dev='/dev/fda'>
disk: Support <seclabel> overrides
2015-09-06 02:40:45 +08:00
<seclabel model='selinux' relabel='no'/>
<seclabel model='dac' relabel='no'/>
</source>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<target dev='fda' bus='fdc'/>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='5'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</disk>
<disk type='dir' device='floppy'>
<source dir='/tmp'/>
<target dev='fdb' bus='fdc'/>
</disk>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<!-- bus ide -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='file' device='disk'>
<source file='/tmp/foobar'/>
<target dev='hda' bus='ide'/>
<iotune>
<read_bytes_sec>5242880</read_bytes_sec>
<total_iops_sec>50</total_iops_sec>
</iotune>
</disk>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<disk type='file' device='cdrom'>
<source startupPolicy='requisite'/>
<target dev='hdb' bus='ide'/>
</disk>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='block' device='disk'>
<driver cache='none' type="raw"/>
Fix tests on f20, /dev/loop0 isn't available
2013-09-26 07:35:05 +08:00
<source dev='/dev/null'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<target dev='hdc' bus='ide'/>
</disk>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<!-- bus scsi -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='block' device='cdrom'>
<target dev='sdb' bus='scsi'/>
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
<address type='drive' controller='5'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</disk>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='file' device='disk'>
<driver name="qemu" type="qcow2" cache="none"/>
Remove 'Choose CD', rework details and create media change The new UI is handled in mediacombo. It's a combobox+entry. The combobox is prepopulated with host cdrom/floppy devices, and previously used media paths from gsettings The new VM wizard no longer has separate UI for cdrom device vs ISO media. The choosecd dialog is gone all together, and media is changed with the 'apply' button like all other details changes
2018-10-07 02:26:31 +08:00
<source file='/tmp/foobar2/this_is_a_really_long_path_to_see_how_the_ui_handles_it/hopefully_it_doesnt_mess_things_up_too_bad/i_guess_we_will_see/in_fact_can_we_see_this_filename.img'/>
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
<target dev='sda' bus='scsi'/>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='1'/>
testdriver: add missing addrStr for scsi disk Signed-off-by: Lin Ma <lma@suse.com>
2017-11-06 20:52:08 +08:00
<address type='drive' controller='9' bus='0' target='0' unit='0'/>
cli: Add --disk readonly and shareable options This deprecates the difficult perms= sub option
2014-01-25 08:05:04 +08:00
<shareable/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</disk>
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
tests: Add test-many-devices disk device=lun example
2018-10-12 04:09:55 +08:00
<disk type='block' device='lun' rawio='no' sgio='unfiltered'>
<driver name='qemu' type='raw'/>
<source dev='/dev/szz'>
<reservations managed="yes"/>
</source>
<target dev='sdc' bus='scsi'/>
</disk>
virt-install: set_install_defaults before disk validation So we validate the CDROM disk contents too. This revealed we were using a cdrom path in the test driver that was assigned as a writeable disk to another test VM, which is a correct warning, so fix the fallout, and ensure that we don't warn when colliding with another cdrom device
2019-02-08 04:00:27 +08:00
<disk type='file' device='cdrom'>
<source file='/dev/default-pool/testvol2.img'/>
<target dev='sdf' bus='scsi'/>
<readonly/>
</disk>
tests: Add test-many-devices disk device=lun example
2018-10-12 04:09:55 +08:00
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
<!-- bus virtio -->
virtinst: add support for disk type="volume" Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-09-26 21:24:34 +08:00
<disk type="volume" device="disk">
<driver name="qemu"/>
virt-install: Support --disk source_pool,source_volume For setting type=volume disks. This requires some reworking of devicedisk bits
2014-12-07 05:22:00 +08:00
<source pool="rbd-ceph" volume="vol1"/>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<target dev="vdb" bus="virtio"/>
virtinst: add support for disk type="volume" Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-09-26 21:24:34 +08:00
<readonly/>
</disk>
devicedisk: Never raise error for missing TYPE_VOLUME We can't predict when it's expected or not, so just never raise the error and let libvirt error if the user is trying do things at create time.
2014-12-11 02:11:18 +08:00
<disk type="volume" device="disk">
<driver name="qemu"/>
<source pool="idontexist" volume="vol1"/>
<target dev="vdc" bus="virtio"/>
<readonly/>
</disk>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='http' name='/my-file.img'>
<host name='example.org'/>
</source>
<target dev='vdaa' bus='virtio'/>
</disk>
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='nbd'>
<host transport='unix' socket='/var/run/nbdsock'/>
</source>
<target dev='vdab' bus='virtio'/>
</disk>
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='rbd' name='pool/image'>
<host name='mon1.example.org' port='6321'/>
<host name='mon2.example.org' port='6322'/>
<host name='mon3.example.org' port='6322'/>
</source>
<target dev='vdac' bus='virtio'/>
</disk>
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='sheepdog' name='image,with,commas'>
<host name='example.org' port='6000'/>
</source>
<target dev='vdad' bus='virtio'/>
</disk>
testdriver: Add more gluster examples
2014-12-11 01:42:03 +08:00
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='gluster' name='test-volume/test-gluster2.raw'>
<host name='192.168.1.100'/>
</source>
<target dev='vdae' bus='virtio'/>
</disk>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<!-- bus usb -->
details: Use devicedisk path lookup for source_pool
2015-09-06 05:59:47 +08:00
<disk type='volume' device='disk'>
<source pool='default-pool' volume='overlay.img'/>
tests: Order disks in same order libvirt shows them
2014-12-07 05:42:39 +08:00
<target dev='sdd' bus='usb'/>
</disk>
<!-- bus xen -->
<disk type='file' device='disk'>
<driver name='tap' type='qcow' cache="writethrough"/>
<source file='/tmp/foobar4'/>
<target dev='xvdc' bus='xen'/>
</disk>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
<!-- controllers -->
<controller type='scsi' index='9' model='virtio-scsi'/>
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-22 07:37:01 +08:00
<controller type='scsi' model='virtio-scsi'/>
<controller type='usb'/>
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- interfaces -->
<interface type='network'>
<source network='default'/>
<mac address='22:22:33:54:32:10'/>
<model type='e1000'/>
</interface>
<interface type='network'>
<source network='idontexistfool'/>
virt-xml: Initial commit, basic set of tests
2014-01-19 23:37:14 +08:00
<mac address='22:11:11:11:11:11'/>
tests: Don't use bogus net model names Libvirt is rejecting them now
2019-04-17 22:07:35 +08:00
<model type='Am79C970A'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</interface>
<interface type='network'>
<source network='dupmac'/>
<mac address='22:22:33:54:32:11'/>
</interface>
virt-xml: Initial commit, basic set of tests
2014-01-19 23:37:14 +08:00
<interface type='user'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<interface type='bridge'>
<source bridge='brempty'/>
<mac address='22:22:33:44:AA:BB'/>
<model type='virtio'/>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='123'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</interface>
<interface type='bridge'>
<source bridge='br0'/>
<mac address='22:00:00:44:AA:BF'/>
<model type='e1000'/>
</interface>
<interface type='ethernet'>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<mac address='00:11:7f:33:44:55'/>
<script path='/etc/qemu-ifup'/>
<target dev='nic02'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</interface>
<interface type="direct">
<mac address="F0:11:22:33:44:5F"/>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='3'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<source dev="eth0.1" mode="vepa"/>
<virtualport type="802.1Qbg">
<parameters managerid="12" typeid="1193046" typeidversion="1" instanceid="09b11c53-8b5c-4eeb-8f00-d84eaa0aaa3b"/>
</virtualport>
<address type="pci" domain="0x0000" bus="0x00" slot="0x07" function="0x0"/>
</interface>
testdriver: Add vhostuser example Signed-off-by: Lin Ma <lma@suse.com>
2017-10-20 17:08:27 +08:00
<interface type="vhostuser">
<source type="unix" path="/tmp/vhost1.sock" mode="server"/>
<mac address="00:11:22:33:44:66"/>
<model type="virtio"/>
</interface>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- input devices -->
<input type='mouse' bus='ps2'/>
<input type='tablet' bus='usb'/>
details: Improve UI labeling of keyboard devices
2015-04-10 01:36:40 +08:00
<input type='keyboard' bus='usb'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- Graphics devices -->
doc: remove reference to SDL from virt-install man page Adjust some tests to not use --graphics sdl. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-02-06 19:12:12 +08:00
<graphics type='vnc' display=':3.4' xauth='/testdir/.Xauthority' fullscreen='yes'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<graphics type='vnc'/>
<graphics type='vnc' listen="1.2.3.4" keymap="fi"/>
<graphics type='vnc' port="5903" passwd="foobar"/>
<graphics type='rdp'/>
Move shared graphics editing UI to gfxdetails.py Fixes a couple UI bugs: https://bugzilla.redhat.com/show_bug.cgi?id=696217 https://bugzilla.redhat.com/show_bug.cgi?id=875403
2014-01-29 07:44:40 +08:00
<graphics type='spice' autoport='yes' passwd=''/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<graphics type="spice" passwd="newpass" port="6000" tlsPort="6001" listen="1.2.3.4">
<channel name="inputs" mode="secure"/>
<channel name="main" mode="any"/>
<channel name="record" mode="insecure"/>
</graphics>
<!-- sound devices -->
<sound model='sb16'/>
<sound model='es1370'/>
<sound model='ich6'/>
<!-- Video devices -->
<video>
<model type='vmvga'/>
</video>
<video>
<model type='cirrus' vram='10240' heads='3'/>
</video>
<!-- hostdev devices -->
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x04b3'/>
<product id='0x4485'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<address bus='0x03' device='0x02'/>
</source>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='9'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address bus='0x00' slot='0x19' function="0x0"/>
</source>
Expose hostdev rombar in UI and cli (bz 768857)
2014-02-11 03:24:22 +08:00
<rom bar='off'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain="0x03" bus='0x00' slot='0x19' function="0x0"/>
</source>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='6'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</hostdev>
virt-install: Support --hostdev scsi passthrough (bz 1054912) Pass it a type=scsi nodedev name, and we will set things up correctly.
2015-04-12 03:52:42 +08:00
<hostdev mode="subsystem" type="scsi" managed="no">
<source>
<adapter name="scsi_host0"/>
<address bus="0" target="0" unit="0"/>
</source>
</hostdev>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
testdriver: Add some <console> devices
2013-10-05 23:07:05 +08:00
<!-- serial devices -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<serial type='null'/>
<serial type='tcp'>
<source mode='bind' host='my.source.host' service='1234'/>
<protocol type='telnet'/>
</serial>
devicechar: Support source_master and source_slave Needed for type=nvdm for *bsd https://bugzilla.redhat.com/show_bug.cgi?id=1369803
2016-08-25 04:37:36 +08:00
<serial type="nmdm">
<source master="/dev/nmdm0A" slave="/dev/nmdm0B"/>
</serial>
testdriver: Add some <console> devices
2013-10-05 23:07:05 +08:00
<!-- parallel devices -->
<parallel type='file'>
<source path='/tmp/foo.log'/>
</parallel>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<parallel type='unix'>
<source mode='bind' path='/tmp/foobar'/>
</parallel>
<parallel type='udp'>
<source mode='bind' host='my.bind.host' service='1111'/>
<source mode='connect' host='my.source.host' service='2222'/>
</parallel>
testdriver: Add some <console> devices
2013-10-05 23:07:05 +08:00
<!-- console devices -->
<console type='pty'>
<target type='virtio'/>
</console>
<console type='pty'>
<target type='uml'/>
</console>
<!-- channel devices -->
<channel type='pipe'>
<source path='/tmp/guestfwd'/>
<target type='guestfwd' address='10.0.2.1' port='4600'/>
</channel>
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0'/>
<address type='virtio-serial' controller='1' bus='0' port='3'/>
</channel>
<channel type='pty'>
details: If we know the channel target name, pretty list it
2013-10-06 02:04:49 +08:00
<target type='virtio' name='org.qemu.guest_agent.0'/>
</channel>
<channel type='unix'>
<source mode='bind'/>
<target type='virtio' name='org.libguestfs.channel.0'/>
testdriver: Add some <console> devices
2013-10-05 23:07:05 +08:00
</channel>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- watchdog devices -->
<watchdog model='ib700' action='poweroff'/>
<!-- smartcard devices -->
<smartcard mode='host'>
<address type='ccid' controller='0' slot='0'/>
</smartcard>
<smartcard mode='host-certificates'>
<certificate>cert1</certificate>
<certificate>cert2</certificate>
<certificate>cert3</certificate>
</smartcard>
<smartcard mode='passthrough' type='spicevmc'/>
<smartcard mode='passthrough' type='tcp'>
<source mode='bind' host='127.0.0.1' service='2001'/>
<protocol type='raw'/>
</smartcard>
<!-- redir devices -->
<redirdev bus='usb' type='tcp'>
<source mode='connect' host='localhost' service='4000'/>
<protocol type='raw'/>
</redirdev>
<redirdev bus='usb' type='spicevmc'>
<address type='usb' bus='0' port='4'/>
cli: Support per-device <boot order=>
2014-02-10 02:36:12 +08:00
<boot order='7'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</redirdev>
<redirfilter>
<usbdev class='0x08' vendor='0x15E1' product='0x2007' version='1.10' allow='yes'/>
<usbdev class='-1' vendor='-1' product='-1' version='-1' allow='no'/>
</redirfilter>
testdriver: Add <filesystem> examples
2013-12-03 02:47:09 +08:00
<!-- filesystems -->
<filesystem>
<driver type='handle'/>
testdriver: Use different filesystem targets for test-many-devices To differentiate in the virt-manager UI
2015-09-21 08:15:12 +08:00
<source dir='/foo/bar1'/>
<target dir='/target/1'/>
testdriver: Add <filesystem> examples
2013-12-03 02:47:09 +08:00
</filesystem>
<filesystem type='template'>
<source name='template_fedora'/>
testdriver: Use different filesystem targets for test-many-devices To differentiate in the virt-manager UI
2015-09-21 08:15:12 +08:00
<target dir='/target/2'/>
testdriver: Add <filesystem> examples
2013-12-03 02:47:09 +08:00
</filesystem>
<filesystem type='mount' accessmode='squash'>
<driver type='path' wrpolicy='immediate'/>
testdriver: Use different filesystem targets for test-many-devices To differentiate in the virt-manager UI
2015-09-21 08:15:12 +08:00
<source dir='/foo/bar3'/>
<target dir='target3'/>
testdriver: Add <filesystem> examples
2013-12-03 02:47:09 +08:00
</filesystem>
<filesystem type='mount' accessmode='mapped'>
<driver type='path'/>
testdriver: Use different filesystem targets for test-many-devices To differentiate in the virt-manager UI
2015-09-21 08:15:12 +08:00
<source dir='/foo/bar4'/>
<target dir='/target4'/>
testdriver: Add <filesystem> examples
2013-12-03 02:47:09 +08:00
</filesystem>
fsdetails: Fix displaying filesystem type=ram devices And add a test XML example to demonstrate it
2017-06-28 02:08:44 +08:00
<filesystem type='ram'>
<source usage='8192' units='KiB'/>
<target dir='/run'/>
</filesystem>
fsdetails: Use combo entry for format list And stop listing all the crazy qemu formats
2018-09-06 08:13:56 +08:00
<filesystem type='file' accessmode='passthrough'>
<driver type='nbd' format='vmdk'/>
<source file='/root/container.vmdk'/>
<target dir='/home'/>
</filesystem>
testdriver: Add <filesystem> examples
2013-12-03 02:47:09 +08:00
Minor TPM UI fixups
2013-06-27 08:05:32 +08:00
<!-- tpm devices -->
<tpm model='tpm-tis'>
<backend type='passthrough'>
VirtualTPM: Convert to new style properties
2013-07-16 00:18:23 +08:00
<device path='/dev/tzz'/>
Minor TPM UI fixups
2013-06-27 08:05:32 +08:00
</backend>
</tpm>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
virtinst: add support for virtio-rng devices The virtio-rng device is supported by libvirt since version 1.0.3. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-18 21:29:28 +08:00
<!-- rng devices -->
<rng model='virtio'>
<rate period='2000' bytes='1234'/>
<backend model='egd' type='tcp'>
<source mode='connect' host='1.2.3.4' service='1234'/>
</backend>
</rng>
virtinst: add support for panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:54 +08:00
<!-- panic notifier devices -->
<panic>
<address type='isa' iobase='0x505'/>
</panic>
tests: Add multi <panic> example
2017-09-16 07:33:22 +08:00
<panic model='s390'/>
<panic model='pseries'/>
<panic model='hyperv'/>
virt-xml: Initial commit, basic set of tests
2014-01-19 23:37:14 +08:00
<!-- memballoon device -->
<memballoon model='virtio'/>
testdriver: Add vsock example
2019-01-07 07:08:04 +08:00
<!-- vsock device -->
<vsock model='virtio'>
<cid address='5'/>
</vsock>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</devices>
virtinst: Support multiple seclabels libvirt has supported this for a while. Wire it all up through the cli, and fix some bad assumptions along the way.
2015-05-04 06:08:10 +08:00
disk: Support <seclabel> overrides
2015-09-06 02:40:45 +08:00
<seclabel model='selinux' type='dynamic' relabel='yes'/>
<seclabel model='dac' type='static' relabel='yes'>
<label type='qemu'>107:107</label>
</seclabel>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</domain>
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-22 07:37:01 +08:00
testdriver: Add test-alternate-devs guest for alternate rng config
2013-09-24 07:59:42 +08:00
<domain type='test'>
<name>test-alternate-devs</name>
<uuid>4a64cc71-19c4-2fd0-2323-00aa941ea3c3</uuid>
<description>Test alternate devices that can't be crammed in
details: Add OS name view/edit, + oslist rework This is just a big nasty commit. Turn the OS inspection page into an always available page that shows the libosinfo name from the domain metadata XML. Use oslist.py and have it absorb more of the common behavior needed by create.py and details.py. Add UI tests for it all
2018-09-30 04:04:05 +08:00
test-many-devices, like an alternate RNG, EOL OS ID, title field
testdriver: Add test-alternate-devs guest for alternate rng config
2013-09-24 07:59:42 +08:00
</description>
domain: If title present, print only it Forcing the name to be in the picture reduces the usefulness IMO
2013-10-04 23:50:19 +08:00
<title>test alternate devs (title)</title>
details: Add OS name view/edit, + oslist rework This is just a big nasty commit. Turn the OS inspection page into an always available page that shows the libosinfo name from the domain metadata XML. Use oslist.py and have it absorb more of the common behavior needed by create.py and details.py. Add UI tests for it all
2018-09-30 04:04:05 +08:00
<metadata>
<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
<libosinfo:os id="http://microsoft.com/msdos/6.22"/>
</libosinfo:libosinfo>
</metadata>
testdriver: Add test-alternate-devs guest for alternate rng config
2013-09-24 07:59:42 +08:00
<memory>8388608</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
testdriver: Add a host-model and host-passthrough usage
2014-09-21 22:17:51 +08:00
<cpu mode='host-model'/>
testdriver: Add test-alternate-devs guest for alternate rng config
2013-09-24 07:59:42 +08:00
<os>
<type arch='i686'>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<rng model='virtio'>
<rate bytes='123' period='1234'/>
<backend model='random'>/dev/hwrng</backend>
</rng>
</devices>
</domain>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
details: Add OS name view/edit, + oslist rework This is just a big nasty commit. Turn the OS inspection page into an always available page that shows the libosinfo name from the domain metadata XML. Use oslist.py and have it absorb more of the common behavior needed by create.py and details.py. Add UI tests for it all
2018-09-30 04:04:05 +08:00
tests: make test-clone VMs offline by default Simplifies test cases
2017-03-07 04:46:39 +08:00
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<test:runstate>5</test:runstate>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>test-clone-simple</name>
<currentMemory>204800</currentMemory>
<memory>409600</memory>
<uuid>12345678-1234-FFFF-1234-12345678FFFF</uuid>
<os>
<type arch='i686'>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='hd'/>
</os>
<features>
<acpi/><apic/>
</features>
<clock offset="utc"/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
guest: Don't set any defaults for on_* Currently we hardcode these defaults for installing VMs: <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> And these for post-install config: <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> But this has some issues. on_crash=restart is problematic in that most configs don't support it, and some like virtuozzo actively reject it. Additionally this we should leave as much to libvirt defaults as we can, which are more sensible in this case. Drop everything except setting on_reboot=destroy for the install time case (which is required for our config changes). Since on_poweroff and on_crash already default to 'destroy', the install time config is unchanged, and the post-install config now on_crash=destroy instead of 'restart'. The s390 on_crash=preserve workaround is dropped, which was intended to avoid a reboot loop caused by on_crash=reboot
2017-02-21 22:27:56 +08:00
<on_crash>destroy</on_crash>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<vcpu>5</vcpu>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<disk type='file' device='disk'>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<source file='/dev/default-pool/test-clone-simple.img'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<target dev='hda' bus='ide'/>
details: Disable snapshot buttons if conn or guest doesn't have support
2013-10-01 08:33:42 +08:00
<driver type="qcow2"/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</disk>
<interface type='user'>
<mac address='22:11:11:11:11:11'/>
</interface>
<parallel type='file'>
<source path='/tmp/foo.log'/>
</parallel>
</devices>
</domain>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
tests: make test-clone VMs offline by default Simplifies test cases
2017-03-07 04:46:39 +08:00
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<test:runstate>5</test:runstate>
tests: Rename clone test VMs to have a common "test-clone" prefix
2017-03-07 04:35:02 +08:00
<name>test-clone</name>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<currentMemory>204800</currentMemory>
<memory>409600</memory>
<uuid>12345678-1234-1234-1234-12345678FFFF</uuid>
<os>
<type arch='i686'>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='hd'/>
</os>
<features>
<acpi/><apic/>
</features>
<clock offset="utc"/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
guest: Don't set any defaults for on_* Currently we hardcode these defaults for installing VMs: <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> And these for post-install config: <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> But this has some issues. on_crash=restart is problematic in that most configs don't support it, and some like virtuozzo actively reject it. Additionally this we should leave as much to libvirt defaults as we can, which are more sensible in this case. Drop everything except setting on_reboot=destroy for the install time case (which is required for our config changes). Since on_poweroff and on_crash already default to 'destroy', the install time config is unchanged, and the post-install config now on_crash=destroy instead of 'restart'. The s390 on_crash=preserve workaround is dropped, which was intended to avoid a reboot loop caused by on_crash=reboot
2017-02-21 22:27:56 +08:00
<on_crash>destroy</on_crash>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<vcpu>5</vcpu>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='block' device='floppy'>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<source dev='/dev/disk-pool/diskvol1'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<target dev='fda' bus='fdc'/>
CloneManager: Make sure to sync driver_name
2013-07-15 03:53:23 +08:00
<driver type="vmdk"/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</disk>
<disk type='block' device='disk'>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<source dev='/dev/disk-pool/diskvol2'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<target dev='sda' bus='scsi'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<readonly/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</disk>
<disk type='block' device='cdrom'>
<target dev='sdb' bus='scsi'/>
</disk>
<disk type='block' device='disk'>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<source dev='/dev/default-pool/collidevol1.img'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<target dev='sdc' bus='scsi'/>
CloneManager: Make sure to sync driver_name
2013-07-15 03:53:23 +08:00
<driver type="qcow2"/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<readonly/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<shareable/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</disk>
<disk type='file' device='disk'>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<source file='/dev/default-pool/default-vol'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<target dev='hda' bus='ide'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</disk>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<disk type='file' device='disk'>
virt-install: set_install_defaults before disk validation So we validate the CDROM disk contents too. This revealed we were using a cdrom path in the test driver that was assigned as a writeable disk to another test VM, which is a correct warning, so fix the fallout, and ensure that we don't warn when colliding with another cdrom device
2019-02-08 04:00:27 +08:00
<source file='/dev/default-pool/testvol9.img'/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<target dev='hdb' bus='ide'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</disk>
<interface type='network'>
<source network='default'/>
<mac address='22:22:33:12:34:AB'/>
<model type='e1000'/>
</interface>
<interface type='user'>
<mac address='22:11:11:11:11:11'/>
</interface>
<parallel type='file'>
<source path='/tmp/foo.log'/>
</parallel>
tests: introduce a test for removing unix channel path for virt-clone Commit 3a33f341 fixed an issue, where we should remove source path for unix channel in order to let libvirt generate new one. Add a test case to cover this change. Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2015-11-03 18:48:53 +08:00
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/test-for-clone/org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0'/>
</channel>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</devices>
</domain>
testdriver: Add guest using a duplicate host USB device
2013-05-11 23:44:25 +08:00
tests: make test-clone VMs offline by default Simplifies test cases
2017-03-07 04:46:39 +08:00
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<test:runstate>5</test:runstate>
tests: Rename clone test VMs to have a common "test-clone" prefix
2017-03-07 04:35:02 +08:00
<name>test-clone-full</name>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<currentMemory>204800</currentMemory>
<memory>409600</memory>
<uuid>abcd5678-aaaa-1234-1234-12345678FFFF</uuid>
<os>
<type arch='i686'>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='hd'/>
</os>
<features>
<acpi/><apic/>
</features>
<clock offset="utc"/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
guest: Don't set any defaults for on_* Currently we hardcode these defaults for installing VMs: <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> And these for post-install config: <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> But this has some issues. on_crash=restart is problematic in that most configs don't support it, and some like virtuozzo actively reject it. Additionally this we should leave as much to libvirt defaults as we can, which are more sensible in this case. Drop everything except setting on_reboot=destroy for the install time case (which is required for our config changes). Since on_poweroff and on_crash already default to 'destroy', the install time config is unchanged, and the post-install config now on_crash=destroy instead of 'restart'. The s390 on_crash=preserve workaround is dropped, which was intended to avoid a reboot loop caused by on_crash=reboot
2017-02-21 22:27:56 +08:00
<on_crash>destroy</on_crash>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<vcpu>5</vcpu>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<disk type='block' device='disk'>
<source dev='/full-pool/testvol1.img'/>
<target dev='hda' bus='ide'/>
</disk>
<interface type='user'>
<mac address='22:11:11:11:11:11'/>
</interface>
<console type='pty'/>
</devices>
</domain>
<domain type='test'>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<name>test-xenpv-kernel</name>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<uuid>596a5d2171f48fb2e068e2386a5c413e</uuid>
<os>
<type>xen</type>
<kernel>/var/lib/xen/vmlinuz.2Dn2YT</kernel>
<initrd>/var/lib/xen/initrd.img.0u-Vhq</initrd>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<cmdline>method=http://download.fedora.devel.redhat.com/pub/fedora/linux/core/test/5.91/x86_64/os</cmdline>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</os>
<memory>430080</memory>
<vcpu>2</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/root/some.img'/>
<target dev='xvda'/>
</disk>
<console tty='/dev/pts/4'/>
</devices>
</domain>
testdriver: Add guest using a duplicate host USB device
2013-05-11 23:44:25 +08:00
<domain type='test'>
<name>test-duplicate-usb</name>
<uuid>4a64cc71-19c4-2fd0-2323-3050abaea3c3</uuid>
<memory>8388608</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='i686'>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<product id='0x7e04'/>
<vendor id='0x03f0'/>
</source>
</hostdev>
</devices>
</domain>
details: Explicitly label virtio scsi disks + controllers
2015-04-05 08:01:03 +08:00
<domain type='test'>
<name>test-spapr-xml</name>
<uuid>2754dd7b-ac8a-4850-aec0-1f3fcd43235b</uuid>
<memory unit='KiB'>524288</memory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='i686'>hvm</type>
<boot dev='hd'/>
</os>
<devices>
<console type='pty'>
<address type="spapr-vio"/>
</console>
<serial type="pty">
<address type="spapr-vio"/>
</serial>
<serial type="pty">
<address type="spapr-vio"/>
</serial>
<disk type="file" device="disk">
<source file="/tmp/scsidisk.img"/>
<target dev="sda" bus="scsi"/>
<address type="drive" controller="1"/>
</disk>
<interface type='user'>
<mac address='22:11:11:11:11:FA'/>
<model>spapr-vlan</model>
<address type="spapr-vio"/>
</interface>
<controller type="scsi" index="1">
<address type="spapr-vio"/>
</controller>
<controller type="scsi" index="0">
<address type="spapr-vio"/>
</controller>
</devices>
</domain>
guest: Drop update_defaults Fold its one purpose into the UEFI setting bits, fix it and test it
2018-09-14 03:51:03 +08:00
<domain type='test'>
<name>test-hyperv-uefi</name>
<uuid>4a64cc71-19c4-2fd0-2323-f050941ea3c3</uuid>
<metadata>
<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
<libosinfo:os id="http://microsoft.com/win/7"/>
</libosinfo:libosinfo>
</metadata>
<memory>8388608</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='i686'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state="on"/>
<vapic state="on"/>
<spinlocks state="on" retries="8191"/>
</hyperv>
<vmport state="off"/>
</features>
<clock offset="localtime">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
<timer name="hypervclock" present="yes"/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
</devices>
</domain>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<name>test-state-shutoff</name>
<memory>1048576</memory>
<bootloader>/tmp/bootfoo</bootloader>
<test:runstate>5</test:runstate>
</domain>
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<name>test-state-paused</name>
<memory>1048576</memory>
<bootloader>/tmp/bootfoo</bootloader>
<test:runstate>3</test:runstate>
</domain>
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<name>test-state-crashed</name>
<memory>1048576</memory>
<bootloader>/tmp/bootfoo</bootloader>
<test:runstate>6</test:runstate>
</domain>
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<name>test-state-pmsuspended</name>
<memory>1048576</memory>
<bootloader>/tmp/bootfoo</bootloader>
<test:runstate>7</test:runstate>
</domain>
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<name>test-state-transient</name>
<memory>1048576</memory>
<bootloader>/tmp/bootfoo</bootloader>
<test:transient/>
</domain>
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
<name>test-state-managedsave</name>
<memory>1048576</memory>
<bootloader>/tmp/bootfoo</bootloader>
<test:runstate>5</test:runstate>
<test:hasmanagedsave/>
</domain>
<!-- ############ -->
<!-- Snapshot VMs -->
<!-- ############ -->
<domain type='test' xmlns:test='http://libvirt.org/schemas/domain/test/1.0'>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
<name>test-snapshots</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<memory>409600</memory>
<uuid>12345678-1234-FDDF-1234-12345678FFFF</uuid>
<bootloader>/tmp/bootfoo</bootloader>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
</disk>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
</devices>
<test:domainsnapshot>
<name>internal-root</name>
<state>running</state>
<creationTime>1375905080</creationTime>
<memory snapshot='internal'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
<description>FOO
desc line #2
ba</description>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
snapshots: Handle XML chars in snapshot name (bz 1468912) https://bugzilla.redhat.com/show_bug.cgi?id=1468912
2017-07-11 05:51:04 +08:00
<name>internal-root-child1&amp;</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<state>running</state>
<parent>
<name>internal-root</name>
</parent>
<creationTime>1375885107</creationTime>
<memory snapshot='internal'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
</devices>
</domain>
<active>1</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>offline-root</name>
<state>shutoff</state>
<creationTime>1375905902</creationTime>
<memory snapshot='no'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>offline-root-child1</name>
<state>shutoff</state>
<parent>
<name>offline-root</name>
</parent>
<creationTime>1375905916</creationTime>
<memory snapshot='no'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>offline-root-child2</name>
<state>shutoff</state>
<parent>
<name>offline-root</name>
</parent>
<creationTime>137590600</creationTime>
<memory snapshot='no'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
snapshots: Make state type/icon UI match other usage
2013-10-01 05:11:22 +08:00
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
snapshots: Make state type/icon UI match other usage
2013-10-01 05:11:22 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
snapshots: Make state type/icon UI match other usage
2013-10-01 05:11:22 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>snap-paused</name>
<state>paused</state>
<creationTime>1375903080</creationTime>
<memory snapshot='internal'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
snapshots: Make state type/icon UI match other usage
2013-10-01 05:11:22 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
snapshots: Make state type/icon UI match other usage
2013-10-01 05:11:22 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>snap-pmsuspended</name>
<state>pmsuspended</state>
<creationTime>1375903080</creationTime>
<memory snapshot='internal'/>
<disks>
<disk name='hda' snapshot='internal'/>
</disks>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>aaa-external-mem</name>
<state>running</state>
<creationTime>1365903080</creationTime>
<memory snapshot='external' file='/path/to/memory/state'/>
<disks>
<disk name='hda' snapshot='external'>
<source file='/path/to/new'/>
</disk>
</disks>
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 05:53:55 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
<test:domainsnapshot>
<name>zzz-external-diskonly</name>
<state>shutoff</state>
<creationTime>1365903080</creationTime>
<disks>
<disk name='hda' snapshot='external'>
<source file='/path/to/diskonly'/>
</disk>
</disks>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<domain type='test'>
testdriver: Fix snapshot metadata
2013-10-04 20:54:31 +08:00
<name>test-snapshots</name>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
<uuid>12345678-1234-fddf-1234-12345678ffff</uuid>
<memory unit='KiB'>409600</memory>
<currentMemory unit='KiB'>409600</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/tmp/bootfoo</bootloader>
<os>
<type arch='i686'>xen</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='file' device='disk'>
<source file='/dev/default-pool/test-clone-simple.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='ide' index='0'/>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 09:41:10 +08:00
<graphics type='vnc'/>
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
</devices>
</domain>
<active>0</active>
</test:domainsnapshot>
</domain>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Add GUI elements for TPM passthrough details Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
2013-06-26 09:45:08 +08:00
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- ######## -->
<!-- Networks -->
<!-- ######## -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<network>
<name>default</name>
<uuid>715666b7-dbd4-6c78-fa55-94863da09f2d</uuid>
<forward mode='nat'/>
<bridge name='virbr0' stp='on' forwardDelay='0' />
<ip address='192.168.122.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.122.2' end='192.168.122.254' />
</dhcp>
</ip>
</network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<network>
<name>isolated_net</name>
<ip address='192.168.100.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.100.128' end='192.168.100.254'/>
</dhcp>
</ip>
testdriver: Add network <bandwidth> example
2014-06-26 20:50:08 +08:00
<bandwidth>
<inbound average="1000" peak="5000" burst="5120"/>
<outbound average="1000" peak="5000" burst="5120"/>
</bandwidth>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</network>
<network>
<name>nat_to_eth0</name>
<forward dev='eth0'/>
<ip address='192.168.100.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.100.128' end='192.168.100.254'/>
</dhcp>
</ip>
</network>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<network>
<name>route</name>
<uuid>715666b7-aaaa-6c78-fa55-94863da09f2d</uuid>
<forward mode='route'/>
<ip address='192.168.123.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.123.2' end='192.168.123.254' />
</dhcp>
</ip>
</network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
testdriver: Add network example of open network forward mode Signed-off-by: Lin Ma <lma@suse.com>
2017-05-03 23:56:30 +08:00
<network>
<name>open</name>
<uuid>f59fb0e3-3903-4867-a97f-3faa2edc0a50</uuid>
<forward mode="open"/>
<domain name="open"/>
<ip address="192.168.100.1" netmask="255.255.255.0">
<dhcp>
<range start="192.168.100.128" end="192.168.100.254"/>
</dhcp>
</ip>
</network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<network>
<name>netboot</name>
<uuid>81ff0d90-c91e-6742-64da-4a736edb9a9b</uuid>
<bridge name="virbr1" stp='off' delay='1'/>
<domain name="example.com"/>
<forward/>
<ip address="192.168.122.1" netmask="255.255.255.0">
<tftp root="/var/lib/tftproot" />
<dhcp>
<range start="192.168.122.2" end="192.168.122.254" />
<bootp file="pxeboot.img" />
</dhcp>
</ip>
</network>
<network>
network: Parse <portgroup> XML
2014-06-01 02:20:56 +08:00
<name>plainbridge-portgroups</name>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<uuid>b1b9d7c6-f620-048f-71ee-ca3ba1ac3e98</uuid>
<forward mode='bridge'/>
<bridge name='br2' />
network: Parse <portgroup> XML
2014-06-01 02:20:56 +08:00
<portgroup name='engineering' default='yes'>
<virtualport type='802.1Qbh'>
<parameters profileid='test'/>
</virtualport>
<bandwidth>
<inbound average='1000' peak='5000' burst='5120'/>
<outbound average='1000' peak='5000' burst='5120'/>
</bandwidth>
</portgroup>
<portgroup name='sales'>
<virtualport type='802.1Qbh'>
<parameters profileid='salestest'/>
</virtualport>
<bandwidth>
<inbound average='500' peak='2000' burst='2560'/>
<outbound average='128' peak='256' burst='256'/>
</bandwidth>
</portgroup>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</network>
<network>
<name>ipv4_prefix</name>
Add Network class for parsing <network> XML Convert virtManager/host.py, do some cleanups and modernization to the UI there, add tests. createnet.py hasn't really been touched yet, but still works because it was building the XML by hand anyways.
2013-09-21 08:40:07 +08:00
<uuid>81ff0d90-c91e-6742-64da-4a736edb9122</uuid>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<forward dev='eth1' mode='nat'>
<interface dev='eth1'/>
</forward>
<bridge name='ipv4_prefix' stp='on' delay='0' />
<ip family='ipv4' address='192.168.50.1' prefix='24'>
</ip>
</network>
<network>
<name>ipv4_nomask</name>
<uuid>81ff0d90-aaaa-6742-64da-4a736edb9a9b</uuid>
<bridge name='ipv4_nomask' stp='on' delay='0' />
<ip family='ipv4' address='10.24.10.1'>
</ip>
</network>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<network ipv6='yes'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>ipv6_empty</name>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<uuid>591d28b3-25fd-21f5-ac71-e1877d787945</uuid>
<bridge name='virbr1' stp='on' delay='0' />
</network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>ipv6_2ranges</name>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<uuid>e08c0cc3-b892-b53b-c41d-c4f526291be9</uuid>
<forward mode='nat'/>
<bridge name='virbr2' stp='on' delay='0' />
<domain name='net6'/>
<ip address='192.168.6.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.6.128' end='192.168.6.254' />
</dhcp>
</ip>
<ip family='ipv6' address='fd00:beef:10:6::1' prefix='64'>
<dhcp>
<range start='fd00:beef:10:6::1:1' end='fd00:beef:10:6::1:f1' />
</dhcp>
</ip>
</network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>ipv6_multirange</name>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<uuid>41b4afe4-87bb-8087-6724-5e208a2d483a</uuid>
<forward mode='nat'/>
<bridge name='virbr3' stp='on' delay='0' />
<domain name='net7'/>
<ip address='192.168.7.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.7.128' end='192.168.7.254' />
<host mac='52:54:00:60:7d:5d' name='paul' ip='192.168.7.2' />
<host mac='52:54:00:69:eb:91' name='badbob' ip='192.168.7.3' />
</dhcp>
</ip>
<ip family='ipv6' address='fd00:beef:10:7::1' prefix='64'>
<dhcp>
<range start='fd00:beef:10:7::1:1' end='fd00:beef:10:7::1:f1' />
<host id='00:03:00:01:52:54:00:60:7d:5d' name='paul' ip='fd00:beef:10:7::7:2' />
<host id='00:03:00:01:52:54:00:69:eb:91' name='badbob' ip='fd00:beef:10:7::7:4' />
</dhcp>
</ip>
<ip family='ipv6' address='fd00:beef:12::' prefix='48' via='fd00:beef:10:7::7:2'>
</ip>
<ip family='ipv4' address='192.168.19.0' netmask='255.255.255.0'>
</ip>
</network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<network>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>ipv6_multirange2</name>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
<uuid>f9c6675f-98f8-ce75-b39a-02c1d23081e0</uuid>
<forward mode='nat'/>
<bridge name='virbr4' stp='on' delay='0' />
<domain name='net8'/>
<ip family='ipv4' address='192.168.8.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.8.64' end='192.168.8.79' />
</dhcp>
</ip>
<ip family='ipv6' address='fd00:beef:10:8::1' prefix='64'>
<dhcp>
<range start='fd00:beef:10:8::1:1' end='fd00:beef:10:8::1:f1' />
<host id='0:3:0:1:52:54:00:d0:2e:22' name='btrfs2' ip='fd00:beef:10:8::2:5' />
</dhcp>
</ip>
<ip family='ipv6' address='fd00:beef:13::' prefix='48' via='fd00:beef:10:8::2:5'>
</ip>
<ip family='ipv4' address='192.168.81.0' netmask='255.255.255.0' via='192.168.8.2'>
</ip>
</network>
network: Fix parsing route netmask
2013-09-23 21:10:43 +08:00
<network ipv6='yes'>
<name>ipv6route</name>
<domain name='bar' />
<forward mode='route' dev='eth1'/>
<ip family='ipv6' address='fd00:db8:ac10:fd01::1' prefix='64'>
<dhcp>
<range start='fd00:db8:ac10:fd01::100' end='fd00:db8:ac10:fd01::1ff'/>
</dhcp>
</ip>
<route family='ipv6' address='fd00:db8:ac10:fd00::' prefix='64' gateway='fd00:db8:ac10:fd01::1' />
</network>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
testdriver: Add openvswitch <network> example
2017-03-25 04:27:46 +08:00
<network>
<name>ovsbr1</name>
<forward mode='bridge'/>
<bridge name='ovsbr1'/>
<virtualport type='openvswitch'/>
</network>
testdriver: Add network example of a pool of SRIOV VFs Signed-off-by: Lin Ma <lma@suse.com>
2017-03-27 10:22:33 +08:00
<network>
<name>passthrough</name>
<forward mode='hostdev' managed='yes'>
<pf dev='eth3'/>
</forward>
</network>
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- ####### -->
<!-- Storage -->
<!-- ####### -->
IPv6 support v2: update gui python and ui The purpose of this update is: 1. replace use of IPy with ipaddr since ipaddr has needed functionality and IPy does not. 2. Update the glade-3 ui (vmm-host.ui) to provide for IPv6 as well as IPv4. If either IPv4 or IPv6 is not defined, its respective frame is hidden. 3. The DNS Domain Name is added to the basic frame. 4. IPv4 forwarding is moved to the basic frame and ipv6 forwarding is added. 5. If an IPv4 address is not defined then the IPv4 is set to Isolated network, internal rout only. 6. IPv6 network has three values for Forwarding: Isolated network, Isolated network with internal forwarding, and Routed network. 7. Add network definitions to tests/testdriver.xml which include IPv6 and other new parameters now being handled. This patch includes the fix for getting a KeyError exception when deleting a network definition. In this update, createnet.py has been changed to use ipaddr but it still only handles IPv4 network creation. . Signed-off-by: Gene Czarcinski <gene@czarc.net> (crobinso: Add Gene to AUTHORS)
2013-03-30 02:38:28 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<pool type='dir'>
<name>default-pool</name>
<uuid>35bb2ad9-388a-cdfe-461a-b8907f6e53fe</uuid>
<capacity>107374182400</capacity>
<allocation>0</allocation>
<available>107374182400</available>
<source>
</source>
<target>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<path>/dev/default-pool</path>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>default-vol</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
Break out shared storage UI to storagelist.py (bz 1060433) We were already sharing a chunk of this in a haphazard way. Now officially break it all out, similar to netlist.py. This mostly unifies the views of host->storage and storagebrowser.py
2015-04-09 06:29:48 +08:00
<volume type='file'>
<name>dir-vol</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='dir'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>iso-vol</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='iso'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>bochs-vol</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='bochs'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>testvol1.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>testvol2.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
virt-install: set_install_defaults before disk validation So we validate the CDROM disk contents too. This revealed we were using a cdrom path in the test driver that was assigned as a writeable disk to another test VM, which is a correct warning, so fix the fallout, and ensure that we don't warn when colliding with another cdrom device
2019-02-08 04:00:27 +08:00
<volume type='file'>
<name>testvol9.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>UPPER</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>test-clone-simple.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>collidevol1.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target/>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>sharevol.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target/>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Probe entire backing chain when checking if path is in use
2014-01-15 06:44:14 +08:00
<name>backingl3.img</name>
storage: Parse volume backingstore
2013-09-29 07:11:27 +08:00
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='raw'/>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Probe entire backing chain when checking if path is in use
2014-01-15 06:44:14 +08:00
<name>backingl2.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
</target>
<backingStore>
<path>/dev/default-pool/backingl3.img</path>
</backingStore>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Probe entire backing chain when checking if path is in use
2014-01-15 06:44:14 +08:00
<name>backingl1.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
</target>
<backingStore>
<path>/dev/default-pool/backingl2.img</path>
</backingStore>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
storage: Parse volume backingstore
2013-09-29 07:11:27 +08:00
<name>overlay.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
</target>
<backingStore>
Probe entire backing chain when checking if path is in use
2014-01-15 06:44:14 +08:00
<path>/dev/default-pool/backingl1.img</path>
storage: Parse volume backingstore
2013-09-29 07:11:27 +08:00
</backingStore>
</volume>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<!-- fake arm media -->
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<name>test-arm-kernel</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='raw'/>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<name>test-arm-initrd</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='raw'/>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Track kernel/initrd/dtb in 'path in use by' UI
2014-01-15 05:32:05 +08:00
<name>test-arm-dtb</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='raw'/>
</target>
</volume>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<pool type='dir'>
<name>spurious-slash-pool</name>
<uuid>35bb2ad9-1122-cdfe-461a-b8907f6e53fe</uuid>
<capacity>107374182400</capacity>
<allocation>0</allocation>
<available>107374182400</available>
<source>
</source>
<target>
<path>/spurious-slash-pool//</path>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>default-vol</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target/>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>testvol1.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target/>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>testvol2.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target/>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>collidevol1.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target/>
</volume>
</pool>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<pool type='dir'>
<name>inactive-pool</name>
<uuid>35bb2aaa-388a-cdfe-461a-b8907f6e53fe</uuid>
<capacity>107374182400</capacity>
<allocation>0</allocation>
<available>107374182400</available>
<source>
</source>
<target>
<path>/inactive-pool</path>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>inactive-vol</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<format type='qcow2'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<pool type='dir'>
<name>cross-pool</name>
<uuid>35bb2ad9-388a-cdfe-461a-b8907f6e5abc</uuid>
<capacity>107374182400</capacity>
<allocation>0</allocation>
<available>107374182400</available>
<source>
</source>
<target>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<path>/dev/cross-pool</path>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>testvol1.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>testvol2.img</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<pool type='dir'>
<name>full-pool</name>
<uuid>35bb2ad9-388a-cdfe-461a-b8907f6e5555</uuid>
<capacity>1</capacity>
<allocation>1</allocation>
<available>0</available>
<source>
</source>
<target>
<path>/full-pool</path>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='file'>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<name>testvol1.img</name>
<capacity>107374182400</capacity>
<allocation>107374182400</allocation>
<target>
<format type='qcow2'/>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<pool type='logical'>
<name>disk-pool</name>
<uuid>35bb2ad9-388a-cdfe-461a-b8907f6e5aaa</uuid>
<capacity>107374182400</capacity>
<allocation>0</allocation>
<available>107374182400</available>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<source>
</source>
<target>
tests: move the storage pool under /dev. The commit efab27afbf02743a3a2582e9a111eb1b7d985b26 in libvirt uses /dev/%s for logical pools, change the tests to accommodate it. (crobinso: additional fix to work with older libvirt)
2013-07-26 10:06:28 +08:00
<path>/dev/disk-pool</path>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='block'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>diskvol1</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<target>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
tests: scsi reservation test shouldn't check host /dev/sda Was failing in our CI
2018-10-12 05:02:45 +08:00
<volume type='block'>
<name>diskvol7</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
</pool>
<pool type='iscsi'>
<name>iscsi-pool</name>
<uuid>abcdead9-388a-cdfe-461a-b8907f6e5aaa</uuid>
<capacity>107374182400</capacity>
<allocation>0</allocation>
<available>107374182400</available>
<source>
<host name="iscsi.example.com"/>
<device path="demo-target"/>
</source>
<target>
<path>/iscsi-pool</path>
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='block'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>diskvol1</name>
<capacity>1000000</capacity>
<allocation>50000</allocation>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<target>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<format type='unknown'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<permissions>
<mode>0700</mode>
<owner>10736</owner>
<group>10736</group>
</permissions>
</target>
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
tests: Add rbd pool example to testdriver
2013-03-27 21:39:16 +08:00
<pool type='rbd'>
<name>rbd-ceph</name>
<uuid>4bcd023e-990e-fcf6-d95c-52dd0cd938c8</uuid>
<capacity unit='bytes'>47256127143936</capacity>
<allocation unit='bytes'>5537792235090</allocation>
<available unit='bytes'>35978000121856</available>
<source>
<host name='ceph-mon-1.example.com' port='6789'/>
<host name='ceph-mon-2.example.com' port='6789'/>
<host name='ceph-mon-3.example.com' port='6789'/>
tests: Make rbd path names more descriptive
2018-10-12 05:33:41 +08:00
<name>rbd-sourcename</name>
devicedisk: copy all rbd pool host and auth for volume (crobinso: add test suite coverage, fix some pylint)
2018-01-26 18:27:20 +08:00
<auth type='ceph' username='admin'>
<secret uuid='f65cc5a8-b77b-4254-9030-d50a528fb456'/>
</auth>
tests: Add rbd pool example to testdriver
2013-03-27 21:39:16 +08:00
</source>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='network'>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<name>vol1</name>
tests: Make rbd path names more descriptive
2018-10-12 05:33:41 +08:00
<key>rbd-sourcename/vol1</key>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<capacity unit='bytes'>8302592</capacity>
<allocation unit='bytes'>8388608</allocation>
<target>
tests: Make rbd path names more descriptive
2018-10-12 05:33:41 +08:00
<path>rbd-sourcename/vol1</path>
tests: Make many-devices dependent on newer libvirt Libvirt started to put type='raw' by default for rbd volumes, which changes our generated XML. Limit the test to only libvirt that supports that check.
2016-01-16 00:44:28 +08:00
<format type='raw'/>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
</target>
</volume>
test: Set volume type in testdriver XML
2014-12-10 06:50:16 +08:00
<volume type='network'>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<name>some-rbd-vol</name>
tests: Make rbd path names more descriptive
2018-10-12 05:33:41 +08:00
<key>rbd-sourcename/some-rbd-vol</key>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<capacity unit='bytes'>104857600</capacity>
<allocation unit='bytes'>104857600</allocation>
<target>
tests: Make rbd path names more descriptive
2018-10-12 05:33:41 +08:00
<path>rbd-sourcename/some-rbd-vol</path>
tests: Make many-devices dependent on newer libvirt Libvirt started to put type='raw' by default for rbd volumes, which changes our generated XML. Limit the test to only libvirt that supports that check.
2016-01-16 00:44:28 +08:00
<format type='raw'/>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
</target>
</volume>
tests: Add rbd pool example to testdriver
2013-03-27 21:39:16 +08:00
</pool>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
<pool type='sheepdog'>
<name>myshpool</name>
<uuid>581381f8-a13f-4f7c-89b5-9c9b71c64834</uuid>
<capacity unit='bytes'>107374182400</capacity>
<allocation unit='bytes'>53687091200</allocation>
<available unit='bytes'>53687091200</available>
<source>
<host name='localhost' port='7000'/>
<name>mysheeppool</name>
</source>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
<volume type='network'>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<name>vol_sheepdog</name>
<key>sheep/vol_sheepdog</key>
<capacity unit='bytes'>1024</capacity>
<allocation unit='bytes'>0</allocation>
<target>
<path>sheepdog:vol_sheepdog</path>
<format type='unknown'/>
<permissions>
<mode>0600</mode>
tests/testdriver: Don't use invalid uid values The value 4294967295 used in the testdriver for sheepdog volume is not valid on 32bit systems as it won't fit in uid_t and libvirt will fail parsing that. Running "./setup.py test" then fails with: raise libvirtError('virConnectOpenAuth() failed') libvirt.libvirtError: XML error: malformed owner element Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2014-12-10 16:42:06 +08:00
<owner>-1</owner>
<group>-1</group>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
</permissions>
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
</target>
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
<pool type='gluster'>
<name>gluster-pool</name>
<uuid>7b83ef6d-28da-44f1-841f-2011320f13b0</uuid>
<capacity unit='bytes'>492258959360</capacity>
<allocation unit='bytes'>16975638528</allocation>
<available unit='bytes'>475283320832</available>
<source>
<host name='192.168.1.100'/>
devicedisk: fix source name attribute for gluster volumes (crobinso: Small code tweak, and add test cases)
2015-01-27 21:10:12 +08:00
<dir path='/some/dir'/>
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
<name>test-volume</name>
</source>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
<volume type='network'>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<name>test-gluster.raw</name>
devicedisk: fix source name attribute for gluster volumes (crobinso: Small code tweak, and add test cases)
2015-01-27 21:10:12 +08:00
<key>gluster://192.168.1.100/test-volume/some/dir/test-gluster.raw</key>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<capacity unit='bytes'>10737418240</capacity>
<allocation unit='bytes'>2489327616</allocation>
<target>
devicedisk: fix source name attribute for gluster volumes (crobinso: Small code tweak, and add test cases)
2015-01-27 21:10:12 +08:00
<path>gluster://192.168.1.100/test-volume/some/dir/test-gluster.raw</path>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
<format type='raw'/>
<permissions>
<mode>0666</mode>
<owner>0</owner>
<group>0</group>
</permissions>
virt-install: Make --disk $URL 'just work' If VirtualDisk.path is set to a URL, parse it and fill in all the source_* values automagically.
2014-12-09 22:20:18 +08:00
</target>
</volume>
testdriver: Add more gluster examples
2014-12-11 01:42:03 +08:00
<volume type='network'>
<name>test-gluster2.raw</name>
devicedisk: fix source name attribute for gluster volumes (crobinso: Small code tweak, and add test cases)
2015-01-27 21:10:12 +08:00
<key>gluster://192.168.1.100/test-volume/some/dir/test-gluster2.raw</key>
testdriver: Add more gluster examples
2014-12-11 01:42:03 +08:00
<capacity unit='bytes'>10737418240</capacity>
<allocation unit='bytes'>2489327616</allocation>
<target>
devicedisk: fix source name attribute for gluster volumes (crobinso: Small code tweak, and add test cases)
2015-01-27 21:10:12 +08:00
<path>gluster://192.168.1.100/test-volume/some/dir/test-gluster2.raw</path>
testdriver: Add more gluster examples
2014-12-11 01:42:03 +08:00
<format type='raw'/>
<permissions>
<mode>0666</mode>
<owner>0</owner>
<group>0</group>
</permissions>
</target>
</volume>
virt-install: Make --disk $URL 'just work' If VirtualDisk.path is set to a URL, parse it and fill in all the source_* values automagically.
2014-12-09 22:20:18 +08:00
<volume type='network'>
<name>test-gluster.qcow2</name>
<key>gluster://192.168.1.100/test-volume/test-gluster.qcow2</key>
<capacity unit='bytes'>10737418240</capacity>
<allocation unit='bytes'>2489327616</allocation>
<target>
<path>gluster://192.168.1.100/test-volume/test-gluster.qcow2</path>
<format type='qcow2'/>
<permissions>
<mode>0666</mode>
<owner>0</owner>
<group>0</group>
</permissions>
tests: testdriver: More network storage examples
2014-12-05 02:06:20 +08:00
</target>
add gluster and sheepdog pool/volume to testdriver.xml
2014-11-13 04:20:39 +08:00
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
storage: Enable creation of zfs storave volumes
2016-08-09 23:48:34 +08:00
<pool type="zfs">
<name>zfs</name>
<source>
<name>testzfspool</name>
<device path="/dev/ada1"/>
</source>
</pool>
virt-clone: add support to clone nvram VARS Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1243335 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-03-06 16:43:10 +08:00
<pool type="dir">
<name>nvram</name>
<source>
</source>
<target>
<path>/nvram</path>
<permissions>
<mode>0700</mode>
<owner>0</owner>
<group>0</group>
</permissions>
</target>
<volume type='file'>
<name>clone-orig_VARS.fd</name>
<capacity>1000</capacity>
<allocation>1000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>0</owner>
<group>0</group>
</permissions>
</target>
</volume>
uitests: Add details->rename tests
2017-03-09 02:08:22 +08:00
<volume type='file'>
<name>test-many-devices_VARS.fd</name>
<capacity>1000</capacity>
<allocation>1000</allocation>
<target>
<permissions>
<mode>0700</mode>
<owner>0</owner>
<group>0</group>
</permissions>
</target>
</volume>
virt-clone: add support to clone nvram VARS Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1243335 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-03-06 16:43:10 +08:00
</pool>
storage: Enable creation of zfs storave volumes
2016-08-09 23:48:34 +08:00
tests: Add mpath and scsi pool to testdriver.xml
2017-03-07 03:44:25 +08:00
<pool type='mpath'>
<name>mpath</name>
<target>
<path>/dev/mapper</path>
</target>
</pool>
<pool type='scsi'>
<name>scsi</name>
<source>
<adapter type='scsi_host' name='host0'/>
</source>
<target>
<path>/dev/disk/by-path</path>
</target>
<volume type='block'>
<name>unit:0:0:0</name>
<key>35002538043584d30</key>
<capacity unit='bytes'>256060514304</capacity>
<allocation unit='bytes'>256060514304</allocation>
<physical unit='bytes'>256060514304</physical>
<target>
<path>/dev/disk/by-path/pci-0000:00:17.0-ata-1</path>
<format type='dos'/>
</target>
</volume>
<volume type='block'>
<name>unit:0:0:1</name>
<key>35002538043584d31</key>
<capacity unit='bytes'>256060514304</capacity>
<allocation unit='bytes'>256060514304</allocation>
<physical unit='bytes'>256060514304</physical>
<target>
<path>/dev/disk/by-path/pci-0000:00:17.0-ata-30</path>
<format type='gpt'/>
</target>
</volume>
</pool>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
testdriver: Add bits for status, transient, managed save, snapshots No unit tests for any of these, just for UI testing at the moment. These require some non-upstream libvirt patches, but it doesn't hurt in the interim while they are reviewed.
2013-08-07 22:48:23 +08:00
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- ####### -->
<!-- Devices -->
<!-- ####### -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>computer</name>
<capability type='system'>
<hardware>
<vendor>LENOVO</vendor>
<version>ThinkPad T61</version>
<serial>L3B2616</serial>
<uuid>97e80381-494f-11cb-8e0e-cbc168f7d753</uuid>
</hardware>
<firmware>
<vendor>LENOVO</vendor>
<version>7LET51WW (1.21 )</version>
<release_date>08/22/2007</release_date>
</firmware>
</capability>
</device>
<device>
<name>net_00_1c_25_10_b1_e4</name>
<parent>pci_8086_1049</parent>
<capability type='net'>
<interface>eth0</interface>
<address>00:1c:25:10:b1:e4</address>
<capability type='80203'/>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<device>
<name>net_00_1c_25_10_b1_ea</name>
<parent>pci_8086_1022</parent>
<capability type='net'>
<interface>physeth2</interface>
<address>00:1c:25:10:aa:e4</address>
<capability type='80203'/>
</capability>
</device>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>net_00_1c_bf_04_29_a4</name>
<parent>pci_8086_4227</parent>
<capability type='net'>
<interface>wlan0</interface>
<address>00:1c:bf:04:29:a4</address>
<capability type='80211'/>
</capability>
</device>
<device>
<name>net_00_1c_bf_04_29_a4_0</name>
<parent>pci_8086_4227</parent>
<capability type='net'>
<interface>wmaster0</interface>
<address>00:1c:bf:04:29:a4</address>
</capability>
</device>
testdriver: Add missing net dev to match pci dev for SR-IOV network test Add missing net device to match pci device for network ui test of the SR-IOV VF pool. Signed-off-by: Lin Ma <lma@suse.com>
2017-03-31 20:11:59 +08:00
<device>
<name>net_00_1b_21_5a_69_f5</name>
<parent>pci_8086_10fb</parent>
<capability type='net'>
<interface>eth3</interface>
<address>00:1b:21:5a:69:f5</address>
</capability>
</device>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>net_3e_79_a5_6f_37_c3</name>
<parent>computer</parent>
<capability type='net'>
<interface>virbr0</interface>
<address>3e:79:a5:6f:37:c3</address>
</capability>
</device>
<device>
<name>net_computer_loopback</name>
<parent>computer</parent>
<capability type='net'>
<interface>lo</interface>
<address>00:00:00:00:00:00</address>
</capability>
</device>
<device>
<name>pci_1180_476</name>
<parent>pci_8086_2448</parent>
<driver>
<name>yenta_cardbus</name>
</driver>
<capability type='pci'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<domain>1</domain>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<bus>21</bus>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<slot>10</slot>
<function>50</function>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<product id='0x0476'>RL5c476 II</product>
<vendor id='0x1180'>Ricoh Co Ltd</vendor>
nodedev: Parse PCI iommuGroup
2013-10-10 21:41:49 +08:00
<iommuGroup number='3'>
<address domain='0x0000' bus='0x15' slot='0x00' function='0x4'/>
</iommuGroup>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_1180_592</name>
<parent>pci_8086_2448</parent>
<capability type='pci'>
<domain>0</domain>
<bus>21</bus>
<slot>0</slot>
<function>4</function>
<product id='0x0592'>R5C592 Memory Stick Bus Host Adapter</product>
<vendor id='0x1180'>Ricoh Co Ltd</vendor>
nodedev: Parse PCI iommuGroup
2013-10-10 21:41:49 +08:00
<iommuGroup number='3'>
<address domain='0x0001' bus='0x15' slot='0x0A' function='0x4'/>
</iommuGroup>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_1180_822</name>
<parent>pci_8086_2448</parent>
<driver>
<name>sdhci-pci</name>
</driver>
<capability type='pci'>
<domain>2</domain>
<bus>21</bus>
<slot>0</slot>
<function>2</function>
<product id='0x0822'>R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter</product>
<vendor id='0x1180'>Ricoh Co Ltd</vendor>
</capability>
</device>
<device>
<name>pci_1180_832</name>
<parent>pci_8086_2448</parent>
<driver>
<name>firewire_ohci</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>21</bus>
<slot>0</slot>
<function>1</function>
<product id='0x0832'>R5C832 IEEE 1394 Controller</product>
<vendor id='0x1180'>Ricoh Co Ltd</vendor>
</capability>
</device>
<device>
<name>pci_1180_843</name>
<parent>pci_8086_2448</parent>
<driver>
<name>ricoh-mmc</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>21</bus>
<slot>0</slot>
<function>3</function>
<product id='0x0843'>R5C843 MMC Host Controller</product>
<vendor id='0x1180'>Ricoh Co Ltd</vendor>
</capability>
</device>
<device>
<name>pci_1180_852</name>
<parent>pci_8086_2448</parent>
<capability type='pci'>
<domain>0</domain>
<bus>21</bus>
<slot>0</slot>
<function>5</function>
<product id='0x0852'>xD-Picture Card Controller</product>
<vendor id='0x1180'>Ricoh Co Ltd</vendor>
</capability>
</device>
<device>
<name>pci_8086_1049</name>
<parent>computer</parent>
<driver>
<name>e1000e</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>25</slot>
<function>0</function>
<product id='0x1049'>82566MM Gigabit Network Connection</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
testdriver: Add SR-IOV example Signed-off-by: Lin Ma <lma@suse.com>
2017-03-27 10:22:31 +08:00
<device>
<name>pci_8086_10fb</name>
<parent>pci_0000_80_01_0</parent>
<driver>
<name>ixgbe</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>129</bus>
<slot>0</slot>
<function>1</function>
<product id='0x10fb'>82599ES 10-Gigabit SFI/SFP+ Network Connection</product>
<vendor id='0x8086'>Intel Corporation</vendor>
<capability type='virt_functions' maxCount='63'>
<address domain='0x0000' bus='0x81' slot='0x10' function='0x1'/>
<address domain='0x0000' bus='0x81' slot='0x10' function='0x3'/>
<address domain='0x0000' bus='0x81' slot='0x10' function='0x5'/>
<address domain='0x0000' bus='0x81' slot='0x10' function='0x7'/>
</capability>
<iommuGroup number='47'>
<address domain='0x0000' bus='0x81' slot='0x00' function='0x1'/>
</iommuGroup>
</capability>
</device>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>pci_8086_2448</name>
<parent>computer</parent>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>30</slot>
<function>0</function>
<product id='0x2448'>82801 Mobile PCI Bridge</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_8086_2811</name>
<parent>computer</parent>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>31</slot>
<function>0</function>
<product id='0x2811'>82801HBM (ICH8M-E) LPC Interface Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2829</name>
<parent>computer</parent>
<driver>
<name>ahci</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>31</slot>
<function>2</function>
<product id='0x2829'>82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2829_scsi_host</name>
<parent>pci_8086_2829</parent>
<capability type='scsi_host'>
<host>0</host>
</capability>
</device>
<device>
<name>pci_8086_2829_scsi_host_0</name>
<parent>pci_8086_2829</parent>
<capability type='scsi_host'>
<host>1</host>
</capability>
</device>
<device>
<name>pci_8086_2829_scsi_host_1</name>
<parent>pci_8086_2829</parent>
<capability type='scsi_host'>
<host>2</host>
</capability>
</device>
<device>
<name>pci_8086_2829_scsi_host_scsi_device_lun0</name>
<parent>pci_8086_2829_scsi_host</parent>
<driver>
<name>sd</name>
</driver>
<capability type='scsi'>
<host>0</host>
<bus>0</bus>
<target>0</target>
<lun>0</lun>
<type>disk</type>
</capability>
</device>
<device>
<name>pci_8086_2829_scsi_host_scsi_host</name>
<parent>pci_8086_2829_scsi_host</parent>
<capability type='scsi_host'>
<host>0</host>
</capability>
</device>
<device>
<name>pci_8086_2830</name>
<parent>computer</parent>
<driver>
<name>uhci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>29</slot>
<function>0</function>
<product id='0x2830'>82801H (ICH8 Family) USB UHCI Controller #1</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2831</name>
<parent>computer</parent>
<driver>
<name>uhci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>29</slot>
<function>1</function>
<product id='0x2831'>82801H (ICH8 Family) USB UHCI Controller #2</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2832</name>
<parent>computer</parent>
<driver>
<name>uhci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>29</slot>
<function>2</function>
<product id='0x2832'>82801H (ICH8 Family) USB UHCI Controller #3</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2834</name>
<parent>computer</parent>
<driver>
<name>uhci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>26</slot>
<function>0</function>
<product id='0x2834'>82801H (ICH8 Family) USB UHCI Controller #4</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2835</name>
<parent>computer</parent>
<driver>
<name>uhci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>26</slot>
<function>1</function>
<product id='0x2835'>82801H (ICH8 Family) USB UHCI Controller #5</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2836</name>
<parent>computer</parent>
<driver>
<name>ehci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>29</slot>
<function>7</function>
<product id='0x2836'>82801H (ICH8 Family) USB2 EHCI Controller #1</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_283a</name>
<parent>computer</parent>
<driver>
<name>ehci_hcd</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>26</slot>
<function>7</function>
<product id='0x283a'>82801H (ICH8 Family) USB2 EHCI Controller #2</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_283e</name>
<parent>computer</parent>
<driver>
<name>i801_smbus</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>31</slot>
<function>3</function>
<product id='0x283e'>82801H (ICH8 Family) SMBus Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_283f</name>
<parent>computer</parent>
<driver>
<name>pcieport-driver</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>28</slot>
<function>0</function>
<product id='0x283f'>82801H (ICH8 Family) PCI Express Port 1</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_8086_2841</name>
<parent>computer</parent>
<driver>
<name>pcieport-driver</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>28</slot>
<function>1</function>
<product id='0x2841'>82801H (ICH8 Family) PCI Express Port 2</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_8086_2843</name>
<parent>computer</parent>
<driver>
<name>pcieport-driver</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>28</slot>
<function>2</function>
<product id='0x2843'>82801H (ICH8 Family) PCI Express Port 3</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_8086_2845</name>
<parent>computer</parent>
<driver>
<name>pcieport-driver</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>28</slot>
<function>3</function>
<product id='0x2845'>82801H (ICH8 Family) PCI Express Port 4</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_8086_2847</name>
<parent>computer</parent>
<driver>
<name>pcieport-driver</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>28</slot>
<function>4</function>
<product id='0x2847'>82801H (ICH8 Family) PCI Express Port 5</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>pci_8086_284b</name>
<parent>computer</parent>
<driver>
<name>HDA Intel</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>27</slot>
<function>0</function>
<product id='0x284b'>82801H (ICH8 Family) HD Audio Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2850</name>
<parent>computer</parent>
<driver>
<name>ata_piix</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>31</slot>
<function>1</function>
<product id='0x2850'>82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2850_scsi_host</name>
<parent>pci_8086_2850</parent>
<capability type='scsi_host'>
<host>3</host>
</capability>
</device>
<device>
<name>pci_8086_2850_scsi_host_0</name>
<parent>pci_8086_2850</parent>
<capability type='scsi_host'>
<host>4</host>
</capability>
</device>
<device>
<name>pci_8086_2850_scsi_host_scsi_device_lun0</name>
<parent>pci_8086_2850_scsi_host</parent>
<driver>
<name>sr</name>
</driver>
<capability type='scsi'>
<host>3</host>
<bus>0</bus>
<target>0</target>
<lun>0</lun>
<type>cdrom</type>
</capability>
</device>
<device>
<name>pci_8086_2850_scsi_host_scsi_host</name>
<parent>pci_8086_2850_scsi_host</parent>
<capability type='scsi_host'>
<host>3</host>
</capability>
</device>
<device>
<name>pci_8086_2a00</name>
<parent>computer</parent>
<driver>
<name>agpgart-intel</name>
</driver>
<capability type='pci'>
<domain>0</domain>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<bus>2</bus>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<slot>0</slot>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<function>15</function>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<product id='0x2a00'>Mobile PM965/GM965/GL960 Memory Controller Hub</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2a02</name>
<parent>computer</parent>
<driver>
<name>i915</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>2</slot>
<function>0</function>
<product id='0x2a02'>Mobile GM965/GL960 Integrated Graphics Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2a03</name>
<parent>computer</parent>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>2</slot>
<function>1</function>
<product id='0x2a03'>Mobile GM965/GL960 Integrated Graphics Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2a04</name>
<parent>computer</parent>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>3</slot>
<function>0</function>
<product id='0x2a04'>Mobile PM965/GM965 MEI Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2a06</name>
<parent>computer</parent>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>3</slot>
<function>2</function>
<product id='0x2a06'>Mobile PM965/GM965 PT IDER Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_2a07</name>
<parent>computer</parent>
<driver>
<name>serial</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>3</slot>
<function>3</function>
<product id='0x2a07'>Mobile PM965/GM965 KT Controller</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
<device>
<name>pci_8086_4227</name>
<parent>pci_8086_2841</parent>
<driver>
<name>iwl3945</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>3</bus>
<slot>0</slot>
<function>0</function>
<product id='0x4227'>PRO/Wireless 3945ABG [Golan] Network Connection</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<device>
<name>storage_serial_ST910021AS_5MH04L87</name>
<parent>pci_8086_2829_scsi_host_scsi_device_lun0</parent>
<capability type='storage'>
<block>/dev/sda</block>
<bus>pci</bus>
<drive_type>disk</drive_type>
<model>ST910021AS</model>
<vendor>ATA</vendor>
<serial>ST910021AS_5MH04L87</serial>
<size>100030242816</size>
</capability>
</device>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>storage_serial_SATA_WDC_WD1600AAJS__WD_WCAP95119685</name>
<parent>pci_8086_27c0_scsi_host_scsi_device_lun0</parent>
nodedev: add DevNode children and helper <devnode> have been proposed for libvirt 3.1, it provides device /dev/ path when available. The get_devnode() helper will return the by-path/ path preferably, as they should be stable. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2017-02-21 21:00:53 +08:00
<devnode type='dev'>/dev/sda</devnode>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<capability type='storage'>
<block>/dev/sda</block>
<bus>scsi</bus>
<drive_type>disk</drive_type>
<model>WDC WD1600AAJS-2</model>
<vendor>ATA</vendor>
<size>160041885696</size>
</capability>
</device>
<device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>storage_model_DVDRAM_GSA_U10N</name>
<parent>pci_8086_2850_scsi_host_scsi_device_lun0</parent>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<capability type='storage'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<block>/dev/sr1</block>
<bus>pci</bus>
<drive_type>cdrom</drive_type>
<model>DVDRAM GSA-U10N</model>
<vendor>HL-DT-ST</vendor>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<capability type='removable'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<media_available>0</media_available>
<media_size>0</media_size>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>storage_model_DVDRAM_GSA_U1200N</name>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<parent>pci_8086_2850_scsi_host_scsi_device_lun0</parent>
<capability type='storage'>
<block>/dev/sr0</block>
<bus>pci</bus>
<drive_type>cdrom</drive_type>
<model>DVDRAM GSA-U10N</model>
<vendor>HL-DT-ST</vendor>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<capability type='removable'>
<media_available>1</media_available>
<media_size>1234</media_size>
<media_label>Fedora12_media</media_label>
</capability>
</capability>
</device>
<!-- Floppy drive empty -->
<device>
<name>storage_serial_MITSUMI_MITSUMI_USB_FDD_061M</name>
<parent>usb_device_3ee_6901_noserial_if0_scsi_host_0_scsi_device_lun0</parent>
<capability type='storage'>
<block>/dev/fda</block>
<bus>usb</bus>
<drive_type>floppy</drive_type>
<model>USB FDD 061M</model>
<vendor>MITSUMI</vendor>
<serial>MITSUMI_MITSUMI_USB_FDD_061M</serial>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<capability type='removable'>
<media_available>0</media_available>
<media_size>0</media_size>
</capability>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<capability type='hotpluggable' />
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- Floppy drive full -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<name>storage_serial_MITSUMI_MITSUMI_USB_FDD_061M_2</name>
<parent>usb_device_3ee_6901_noserial_if0_scsi_host_0_scsi_device_lun0</parent>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<capability type='storage'>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<block>/dev/fdb</block>
<bus>usb</bus>
<drive_type>floppy</drive_type>
<model>USB FDD 061M</model>
<vendor>MITSUMI</vendor>
<serial>MITSUMI_MITSUMI_USB_FDD_061M</serial>
<capability type='removable'>
<media_available>1</media_available>
<media_size>123456</media_size>
<media_label>Floppy_install_label</media_label>
</capability>
<capability type='hotpluggable' />
</capability>
</device>
<device>
<name>storage_serial_SanDisk_Cruzer_Micro_2004453082054CA1BEEE_0_0</name>
<parent>usb_device_781_5151_2004453082054CA1BEEE_if0_scsi_host_0_scsi_device_lun0</parent>
<capability type='storage'>
<block>/dev/sdb</block>
<bus>usb</bus>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<drive_type>disk</drive_type>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<model>Cruzer Micro</model>
<vendor>SanDisk</vendor>
<capability type='removable'>
<media_available>1</media_available>
<media_size>12345678</media_size>
<media_label>Windows_Media</media_label>
</capability>
<capability type='hotpluggable' />
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1a_0</name>
<parent>pci_8086_2834</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>3</bus>
<device>1</device>
<product id='0x0001'>1.1 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1a_0_if0</name>
<parent>usb_device_1d6b_1_0000_00_1a_0</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1a_1</name>
<parent>pci_8086_2835</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>4</bus>
<device>1</device>
<product id='0x0001'>1.1 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1a_1_if0</name>
<parent>usb_device_1d6b_1_0000_00_1a_1</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1d_0</name>
<parent>pci_8086_2830</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>5</bus>
<device>1</device>
<product id='0x0001'>1.1 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1d_0_if0</name>
<parent>usb_device_1d6b_1_0000_00_1d_0</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1d_1</name>
<parent>pci_8086_2831</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>6</bus>
<device>1</device>
<product id='0x0001'>1.1 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1d_1_if0</name>
<parent>usb_device_1d6b_1_0000_00_1d_1</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>usb_device_781_5151_2004453082054CA1BEEE</name>
<parent>usb_device_1d6b_2_0000_00_1a_7</parent>
<capability type='usb_device'>
<bus>1</bus>
<device>4</device>
<product id='0x5151'>Cruzer Micro 256/512MB Flash Drive</product>
<vendor id='0x0781'>SanDisk Corp.</vendor>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<device>
<name>usb_device_1d6b_1_0000_00_1d_2</name>
<parent>pci_8086_2832</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>7</bus>
<device>1</device>
<product id='0x0001'>1.1 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_1_0000_00_1d_2_if0</name>
<parent>usb_device_1d6b_1_0000_00_1d_2</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
<device>
<name>usb_device_1d6b_2_0000_00_1a_7</name>
<parent>pci_8086_283a</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>1</bus>
<device>1</device>
<product id='0x0002'>2.0 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_2_0000_00_1a_7_if0</name>
<parent>usb_device_1d6b_2_0000_00_1a_7</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>usb_device_1d6b_2_0000_00_1d_7</name>
<parent>pci_8086_2836</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>2</bus>
<device>1</device>
<product id='0x0002'>2.0 root hub</product>
<vendor id='0x1d6b'>Linux Foundation</vendor>
</capability>
</device>
<device>
<name>usb_device_1d6b_2_0000_00_1d_7_if0</name>
<parent>usb_device_1d6b_2_0000_00_1d_7</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
<device>
<name>usb_device_483_2016_noserial</name>
<parent>usb_device_1d6b_1_0000_00_1a_0</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>3</bus>
<device>2</device>
<product id='0x2016'>Fingerprint Reader</product>
<vendor id='0x0483'>SGS Thomson Microelectronics</vendor>
</capability>
</device>
<device>
<name>usb_device_483_2016_noserial_if0</name>
<parent>usb_device_483_2016_noserial</parent>
<capability type='usb'>
<number>0</number>
<class>255</class>
<subclass>0</subclass>
<protocol>0</protocol>
</capability>
</device>
<device>
<name>usb_device_4b3_4485_noserial</name>
<parent>usb_device_1d6b_2_0000_00_1a_7</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>1</bus>
<device>3</device>
<product id='0x4485'>Serial Converter</product>
<vendor id='0x04b3'>IBM Corp.</vendor>
</capability>
</device>
<device>
<name>usb_device_4b3_4485_noserial_if0</name>
<parent>usb_device_4b3_4485_noserial</parent>
<driver>
<name>hub</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>9</class>
<subclass>0</subclass>
<protocol>2</protocol>
</capability>
</device>
<device>
<name>usb_device_62a_1_noserial</name>
<parent>usb_device_4b3_4485_noserial</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>1</bus>
<device>4</device>
<product id='0x0001'>Notebook Optical Mouse</product>
<vendor id='0x062a'>Creative Labs</vendor>
</capability>
</device>
<device>
<name>usb_device_62a_1_noserial_if0</name>
<parent>usb_device_62a_1_noserial</parent>
<driver>
<name>usbhid</name>
</driver>
<capability type='usb'>
<number>0</number>
<class>3</class>
<subclass>1</subclass>
<protocol>2</protocol>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- NPIV and fibrechannel -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>pci_8086_25f8</name>
<parent>computer</parent>
<driver>
<name>pcieport-driver</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>4</slot>
<function>0</function>
<product id='0x25f8'>5000 Series Chipset PCI Express x8 Port 4-5</product>
<vendor id='0x8086'>Intel Corporation</vendor>
addhardware: Don't show pci-bridge devices These aren't assignable
2018-10-14 00:19:31 +08:00
<capability type='pci-bridge'/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>pci_10df_fe00_0</name>
<parent>pci_8086_25f8</parent>
<driver>
<name>lpfc</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>16</bus>
<slot>0</slot>
<function>1</function>
<product id='0xfe00'>Zephyr-X LightPulse Fibre Channel Host Adapter</product>
<vendor id='0x10df'>Emulex Corporation</vendor>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<device>
<name>pci_10df_fe00_0_scsi_host</name>
<parent>pci_10df_fe00_0</parent>
<capability type='scsi_host'>
<host>4</host>
<capability type='fc_host'>
<wwnn>20000000c9848141</wwnn>
<wwpn>10000000c9848141</wwpn>
</capability>
<capability type='vport_ops' />
</capability>
</device>
<!-- End NPIV block -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
testdriver: Add guest using a duplicate host USB device
2013-05-11 23:44:25 +08:00
<!-- Duplicate USB devices -->
<device>
<name>usb_5_20</name>
<parent>usb_usb5</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>1</bus>
<device>20</device>
<product id='0x7e04'>Dup USB 1</product>
<vendor id='0x03f0'>HP</vendor>
</capability>
</device>
<device>
<name>usb_5_21</name>
<parent>usb_usb5</parent>
<driver>
<name>usb</name>
</driver>
<capability type='usb_device'>
<bus>1</bus>
<device>21</device>
<product id='0x7e04'>Dup USB 2</product>
<vendor id='0x03f0'>HP</vendor>
</capability>
</device>
<!-- End duplicate USB devices -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
nodedev: add DRMDevice drm capability has been proposed for libvirt 3.1, it provide Direct Rendering Manager (DRM) devices. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2017-02-21 21:00:54 +08:00
<device>
<name>pci_0000_00_02_0</name>
<path>/sys/devices/pci0000:00/0000:00:02.0</path>
<parent>computer</parent>
<driver>
<name>i915</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>0</bus>
<slot>2</slot>
<function>0</function>
<product id='0x191b'>HD Graphics 530</product>
<vendor id='0x8086'>Intel Corporation</vendor>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
nodedev: add DRMDevice drm capability has been proposed for libvirt 3.1, it provide Direct Rendering Manager (DRM) devices. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2017-02-21 21:00:54 +08:00
<device>
<name>drm_renderD129</name>
<path>/sys/devices/pci0000:00/0000:00:02.0/drm/renderD129</path>
<devnode type='dev'>/dev/dri/renderD129</devnode>
<devnode type='link'>/dev/dri/by-path/pci-0000:00:02.0-render</devnode>
<devnode type='link'>/dev/dri/by-id/foo-render</devnode>
<parent>pci_0000_00_02_0</parent>
<capability type='drm'>
<type>render</type>
</capability>
</device>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- ########## -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<!-- Interfaces -->
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<!-- ########## -->
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<interface type='ethernet' name='eth0'>
<start mode='none'/>
<mac address='00:FF:EE:FF:EE:FF'/>
</interface>
<interface type='ethernet' name='eth1'>
<mac address='00:FF:EE:FF:EE:AB'/>
</interface>
<interface type='ethernet' name='wlan0'>
<start mode='none'/>
<mac address='00:AA:CC:BB:AA:BB'/>
</interface>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
tests: Drop most interface XML testing No part of the app requires the <interface> details any more, so drop testing
2019-05-05 00:13:37 +08:00
<!-- bond example -->
<interface type="ethernet" name="eth-bond0-1"/>
<interface type="ethernet" name="eth-bond0-2"/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<interface type="bond" name="bond0">
<start mode="none"/>
<protocol family="ipv4">
<ip address="192.168.50.7" prefix="24"/>
<route gateway="192.168.50.1"/>
</protocol>
<bond mode="active-backup">
<miimon freq="100" updelay="10" carrier="ioctl"/>
<interface type="ethernet" name="eth-bond0-1"/>
<interface type="ethernet" name="eth-bond0-2"/>
</bond>
</interface>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<!-- Plain bridge -->
tests: Drop most interface XML testing No part of the app requires the <interface> details any more, so drop testing
2019-05-05 00:13:37 +08:00
<interface type="ethernet" name="eth-brplain0"/>
<interface type="ethernet" name="eth-brplain1"/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<interface type="bridge" name="brplain">
<start mode="onboot"/>
<mtu size="1500"/>
<bridge stp="off">
<interface type="ethernet" name="eth-brplain0"/>
<interface type="ethernet" name="eth-brplain1"/>
</bridge>
</interface>
<!-- Empty bridge -->
<interface type="bridge" name="brempty">
<start mode="onboot"/>
<mtu size="1500"/>
<bridge stp="off"/>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
<protocol family='ipv4'>
<dhcp/>
</protocol>
<protocol family='ipv6'>
<autoconf/>
<dhcp/>
</protocol>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
</interface>
tests: Greatly expand testdriver.xml Mostly comes from my own testdriver I used for manual virt-manager testing. Add some notes to HACKING about using it.
2013-04-22 01:12:08 +08:00
tests: Drop most interface XML testing No part of the app requires the <interface> details any more, so drop testing
2019-05-05 00:13:37 +08:00
<!-- vlan example -->
<interface type="ethernet" name="vlaneth1"/>
Merge code from python-virtinst.git As outlined here: https://www.redhat.com/archives/virt-tools-list/2012-February/msg00040.html For now this is just a direct import of the code from virtinst commit dca5a4d6245f21d554f8853197a6a234bfc8e52c. History is not merged, so please refer to original git for detailed commit histor: http://git.fedorahosted.org/cgit/python-virtinst.git/
2013-03-18 05:06:52 +08:00
<interface type="vlan" name="vlaneth1.3">
<start mode="onboot"/>
<vlan tag="43">
<interface name="vlaneth1"/>
</vlan>
</interface>
</node>