External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-05 12:51:12 +00:00
Code Issues Packages Projects Releases Wiki Activity
e8589963bc
libvirt/tests/bhyvexml2argvdata/bhyvexml2argv-grub-bootorder2.xml

40 lines
1.2 KiB
XML
Raw Normal View History

drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
<domain type='bhyve'>
<name>bhyve</name>
<uuid>df3be7e7-a104-11e3-aeb0-50e5492bd3dc</uuid>
<memory>219136</memory>
<vcpu>1</vcpu>
<bootloader>/usr/local/sbin/grub-bhyve</bootloader>
<os>
<type>hvm</type>
</os>
<devices>
<disk type='file'>
<driver name='file' type='raw'/>
<source file='/tmp/freebsd1.img'/>
<target dev='hda' bus='sata'/>
<boot order='111'/>
bhyvexml2argvdata: Fix <drive/> addresses After c07d1c1c4f got merged it uncovered couple of broken domain XMLs for bhyvexml2argv test. Some disk drives had incompatible type of address configured. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-12-25 16:56:22 +00:00
<address type='drive' controller='0' bus='0' target='2' unit='0'/>
drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
</disk>
<disk type='file'>
<driver name='file' type='raw'/>
<source file='/tmp/freebsd2.img'/>
bhyve: fix bhyvexml2arg test Don't use duplicating target dev names.
2016-06-12 08:01:50 +00:00
<target dev='hdb' bus='sata'/>
drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
<boot order='22'/>
bhyvexml2argvdata: Fix <drive/> addresses After c07d1c1c4f got merged it uncovered couple of broken domain XMLs for bhyvexml2argv test. Some disk drives had incompatible type of address configured. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-12-25 16:56:22 +00:00
<address type='drive' controller='0' bus='0' target='4' unit='0'/>
drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
</disk>
<disk type='file'>
<driver name='file' type='raw'/>
<source file='/tmp/freebsd3.img'/>
bhyve: fix bhyvexml2arg test Don't use duplicating target dev names.
2016-06-12 08:01:50 +00:00
<target dev='hdc' bus='sata'/>
drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
<boot order='3'/>
bhyvexml2argvdata: Fix <drive/> addresses After c07d1c1c4f got merged it uncovered couple of broken domain XMLs for bhyvexml2argv test. Some disk drives had incompatible type of address configured. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-12-25 16:56:22 +00:00
<address type='drive' controller='0' bus='0' target='6' unit='0'/>
drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
</disk>
<interface type='bridge'>
bhyvexml2argvdata: Add mac address to <interface/> In the next patch we will need a stable mac address for <interface/>. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-12-26 11:35:50 +00:00
<mac address='52:54:00:0e:d2:6f'/>
drvbhyve: Use boot-order for grub-bhyve boot device Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
2014-11-12 22:31:53 +00:00
<model type='virtio'/>
<source bridge="virbr0"/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
</devices>
</domain>
Reference in New Issue Copy Permalink