[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Diferencias

Muestra las diferencias entre dos versiones de la página.

Enlace a la vista de comparación

Ambos lados, revisión anteriorRevisión previa
Próxima revisión
Revisión previa
Próxima revisiónAmbos lados, revisión siguiente
es:howtos:hardware:arm:qemu_support_in_slackware_arm [2019/09/01 20:56 (UTC)] – [Crear una imagen de disco para QEMU] rrampes:howtos:hardware:arm:qemu_support_in_slackware_arm [2019/09/01 21:24 (UTC)] – [QEMU Bridged Mode Networking] rramp
Línea 172: Línea 172:
 <note warning>Tenga en cuenta que una vez que haya instalado Slackware ARM en esta imagen de disco debe moverlo a un directorio diferente para su almacenamiento, o se arriesga a que se destruya cuando **makeimg** se ejecute en un momento posterior.</note> <note warning>Tenga en cuenta que una vez que haya instalado Slackware ARM en esta imagen de disco debe moverlo a un directorio diferente para su almacenamiento, o se arriesga a que se destruya cuando **makeimg** se ejecute en un momento posterior.</note>
  
-===== QEMU Network Settings =====+===== Configuración de red para QEMU =====
  
-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.**+Esta sección cubre el proceso de configuración de redes de invitados para QEMU. Dos tipos de procesos son descriptos. 
 +//Network Address Translation mode (NAT)// es la primera y la forma recomendada para obtener una red red funcional en los huéspedes de QEMU. 
 +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í. 
 +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**.
  
-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.+Existen muchas formas diferentes para configurar la red de invitados para QEMU. Este documento solo cubrirá las funcionalidades de QEMU para que Slackware ARM arranqueRefié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.
  
 <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:
Línea 202: Línea 206:
  
 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. 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.
-==== QEMU Bridged Mode Networking ====+==== 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.
 es:howtos:hardware:arm:qemu_support_in_slackware_arm ()