Home
last modified time | relevance | path

Searched refs:VM (Results 1 – 25 of 47) sorted by relevance

12

/f-stack/dpdk/doc/guides/nics/
H A Dvmxnet3.rst86 * Before starting a VM, a VMXNET3 interface to a VM through VMware vSphere Client must be assigne…
93 Assigning a VMXNET3 interface to a VM using VMware vSphere Client
112 This section describes an example setup for Phy-vSwitch-VM-Phy communication.
130 -> Guest VM VMXNET3 port 0 rx burst
131 -> Guest VM 82599 VF port 0 tx burst
138 The following figure shows an example VM-to-VM communication over a Phy-VM-vSwitch-VM-Phy communica…
149 … a destination MAC address needs to be written in packets to hit the other VM's VMXNET3 interface.
154 -> Guest VM 82599 port 0 rx burst
155 -> Guest VM VMXNET3 port 1 tx burst
159 -> Guest VM VMXNET3 port 0 rx burst
[all …]
H A Dvdev_netvsc.rst23 VM migration. From a VM standpoint they appear as hot-plug devices that come
68 This driver is invoked automatically in Hyper-V VM systems unless the user
91 auto-detection in Hyper-V VM).
H A Dvirtio.rst10 for fast guest VM to guest VM communication and guest VM to host communication.
17 For basic qemu-KVM installation and other Intel EM poll mode driver in guest VM,
18 please refer to Chapter "Driver for VM Emulated Devices".
170 VM virtio port 0 Rx burst->Guest VM virtio port 0 Tx burst-> KNI Tx queue
195 VM virtio port 0 Rx burst-> Guest VM 82599 VF port1 Tx burst-> IXIA packet
200 IXIA packet generator-> Guest VM 82599 VF port1 Rx burst-> Guest VM virtio
296 to do that if the VM is created by qemu 2.6.2 or below, since the
312 #. Properly set msix vectors when starting VM:
314 Enable multi-queue when starting VM, and specify msix vectors in qemu
321 #. In VM, insert vfio module in NOIOMMU mode:
[all …]
H A Davp.rst56 * VM live-migration
71 Launching a VM with an AVP type network attachment
74 The following example will launch a VM with three network attachments. The
H A Denic.rst112 (VM-FEX), which gives the VM a dedicated
115 host to route intra-host VM traffic.
138 required. Then, using libvirt, create a VM instance with an assigned device.
161 When the VM instance is started, libvirt will bind the host VF to
167 fully provisioned until libvirt brings up the VM that it is assigned
171 seen on the VM instance and should be available for binding to a DPDK.
196 Passthrough does not require SR-IOV. If VM-FEX is not desired, the user
199 passthrough devices do not require libvirt, port profiles, and VM-FEX.
431 as assigned devices on VM instances.
432 - Currently, unbind of the ENIC kernel mode driver 'enic.ko' on the VM
[all …]
H A Dliquidio.rst87 #. Assign VF(s) to VM.
89 The VF devices may be passed through to the guest VM using qemu or
110 Use ``igb_uio`` instead of ``vfio-pci`` in VM.
H A Dintel_vf.rst72 IAVF Driver is VF driver which supports for all future Intel devices without requiring a VM update.…
73 …ver would add more and more advanced features that can be turned on in the VM if the underlying HW…
492 — qemu-kvm-0.14.0 allows a maximum of four PCI devices assigned to a VM,
588 SR-IOV (PF/VF) Approach for Inter-VM Communication
591 Inter-VM data communication is one of the traffic bottle necks in virtualization platforms.
592 SR-IOV device assignment helps a VM to attach the real device, taking advantage of the bridge in th…
600 In the NIC, writing the destination of a MAC address belongs to another cross device VM to the PF s…
605 The SR-IOV NIC switch forwards the packet to a specific VM according to the MAC destination address
606 which belongs to the destination VF on the VM.
612 Inter-VM Communication
H A De1000em.rst4 Driver for VM Emulated Devices
101 For example, to start a VM with two emulated e1000 devices, issue the following command:
H A Dbnx2x.rst187 The VF devices may be passed through to the guest VM using virt-manager or
188 virsh etc. bnx2x PMD should be used to bind the VF devices in the guest VM
H A Dthunderx.rst116 #. Pass VF device to VM context (PCIe Passthrough):
118 The VF devices may be passed through to the guest VM using qemu or
148 … **VFIO-NOIOMMU** is required only when running in VM context and should not be enabled otherwise.
H A Dqede.rst259 The VF devices may be passed through to the guest VM using ``virt-manager`` or
260 ``virsh``. QEDE PMD should be used to bind the VF devices in the guest VM
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dvm_power_management.rst19 VM-local only information (vCPU/lcore, and so on) to a host resident VM
29 VM applications can request frequency changes for a vCPU. The VM
67 **DPDK VM Application**
75 **VM Power Monitor**
99 where each VM can have several channels up to a maximum of 64 per VM. In this
102 To enable frequency changes from within a VM, the VM forwards a
120 management requests. Once the VM sends the policy to the host, the VM no
227 DPDK VM applications.
229 Each channel on a VM is present at:
838 The name of the VM or host.
[all …]
H A Dvdpa.rst101 VM to vDPA backend VM and vice versa. Here are the detailed steps. Assume A is
102 the source host with SW vhost VM and B is the destination host with vDPA.
104 1. Start vdpa sample and launch a VM with exact same parameters as the VM on A,
H A Dvhost_blk.rst22 This section shows the steps how to start a VM with the block device as
43 Start the VM
H A Dvhost_crypto.rst16 This section shows the steps how to start a VM with the crypto device as
64 Start the VM
H A Dvhost.rst21 port first and enqueued to the VM's Rx queue. Through the guest testpmd's
50 Start the VM
119 - 0 disables vm2vm, implying that VM's packets will always go to the NIC port.
196 * Failed to build DPDK in VM
/f-stack/dpdk/doc/guides/howto/
H A Dlm_virtio_vhost_user.rst4 Live Migration of VM with Virtio on host running vhost_user
90 Start the VM on host_server_1
110 **In VM on host_server_1:**
112 Setup DPDK in the VM and run testpmd in the VM.
171 Start the VM on host_server_2.
187 VM status: paused (inmigrate)
199 VM status: paused (postmigrate)
221 **In VM on host_server_2:**
237 VM status: running
242 **In VM on host_server_2:**
[all …]
H A Dlm_bond_virtio_sriov.rst4 Live Migration of VM with SR-IOV VF
19 A bonded device is created in the VM.
87 **In VM on host_server_1:**
207 **In VM on host_server_1:**
237 VM status: paused (inmigrate)
249 VM status: paused (postmigrate)
296 **In VM on host_server_2:**
310 VM status: running
327 **In VM on host_server_2:**
569 Sample VM scripts
[all …]
H A Dvirtio_user_for_container_networking.rst40 context of QEMU/VM, the basic idea here is to present a kind of virtual devices,
42 QEMU in VM's context is saved by just registering a new kind of virtual device
47 memory shared? In VM's case, qemu always shares the whole physical layout of VM
H A Dpvp_reference_benchmark.rst15 The guide covers two ways of launching the VM, either by directly calling the
38 node. Two cores are assigned to the VM vCPUs running testpmd and four are
142 VM launch
145 The VM may be launched either by calling QEMU directly, or by using libvirt.
H A Dvfd.rst48 migration, the VF application may transfer from one VM to another. It is
82 #. Start a VM with the new VF port bypassed to it.
88 #. Bind the VF port to ``igb_uio`` in the VM::
92 #. Run a DPDK application on the VF in the VM::
/f-stack/freebsd/contrib/device-tree/Bindings/reserved-memory/
H A Dxen,shared-memory.txt4 virtual machine. Typically, a region is configured at VM creation time
20 memory region used for the mapping in the borrower VM.
24 the VM config file
/f-stack/dpdk/doc/guides/vdpadevs/
H A Difc.rst27 container vDPA driver can program DMA remapping table with the VM's memory
43 IOMMU programming to enable VF DMA to VM's memory, VFIO interrupt setup to
48 in VM gets ready.
53 This function gets called when virtio driver stops device in VM.
76 Rx/Tx directly with virtio driver in VM.
/f-stack/dpdk/doc/guides/prog_guide/
H A Dswitch_representation.rst124 | hypervisor | | VM 1 | | VM 2 |
177 | hypervisor | | VM 1 | | VM 2 |
223 | hypervisor | | VM 1 | | VM 2 |
276 | hypervisor | | VM 1 | | VM 2 |
393 | hypervisor | | VM 1 | | VM 2 |
432 For instance, matching traffic sent by VM 2 would be done through an ingress
462 | hypervisor | | VM 1 | : | hypervisor | | VM 1 |
523 | hypervisor | | VM 1 |
700 | hypervisor | | VM 1 | | VM 2 |
/f-stack/dpdk/doc/guides/rel_notes/
H A Dknown_issues.rst537 VM power manager may not work on systems with more than 64 cores
541 …When using VM power manager on a system with more than 64 cores, VM(s) should not use cores 64 or …
544 VM power manager should not be used with VM(s) that are using cores 64 or above.
553 VM power manager application.

12