mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-07-11 04:15:49 +00:00
392292cd99
By using the auto-generated NVRAM path in test data files, we won't see
bugs where a user specified path gets accidentally overwritten by a
post-parse callback, or VM startup. For example, this caused us to miss
the bug fixed by:
commit 24adb6c7a6
Author: Michal Prívozník <mprivozn@redhat.com>
Date: Wed Feb 23 08:50:44 2022 +0100
qemu: Don't regenerate NVRAM path if parsed from domain XML
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
45 lines
1.4 KiB
XML
45 lines
1.4 KiB
XML
<domain type='qemu'>
|
|
<name>guest</name>
|
|
<uuid>1ccfd97d-5eb4-478a-bbe6-88d254c16db7</uuid>
|
|
<metadata>
|
|
<libosinfo:libosinfo xmlns:libosinfo='http://libosinfo.org/xmlns/libvirt/domain/1.0'>
|
|
<libosinfo:os id='http://fedoraproject.org/fedora/29'/>
|
|
</libosinfo:libosinfo>
|
|
</metadata>
|
|
<memory>4194304</memory>
|
|
<currentMemory>4194304</currentMemory>
|
|
<vcpu>4</vcpu>
|
|
<os>
|
|
<type arch='aarch64' machine='virt'>hvm</type>
|
|
<loader readonly='yes' type='pflash'>/usr/share/AAVMF/AAVMF_CODE.fd</loader>
|
|
<nvram>/some/user/nvram/path/guest_VARS.fd</nvram>
|
|
<boot dev='hd'/>
|
|
</os>
|
|
<features>
|
|
<acpi/>
|
|
</features>
|
|
<clock offset='utc'/>
|
|
<devices>
|
|
<emulator>/usr/bin/qemu-system-aarch64</emulator>
|
|
<disk type='file' device='disk'>
|
|
<driver name='qemu' type='qcow2'/>
|
|
<source file='/var/lib/libvirt/images/guest.qcow2'/>
|
|
<target dev='vda' bus='virtio'/>
|
|
</disk>
|
|
<controller type='usb' index='0' model='qemu-xhci' ports='15'/>
|
|
<interface type='user'>
|
|
<mac address='52:54:00:09:a4:37'/>
|
|
<model type='virtio'/>
|
|
</interface>
|
|
<console type='pty'/>
|
|
<channel type='unix'>
|
|
<source mode='bind'/>
|
|
<target type='virtio' name='org.qemu.guest_agent.0'/>
|
|
</channel>
|
|
<memballoon model='virtio'/>
|
|
<rng model='virtio'>
|
|
<backend model='random'>/dev/urandom</backend>
|
|
</rng>
|
|
</devices>
|
|
</domain>
|