| Ambos lados, revisión anteriorRevisión previaPróxima revisión | Revisión previaPróxima revisiónAmbos lados, revisión siguiente |
| es:howtos:hardware:arm:qemu_support_in_slackware_arm [2019/09/01 21:03 (UTC)] – [QEMU Network Settings] rramp | es:howtos:hardware:arm:qemu_support_in_slackware_arm [2019/11/10 12:23 (UTC)] – [Modo de red NAT para QEMU] rramp |
|---|
| La segunda forma es el //modo puente//. | La segunda forma es el //modo puente//. |
| El modo NAT no permite el acceso directo a la red física del host x86 Slackware y el modo puente sí. | El modo NAT no permite el acceso directo a la red física del host x86 Slackware y el modo puente sí. |
| | Es mejor utilizar el modo puente si planea realizar operaciones de red más avanzadas que requieran acceso completo al host y a la red física del host. **La mayoría de los usuarios querrán usar el modo NAT**. |
| |
| This section covers the process of setting up QEMU guest networking. Two different processes will be described. //Network Address Translation mode (NAT)// is the first and recommended way to get a functional network in QEMU guests. The second is //bridged mode//. NAT mode does not allow direct access to the Slackware x86 host's physical network and bridged mode does. It is best to use bridged mode if you plan on doing any more advanced network operations that require full access to the host and the host's physical network. **Most users will want to use NAT mode.** | Existen muchas formas diferentes para configurar la red de invitados para QEMU. Este documento solo cubrirá las funcionalidades de QEMU para que Slackware ARM arranque. Refiérase a las paginas del manual o [[https://www.qemu.org/documentation/ | a la documentación de QEMU]] si necesitas una explicación más detallada. |
| | |
| There are many different ways to configure QEMU guest networking. This document will only cover the QEMU functionality required to boot Slackware ARM. Refer to the QEMU man pages or the [[https://www.qemu.org/documentation/ | QEMU documentation]] if you need further explanation. | |
| |
| <note warning>Later on when you boot the Slackware ARM installer in QEMU you may need to modify the **txqueuelen** for your network interfaces. This is because large Slackware packages time out while being downloaded from the NFS share on the host. This happens because QEMU emulation is very slow. The NFS daemon on your host machine occasionally shuts down the network socket before large packages (rust, kernel-firmware, etc) finish being copied to the SD Card. Setting the txqueuelen to **10000** for all network interfaces should be sufficient to prevent this anomaly. The following command seems to resolve this issue: | <note warning>Later on when you boot the Slackware ARM installer in QEMU you may need to modify the **txqueuelen** for your network interfaces. This is because large Slackware packages time out while being downloaded from the NFS share on the host. This happens because QEMU emulation is very slow. The NFS daemon on your host machine occasionally shuts down the network socket before large packages (rust, kernel-firmware, etc) finish being copied to the SD Card. Setting the txqueuelen to **10000** for all network interfaces should be sufficient to prevent this anomaly. The following command seems to resolve this issue: |
| Run this command for each network interface actively used by QEMU. | Run this command for each network interface actively used by QEMU. |
| </note> | </note> |
| ==== QEMU NAT Mode Networking ==== | ==== Modo de red NAT para QEMU ==== |
| NAT mode does not require any additional configuration on the Slackware x86 host machine or in the QEMU guest machine. Here is a shortened example of a QEMU guest being launched with NAT mode networking: | El modo NAT no requiere una configuración adicional sobre una máquina Slackware x86 o en la máquina invitada QEMU. |
| | Aquí hay un ejemplo abreviado de un invitado de QEMU que está siendo lanzado con el modo de red NAT: |
| <code> | <code> |
| # cd /export/armhost | # cd /export/armhost |
| </code> | </code> |
| |
| The **-net nic** and **-net user** options enable QEMU to start the Slackware ARM guest with NAT mode networking enabled. These settings are documented further in both the **installer_launch** and **disk_launch** helper scripts. | Las opciones **-net nic** y **-net user** permiten que QEMU inicie el huésped de Slackware ARM con el modo de red en modo NAT activado. |
| | Estos ajustes se documentan más en los scripts de ayuda **installer_launch** y **disk_launch**. |
| With NAT mode enabled, QEMU launches a virtual network of 10.0.2.0/24. The QEMU guest will be assigned the IP address 10.0.2.15. The guest can access the Slackware x86 host at 10.0.2.2 and the QEMU DNS server runs at 10.0.2.3. QEMU does not have direct access to the host's Local Area Network. This means that the QEMU guest isn't assigned a physical IP address by your router DHCP service. You will not be able to ping the QEMU guest from the host machine but the guest should be able to ping the host machine at 10.0.2.2. The QEMU guest should be able to access the internet and communicate with the host machine. | Con el modo NAT habilitado, QEMU lanza una red virtual 10.0.2.0/24. |
| ==== QEMU Bridged Mode Networking ==== | Al huésped de QEMU se le asignará la dirección IP 10.0.2.15. |
| | El invitado puede acceder al host x86 de Slackware en 10.0.2.2 y el servidor DNS de QEMU se ejecuta en 10.0.2.3. |
| | QEMU no tiene acceso directo a la red de área local del host. Esto significa que al huésped de QEMU no se le asigna una dirección IP física por el servicio DHCP de su router. |
| | No podrá hacer ping al invitado de QEMU desde la máquina anfitriona, pero el invitado debería poder hacer ping a la máquina anfitriona en 10.0.2.2. |
| | El huésped de QEMU debe poder acceder a Internet y comunicarse con la máquina anfitriona. |
| | ==== Modo de red puente para QEMU ==== |
| |
| The best way to set up a bridged network interface for QEMU is with the provided helper script, rc.local-additions. If you choose to take this route, you need to disable the NetworkManager service. NetworkManager comes with Slackware, but it is not developed by Slackware. As a result, the process of configuring a bridge with NetworkManager is not supported in this guide. | The best way to set up a bridged network interface for QEMU is with the provided helper script, rc.local-additions. If you choose to take this route, you need to disable the NetworkManager service. NetworkManager comes with Slackware, but it is not developed by Slackware. As a result, the process of configuring a bridge with NetworkManager is not supported in this guide. |
