External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-03 20:01:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
2250a0b56f
libvirt/tests/xmconfigdata/test-fullvirt-usbmouse.xml

56 lines
1.8 KiB
XML
Raw Normal View History

Added support for input devices
2007-07-18 21:08:22 +00:00
<domain type='xen'>
<name>XenGuest2</name>
Cleanup UUID apis & constants
2007-08-09 20:19:12 +00:00
<uuid>c7a5fdb2-cdaf-9455-926a-d65c16db1809</uuid>
xml: output memory unit for clarity Make it obvious to 'dumpxml' readers what unit we are using, since our default of KiB for memory (1024) differs from qemu's default of MiB; and differs from our use of bytes for storage. Tests were updated via: $ find tests/*data tests/*out -name '*.xml' | \ xargs sed -i 's/<\(memory\|currentMemory\|hard_limit\|soft_limit\|min_guarantee\|swap_hard_limit\)>/<\1 unit='"'KiB'>/" $ find tests/*data tests/*out -name '*.xml' | \ xargs sed -i 's/<\(capacity\|allocation\|available\)>/<\1 unit='"'bytes'>/" followed by a few fixes for the stragglers. Note that with this patch, the RNG for <memory> still forbids validation of anything except unit='KiB', since the code silently ignores the attribute; a later patch will expand <memory> to allow scaled input in the code and update the RNG to match. * docs/schemas/basictypes.rng (unit): Add 'bytes'. (scaledInteger): New define. * docs/schemas/storagevol.rng (sizing): Use it. * docs/schemas/storagepool.rng (sizing): Likewise. * docs/schemas/domaincommon.rng (memoryKBElement): New define; use for memory elements. * src/conf/storage_conf.c (virStoragePoolDefFormat) (virStorageVolDefFormat): Likewise. * src/conf/domain_conf.h (_virDomainDef): Document unit used internally. * src/conf/storage_conf.h (_virStoragePoolDef, _virStorageVolDef): Likewise. * tests/*data/*.xml: Update all tests. * tests/*out/*.xml: Likewise. * tests/define-dev-segfault: Likewise. * tests/openvzutilstest.c (testReadNetworkConf): Likewise. * tests/qemuargv2xmltest.c (blankProblemElements): Likewise.
2012-02-23 00:48:38 +00:00
<memory unit='KiB'>592896</memory>
<currentMemory unit='KiB'>403456</currentMemory>
numad: Always output 'placement' of <vcpu> <vcpu> is not an optional node. The value for its 'placement' actually always defaults to 'static' in the underlying codes. (Even no 'cpuset' and 'placement' is specified, the domain process will be pinned to all the available pCPUs).
2012-05-08 16:04:36 +00:00
<vcpu placement='static'>1</vcpu>
Added support for input devices
2007-07-18 21:08:22 +00:00
<os>
tests: move xmconfig tests to WITH_LIBXL In preparation of removing the legacy Xen driver, move the xmconfig tests from WITH_XEN to WITH_LIBXL. Even though the legacy driver will be removed, we'll want to maintain the ability to convert xm config to XML. Requires fixing up the tests to account for different behavior of Xen vs libxl post parse functions. For consistency with other Xen config tests, change the <os> arch to x86_64. There is some test file fallout due to differences in handling of default values between xend and libxl. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2016-12-30 21:43:43 +00:00
<type arch='x86_64' machine='xenfv'>hvm</type>
conf: Extend <loader/> and introduce <nvram/> Up to now, users can configure BIOS via the <loader/> element. With the upcoming implementation of UEFI this is not enough as BIOS and UEFI are conceptually different. For instance, while BIOS is ROM, UEFI is programmable flash (although all writes to code section are denied). Therefore we need new attribute @type which will differentiate the two. Then, new attribute @readonly is introduced to reflect the fact that some images are RO. Moreover, the OVMF (which is going to be used mostly), works in two modes: 1) Code and UEFI variable store is mixed in one file. 2) Code and UEFI variable store is separated in two files The latter has advantage of updating the UEFI code without losing the configuration. However, in order to represent the latter case we need yet another XML element: <nvram/>. Currently, it has no additional attributes, it's just a bare element containing path to the variable store file. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Acked-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2014-08-06 11:18:53 +00:00
<loader type='rom'>/usr/lib/xen/boot/hvmloader</loader>
Added support for input devices
2007-07-18 21:08:22 +00:00
<boot dev='cdrom'/>
</os>
<features>
<acpi/>
<apic/>
Prepare xm_internal driver for new domain XML apis
2008-07-25 13:39:02 +00:00
<pae/>
Added support for input devices
2007-07-18 21:08:22 +00:00
</features>
Xen: tests: use latest XEND_CONFIG_VERSION in xm/xl tests Change all tests to use the latest XEND_CONFIG_VERSION (XEND_CONFIG_VERSION_3_1_0 = 4). Fix tests that do not conform to the latest version. Signed-off-by: Jim Fehlig <jfehlig@suse.com>
2015-12-05 01:09:28 +00:00
<clock offset='variable' adjustment='0' basis='utc'/>
Prepare xm_internal driver for new domain XML apis
2008-07-25 13:39:02 +00:00
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
Added support for input devices
2007-07-18 21:08:22 +00:00
<devices>
tests: Xen: use qemu-system-i386 for emulator Many of the old xm and sexpr test files used qemu-dm as the emulator. Modern Xen systems no longer use the old, forked qemu-dm, instead preferring the distro provided qemu or an "upstream" qemu that is built when the Xen tools are built. This qemu is typically installed in /usr/lib/xen/bin/qemu-system-i386. The libxl test files already use /usr/lib/xen/bin/qemu-system-i386. For consistency, change the old test files to use the same emulator Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2018-04-11 16:38:14 +00:00
<emulator>/usr/lib/xen/bin/qemu-system-i386</emulator>
Added support for input devices
2007-07-18 21:08:22 +00:00
<disk type='block' device='disk'>
tests: move xmconfig tests to WITH_LIBXL In preparation of removing the legacy Xen driver, move the xmconfig tests from WITH_XEN to WITH_LIBXL. Even though the legacy driver will be removed, we'll want to maintain the ability to convert xm config to XML. Requires fixing up the tests to account for different behavior of Xen vs libxl post parse functions. For consistency with other Xen config tests, change the <os> arch to x86_64. There is some test file fallout due to differences in handling of default values between xend and libxl. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2016-12-30 21:43:43 +00:00
<driver name='phy' type='raw'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
<source dev='/dev/HostVG/XenGuest2'/>
Added disk target bus type to Xen driver
2008-05-08 14:41:56 +00:00
<target dev='hda' bus='ide'/>
xen: use virDomainDefPostParse for parsing XM/XL/SEXPR cofings This change ensures to call driver specific post-parse code to modify domain definition after parsing hypervisor config the same way we do after parsing XML. Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2015-11-28 04:33:55 +00:00
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
</disk>
<disk type='file' device='cdrom'>
tests: move xmconfig tests to WITH_LIBXL In preparation of removing the legacy Xen driver, move the xmconfig tests from WITH_XEN to WITH_LIBXL. Even though the legacy driver will be removed, we'll want to maintain the ability to convert xm config to XML. Requires fixing up the tests to account for different behavior of Xen vs libxl post parse functions. For consistency with other Xen config tests, change the <os> arch to x86_64. There is some test file fallout due to differences in handling of default values between xend and libxl. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2016-12-30 21:43:43 +00:00
<driver name='file' type='raw'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
<source file='/root/boot.iso'/>
Added disk target bus type to Xen driver
2008-05-08 14:41:56 +00:00
<target dev='hdc' bus='ide'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
<readonly/>
xen: use virDomainDefPostParse for parsing XM/XL/SEXPR cofings This change ensures to call driver specific post-parse code to modify domain definition after parsing hypervisor config the same way we do after parsing XML. Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2015-11-28 04:33:55 +00:00
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
</disk>
libxl: Add implicit xenbus controller All Xen domains have a xenbus device. Implicitly add one if not already explicitly specified in the domain config. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2019-03-07 00:43:21 +00:00
<controller type='xenbus' index='0'/>
domain: add implicit controllers from post parse Seems like the natural fit, since we are already adding other XML bits in the PostParse routine. Previously AddImplicitControllers was only called at the end of XML parsing, meaning code that builds a DomainDef by hand had to manually call it. Now those PostParse callers get it for free. There's some test churn here; xen xm and sexpr test suite bits weren't calling this before, but now they are, so you'll see new IDE controllers. I don't think this will cause problems in practice, since the code already needs to handle these implicit controllers like in the case when a user defines their own XML.
2016-01-08 03:49:57 +00:00
<controller type='ide' index='0'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
<interface type='bridge'>
Prepare xm_internal driver for new domain XML apis
2008-07-25 13:39:02 +00:00
<mac address='00:16:3e:66:92:9c'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
<source bridge='xenbr1'/>
Fix XM driver VIF config creation
2009-04-24 12:17:50 +00:00
<script path='vif-bridge'/>
xen tests: Fix missing "type ioemu" with rhel5-api The most common cause of errors with rhel5-api turn on was missing "(type ioemu)" in sexpr or its equivalent in XM configuration file. This happens because the presence of that part in sexpr (or cfg) depends on xen version the host is running. Let's avoid it by explicitly specifying interface model which ensures "type ioemu" will always be emitted. This patch adds <model type='e1000'/> withing the interface element in all affected xml files. And (model 'e1000') to all corresponding sexpr files with similar fix to cfg files. Such configuration works regardless on Xen version.
2010-08-23 12:58:08 +00:00
<model type='e1000'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
</interface>
<input type='mouse' bus='usb'/>
<input type='mouse' bus='ps2'/>
conf: Add keyboard input device type There is no keyboard support currently in libvirt. For some platforms (PPC64 QEMU) this makes graphics unusable, since the keyboard is not implicit and it can't be added via libvirt. Signed-off-by: Li Zhang <zhlcindy@linux.vnet.ibm.com> Signed-off-by: Ján Tomko <jtomko@redhat.com>
2014-02-17 10:17:53 +00:00
<input type='keyboard' bus='ps2'/>
conf: add <listen> subelement to domain <graphics> element Once it's plugged in, the <listen> element will be an optional replacement for the "listen" attribute that graphics elements already have. If the <listen> element is type='address', it will have an attribute called 'address' which will contain an IP address or dns name that the guest's display server should listen on. If, however, type='network', the <listen> element should have an attribute called 'network' that will be set to the name of a network configuration to get the IP address from. * docs/schemas/domain.rng: updated to allow the <listen> element * docs/formatdomain.html.in: document the <listen> element and its attributes. * src/conf/domain_conf.[hc]: 1) The domain parser, formatter, and data structure are modified to support 0 or more <listen> subelements to each <graphics> element. The old style "legacy" listen attribute is also still accepted, and will be stored internally just as if it were a separate <listen> element. On output (i.e. format), the address attribute of the first <listen> element of type 'address' will be duplicated in the legacy "listen" attribute of the <graphic> element. 2) The "listenAddr" attribute has been removed from the unions in virDomainGRaphicsDef for graphics types vnc, rdp, and spice. This attribute is now in the <listen> subelement (aka virDomainGraphicsListenDef) 3) Helper functions were written to provide simple access (both Get and Set) to the listen elements and their attributes. * src/libvirt_private.syms: export the listen helper functions * src/qemu/qemu_command.c, src/qemu/qemu_hotplug.c, src/qemu/qemu_migration.c, src/vbox/vbox_tmpl.c, src/vmx/vmx.c, src/xenxs/xen_sxpr.c, src/xenxs/xen_xm.c Modify all these files to use the listen helper functions rather than directly referencing the (now missing) listenAddr attribute. There can be multiple <listen> elements to a single <graphics>, but the drivers all currently only support one, so all replacements of direct access with a helper function indicate index "0". * tests/* - only 3 of these are new files added explicitly to test the new <listen> element. All the others have been modified to reflect the fact that any legacy "listen" attributes passed in to the domain parse will be saved in a <listen> element (i.e. one of the virDomainGraphicsListenDefs), and during the domain format function, both the <listen> element as well as the legacy attributes will be output.
2011-07-07 04:20:28 +00:00
<graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1' passwd='123poi'>
<listen type='address' address='127.0.0.1'/>
</graphics>
tests: fix xen-related tests My commit 6879be4 moved the addition of the implicit video device from the XML parser to the PostParse function, but did not regenerate all the tests.
2016-04-12 12:58:43 +00:00
<video>
tests: move xmconfig tests to WITH_LIBXL In preparation of removing the legacy Xen driver, move the xmconfig tests from WITH_XEN to WITH_LIBXL. Even though the legacy driver will be removed, we'll want to maintain the ability to convert xm config to XML. Requires fixing up the tests to account for different behavior of Xen vs libxl post parse functions. For consistency with other Xen config tests, change the <os> arch to x86_64. There is some test file fallout due to differences in handling of default values between xend and libxl. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2016-12-30 21:43:43 +00:00
<model type='cirrus' vram='8192' heads='1' primary='yes'/>
tests: fix xen-related tests My commit 6879be4 moved the addition of the implicit video device from the XML parser to the PostParse function, but did not regenerate all the tests.
2016-04-12 12:58:43 +00:00
</video>
libxl: add support for memballoon device All Xen PV and HVM with PV driver support a memory balloon device, which cannot be disabled through the toolstack. Model the device in the libxl driver, similar to the recently removed xend-based driver. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2018-04-10 00:15:17 +00:00
<memballoon model='xen'/>
Added support for input devices
2007-07-18 21:08:22 +00:00
</devices>
</domain>
Reference in New Issue Copy Permalink