Re: WMware no tiene acceso a la RED ni internet debido a problemas en configuración
Te has enterado de algo de unos parches de vmware para kernel 2.6.14?
No estoy muy seguro del tema pero googleando 1 poco e visto esta web,
échale un vistazo que no la he visto entera.
http://www.vmware.com/community/thread.jspa?threadID=26522&tstart=30
2005/12/14, Alejandro Garrido <garridomota@gmail.com>:
> Saludos lista que tal?. Bueno les escribo para presentarles el problema
> que tengo con VMware.
>
> El VMware me esta funcionando de hecho ya instalé el WindowsXP sin
> problemas pero tengo problemas con la RED de Vmware o lógicamente con el
> internet. Con esto quiero decir que no tengo ni RED ni Internet.
> Actualmente estoy en Debian Etch con un kernel 2.6.14.3 compilado por mi
> mismo y funcionando bien.
> El problema es el siguiente. Pude hacer funcionar Vmware pero a que
> punto? El que desactivo la REd fui yo mismo porque si no el VMware no me
> arranca. Cuando llego a la pregunta "Do you want networking for your
> virtual machines? (yes/no/help) [yes]" Pues tengo que colocar NO porque
> si coloco si Sencillamente aborta la configuración del Vmware.
>
> Les voy a pegar __/TODO/__ el proceso desde "Do you want networking for
> your virtual machines? (yes/no/help) [yes]" para que vean que pasa he
> probado varias en las preguntas que prosiguen a "Do you want networking
> for your virtual machines?" pero nada
>
> PD: No me manden a usar qemu que ya lo probe y no me gusto para nada
> debido a lo lento que es. También se que existe kqemu para acelerar el
> qemu pero el kqemu no es Software Libre y si es para eso me voy por
> Vmware que tampoco lo es pero es rápido.
>
> Aquí les paso todo el proceso:
>
> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::.
>
> Do you want networking for your virtual machines? (yes/no/help) [no] yes
>
> This program previously created the file /dev/vmnet0, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet1, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet2, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet3, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet4, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet5, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet6, and was about to
> remove
> it. Somebody else apparently did it already.
>
> This program previously created the file /dev/vmnet7, and was about to
> remove
> it. Somebody else apparently did it already.
>
> Configuring a bridged network for vmnet0.
>
> The following bridged networks have been defined:
>
> . vmnet0 is bridged to eth0
>
> All your ethernet interfaces are already bridged.
>
> Do you want to be able to use NAT networking in your virtual machines?
> (yes/no)
> [yes] no
>
> Do you want to be able to use host-only networking in your virtual machines?
> [no]
>
> Extracting the sources of the vmnet module.
>
> Building the vmnet module.
>
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config0/vmnet-only'
> make -C /lib/modules/2.6.14.313-12-05/build/include/.. SUBDIRS=$PWD
> SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/Por_ver/linux-2.6.14.3'
> CC [M] /tmp/vmware-config0/vmnet-only/driver.o
> In file included from /tmp/vmware-config0/vmnet-only/vnet.h:14,
> from /tmp/vmware-config0/vmnet-only/vnetInt.h:10,
> from /tmp/vmware-config0/vmnet-only/driver.c:40:
> /tmp/vmware-config0/vmnet-only/vm_atomic.h:54:5: warning: "_MSC_VER" is
> not defined
> In file included from /tmp/vmware-config0/vmnet-only/vm_oui.h:13,
> from /tmp/vmware-config0/vmnet-only/vnetInt.h:11,
> from /tmp/vmware-config0/vmnet-only/driver.c:40:
> /tmp/vmware-config0/vmnet-only/vm_basic_asm.h:48:5: warning: "_MSC_VER"
> is not defined
> /tmp/vmware-config0/vmnet-only/driver.c: In function 'VNetProcessOwnsPort':
> /tmp/vmware-config0/vmnet-only/driver.c:1698: error: 'struct
> files_struct' has no member named 'max_fds'
> make[2]: *** [/tmp/vmware-config0/vmnet-only/driver.o] Error 1
> make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2
> make[1]: Leaving directory `/usr/src/Por_ver/linux-2.6.14.3'
> make: *** [vmnet.ko] Error 2
> make: Leaving directory `/tmp/vmware-config0/vmnet-only'
> Unable to build the vmnet module.
>
> For more information on how to troubleshoot module-related problems, please
> visit our Web site at
> "http://www.vmware.com/download/modules/modules.html"; and
> "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";.
>
> Execution aborted.
>
> :::::::::::::::::::::::::::::::::::::::::::::::::::::
>
> --
> Salu2
> Atentamente:
> Alejandro Garrido Mota
> GNU/Linux Debian Etch
> En kernel 2.6.11.7
> Usuario Linux registrado #386758
> Caracas-Venezuela
> GPG Key Fingerprint = F6A7 EF7E 4688 70C6 6B37 A8EF F6B0 9645 B24B F200
>
>
> --
> To UNSUBSCRIBE, email to debian-user-spanish-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--
DoNoBaN
Reply to: