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 anterior Revisión previa
Próxima revisión
Revisión previa
es:howtos:hardware:arm:qemu_support_in_slackware_arm [2019/09/01 21:23 (UTC)]
rramp [Configuración de red para QEMU]
es:howtos:hardware:arm:qemu_support_in_slackware_arm [2019/09/01 21:38 (UTC)]
rramp [QEMU NAT Mode Networking]
Línea 190: Línea 190:
 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
Línea 206: Línea 207:
  
 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.

En otros idiomas
QR Code
QR Code es:howtos:hardware:arm:qemu_support_in_slackware_arm (generated for current page)