Searched refs:exported (Results 1 – 15 of 15) sorted by relevance
49 if (chr->exported) { in dbus_display_chardev_export()57 chr->exported = true; in dbus_display_chardev_export()65 if (!chr->exported) { in dbus_display_chardev_unexport()70 chr->exported = false; in dbus_display_chardev_unexport()
127 bool exported; member
21 == verifying the exported snapshot with patterns, method 1 ==27 == verifying the exported snapshot with patterns, method 2 ==
45 # devices can then be exported using @nbd-server-add. The NBD server221 # @device: The device name or node name of the node to be exported347 # Describes a block export, i.e. how single node should be exported on355 # @node-name: The node name of the block node to be exported451 # @node-name: The node name of the block node that is exported
3319 # @dir: directory to be exported as FAT image
17 # This principal needs to be exported to the keytab file listed below
1435 have an inserted media on them are automatically exported; in this case,1451 exported device writable too. The export name is controlled by *name*,
1811 .virtfs\_metadata directory. Directories exported by this1944 .virtfs\_metadata directory. Directories exported by this
26 * which means that nothing is exported at all.
83 exported. ``writable`` determines whether or not the export allows write106 ``growable`` is set, writes after the end of the exported file will grow the
33 the command should be exported by some QEMU subsystem. But it can also be225 QMP commands should use the error interface exported by the error.h header
32 calling exported functions.1343 going to run unless that ``AVOCADO_ALLOW_LARGE_STORAGE=1`` is exported on1352 exported on the environment.
113 exported *qemu_plugin* functions.
506 QEMU can access directly to block device exported using the Network Block Device520 In this case, the block device must be exported using ``qemu-nbd``:
1825 The back-end is responsible of keeping its own table with exported dma-buf fds.