| /qemu/docs/system/devices/ |
| H A D | net.rst | 3 Network emulation
6 QEMU can simulate several network cards (e.g. PCI or ISA cards on the PC
7 target) and can connect them to a network backend on the host or an
8 emulated hub. The various host network backends can either be used to
9 connect the NIC of the guest to a real network (e.g. by using a TAP
10 devices or the non-privileged user mode network stack), or to other
12 socket host network backend).
14 Using TAP network interfaces
17 This is the standard way to connect QEMU to a real network. QEMU adds a
18 virtual network device on your host (called ``tapN``), and you can then
[all …]
|
| H A D | igb.rst | 22 network.sh -6mta
32 Using igb should be nothing different from using another network device. See
|
| /qemu/include/io/ |
| H A D | net-listener.h | 2 * QEMU network listener
66 * Create a new network listener service, which is not
76 * @listener: the network listener object
88 * @listener: the network listener object
105 * @listener: the network listener object
118 * @listener: the network listener object
138 * @listener: the network listener object
153 * @listener: the network listener object
167 * @listener: the network listener object
177 * @listener: the network listener object
|
| /qemu/qapi/ |
| H A D | net.json | 14 # Sets the link status of a virtual network adapter.
16 # @name: the device name of the virtual network adapter
21 # - If @name is not a valid network device, DeviceNotFound
25 # .. note:: Not all network adapters support setting link status.
26 # This command will succeed even if the network adapter does not
40 # Add a network backend.
47 # - If @type is not a valid network backend, DeviceNotFound
62 # Remove a network backend.
64 # @id: the name of the network backend to remove
67 # - If @id is not a valid network backend, DeviceNotFound
[all …]
|
| /qemu/docs/system/ |
| H A D | replay.rst | 30 input devices, serial ports, and network.
62 * ``-net none`` option should be specified when network is not used,
63 because QEMU adds network card by default. When network is needed,
65 in :ref:`network-label` section.
78 the log: mouse and keyboard input, network packets, audio controller input,
93 interacting with user or network.
161 Network devices
164 Record and replay for network interactions is performed with the network filter.
171 Replay network filter is used to record and replay network packets. While
174 injected into the network device. All interactions with network backend
|
| H A D | authz.rst | 6 When configuring a QEMU network backend with either TLS certificates or SASL
22 When configuring the QEMU backend as a network server with TLS, there
41 When configuring the QEMU backend as a network server with SASL, upon
95 In some network backends it will be desirable to grant access to a range of
233 needs to be associated with a network service. The authorization driver object
236 The property to set in the network service will vary depending on the type of
237 identity to verify. By convention, any network server backend that uses TLS
|
| H A D | tls.rst | 3 TLS setup for network services
6 Almost all network services in QEMU have the ability to use TLS for
28 Assuming that the QEMU network services will only ever be exposed to
135 usage in a web server. Although QEMU network services are not in fact
188 certificate is intended for usage in a web client. Although QEMU network
246 used for network services and clients. It requires specifying the
250 credentials can be used for multiple network backends, so VNC,
266 used for a network client or server, and determines which PEM files are
291 Network services which support TLS will all have a ``tls-creds``
|
| H A D | target-mips.rst | 28 - PCI network cards (PCnet32 and others)
71 - RTL8139D as a network card chipset
90 - MIPSnet network emulation
|
| H A D | introduction.rst | 144 how a block device is stored, how network devices see the
145 network or how a serial device is directed to the outside world.
176 As the ``virt`` platform doesn't have any default network or storage
186 We connect the user-mode networking to our network device. As
|
| /qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 107 Booting from a network device
110 The firmware that ships with QEMU includes a small TFTP network bootloader
112 important for booting via the network. If you don't specify the ``bootindex``
113 property here, the network bootloader won't be taken into consideration and
114 the network boot will fail. For a successful network boot, try something
120 The network bootloader also has basic support for pxelinux.cfg-style
|
| /qemu/tests/vm/ |
| H A D | centos-8-aarch64.ks | 23 # Network information
24 network --bootproto=dhcp --device=enp0s1 --onboot=off --ipv6=auto --no-activate
25 network --hostname=localhost.localdomain
|
| /qemu/tests/docker/ |
| H A D | Makefile.include | 176 @echo ' NETWORK=1 Enable virtual network interface with default backend.'
177 @echo ' NETWORK=$$BACKEND Enable virtual network interface with $$BACKEND.'
220 $(if $(NETWORK),$(if $(subst $(NETWORK),,1),--net=$(NETWORK)),--net=none) \
243 docker-test-rust%: NETWORK=1
|
| /qemu/bsd-user/ |
| H A D | errno_defs.h | 84 /* ipc/network software -- argument errors */
98 /* ipc/network software -- operational errors */
99 #define TARGET_ENETDOWN 50 /* Network is down */
100 #define TARGET_ENETUNREACH 51 /* Network is unreachable */
101 #define TARGET_ENETRESET 52 /* Network dropped connection on reset */
125 /* Network File System */
|
| /qemu/docs/system/i386/ |
| H A D | xen.rst | 60 memory for PV back ends (disk, network, etc.). Since QEMU only supports v1
72 block and network drivers instead.
74 Those paravirtual Xen block, network (and console) devices can be created
85 The Xen network device is ``xen-net-device``, which becomes the default NIC
87 by QEMU should automatically work and present a Xen network device to the
|
| /qemu/tests/functional/ |
| H A D | test_aarch64_hotplug_pci.py | 46 # Check for initial state: 2 network adapters, lo and enp0s1.
51 # Hotplug one network adapter to the root port, i.e. pcie.1 bus.
61 # Check if there is a new network adapter.
|
| H A D | test_netdev_ethtool.py | 3 # ethtool tests for emulated network devices
5 # This test leverages ethtool's --test sequence to validate network
33 # This custom kernel has drivers for all the supported network
|
| /qemu/linux-user/mips/ |
| H A D | target_errno_defs.h | 62 #define TARGET_ENONET 64 /* Machine is not on the network */
88 #define TARGET_ENOTUNIQ 80 /* Name not unique on network */
142 #define TARGET_ENETDOWN 127 /* Network is down */
144 #define TARGET_ENETUNREACH 128 /* Network is unreachable */
146 #define TARGET_ENETRESET 129 /* Network dropped connection because of reset */
|
| /qemu/ |
| H A D | qemu-options.hx | 668 " 'drives': floppy (a), hard disk (c), CD-ROM (d), network (n)\n"
678 (Etherboot from network adapter 1-4), hard disk boot is the default.
707 # try to boot from network first, then from hard disk
1113 address is the BMC's address on the I2C network of management
1152 simulator nor QEMU is exposed to any outside network.
1707 network. By default copy-on-read is off.
1920 file system by using the 9P network protocol for communication between
2491 The client is specified by the display. For reverse network
2620 Possible causes for the latter are flaky network connections, or
2770 …This argument can be repeated multiple times. Its main use is to allow network interfaces be crea…
[all …]
|
| /qemu/linux-user/generic/ |
| H A D | target_errno_defs.h | 75 #define TARGET_ENONET 64 /* Machine is not on the network */
87 #define TARGET_ENOTUNIQ 76 /* Name not unique on network */
111 #define TARGET_ENETDOWN 100 /* Network is down */
112 #define TARGET_ENETUNREACH 101 /* Network is unreachable */
113 #define TARGET_ENETRESET 102 /* Network dropped connection because of reset */
|
| /qemu/include/system/ |
| H A D | replay.h | 153 /* Network */
155 /*! Registers replay network filter attached to some backend. */
157 /*! Unregisters replay network filter. */
159 /*! Called to write network packet to the replay log. */
|
| /qemu/replay/ |
| H A D | replay-internal.h | 189 /* Network devices */
191 /*! Called to run network event. */
193 /*! Writes network event to the file. */
195 /*! Reads network from the file. */
|
| /qemu/docs/devel/ |
| H A D | replay.rst | 23 E.g. network packets are written into the log when they arrive into the virtual
24 network adapter.
44 * network filter for recording and replaying the packets
220 of the network connections, that could be broken by the remote timeouts).
280 - REPLAY_ASYNC_EVENT_NET. Incoming network packet. Followed by:
282 - 1-byte network adapter id.
|
| /qemu/linux-user/sparc/ |
| H A D | target_errno_defs.h | 41 #define TARGET_ENETDOWN 50 /* Network is down */
43 #define TARGET_ENETUNREACH 51 /* Network is unreachable */
101 #define TARGET_ENONET 80 /* Machine is not on the network */
171 #define TARGET_ENOTUNIQ 115 /* Name not unique on network */
|
| /qemu/pc-bios/s390-ccw/ |
| H A D | netmain.c | 2 * S390 virtio-ccw network boot loading program
9 * And based on the network loading code from SLOF (netload.c)
220 puts("Could not initialize network device"); in net_init()
517 puts("Network boot starting..."); in netmain()
526 puts("Network initialization failed."); in netmain()
541 puts("Network loading done, starting kernel..."); in netmain()
545 puts("Failed to load OS from network."); in netmain()
|
| /qemu/docs/devel/migration/ |
| H A D | postcopy.rst | 205 error happens (in this case, mostly network errors), QEMU cannot easily
213 - When network issue occurs, both QEMU will go into **POSTCOPY_PAUSED**
216 - When the network is recovered (or a new network is provided), the admin
229 can be pages sent right during the window when the network is
|