Re: Anyone knows how to install VMware Server 2.0.2 on F13?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I thought so too. But after many hours of trying I found only xen
paravirt worked, sort of. The speed is crawling, and there is no
screen scaling, 800X600 only.

[root@localhost xyz123]# uname -a
Linux localhost.localdomain 2.6.33.6-147.fc13.x86_64 #1 SMP Tue Jul 6
22:32:17 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
With a cpu does not support paravirt:
CPU0: Intel(R) Pentium(R) Dual  CPU  E2140  @ 1.60GHz stepping 0b

If you think there is hope to get either KVM or xen to work on my
machine, then let's try it.
Thanks.

On Wed, Jul 14, 2010 at 7:42 AM, Itamar Reis Peixoto
<itamar@xxxxxxxxxxxxxxxx> wrote:
> On Wed, Jul 14, 2010 at 8:40 AM, Yanglong ZHU <yanglong.zhu@xxxxxxxxx> wrote:
>> The VMware's script vmware-config-tools.pl asks for
>>
>> What is the location of the directory of C header files that match your running
>> kernel? [/usr/src/linux/include]
>>
>> I tried all other look like include directories, none worked except
>> /usr/src/kernels/2.6.33.6-147.fc13.x86_64/include
>>
>> After searching and copying the utsrelease.h file as in the following,
>> I got another set of error messages.
>>
>> [root@localhost xyz123]# find . -iname '*relea*'
>> ./config/kernel.release
>> ./generated/utsrelease.h
>> [root@localhost xyz123]# cp -p generated/utsrelease.h linux/
>>
>> By the way, those web sites referred to towards the end of the error
>> message did not have much anything. Even when I was logged in.
>>
>> -----------------------------------
>> What is the location of the directory of C header files that match your running
>> kernel? [/usr/src/linux/include]
>> /usr/src/kernels/2.6.33.6-147.fc13.x86_64/include
>>
>> Extracting the sources of the vmmon module.
>>
>> Building the vmmon module.
>>
>> Using 2.6.x kernel build system.
>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>> make -C /usr/src/kernels/2.6.33.6-147.fc13.x86_64/include/..
>> SUBDIRS=$PWD SRCROOT=$PWD/. modules
>> make[1]: Entering directory `/usr/src/kernels/2.6.33.6-147.fc13.x86_64'
>> CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
>> In file included from /tmp/vmware-config0/vmmon-only/linux/driver.c:31:
>> /tmp/vmware-config0/vmmon-only/./include/compat_wait.h:78: error:
>> conflicting types for ‘poll_initwait’
>> include/linux/poll.h:70: note: previous declaration of ‘poll_initwait’ was here
>> In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:38,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.c:99:
>> /tmp/vmware-config0/vmmon-only/./include/vm_basic_types.h:108:7:
>> warning: "__FreeBSD__" is not defined
>> In file included from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:32,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.h:29,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.c:101:
>> /tmp/vmware-config0/vmmon-only/./include/x86msr.h:164:1: warning:
>> "MSR_THERM2_CTL" redefined
>> In file included from
>> /usr/src/kernels/2.6.33.6-147.fc13.x86_64/arch/x86/include/asm/msr.h:4,
>> from /usr/src/kernels/2.6.33.6-147.fc13.x86_64/arch/x86/include/asm/processor.h:21,
>> from include/linux/prefetch.h:14,
>> from include/linux/list.h:6,
>> from include/linux/module.h:9,
>> from /tmp/vmware-config0/vmmon-only/./include/compat_module.h:27,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.c:26:
>> /usr/src/kernels/2.6.33.6-147.fc13.x86_64/arch/x86/include/asm/msr-index.h:230:1:
>> warning: this is the location of the previous definition
>> In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:103,
>> from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:37,
>> from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:33,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.h:29,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.c:101:
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:329:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:333:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:401:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:407:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:460:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:506:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:551:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:595:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:640:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:684:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:729:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:773:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:775:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:816:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:860:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:862:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:903:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:945:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:947:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:986:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1028:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1030:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1069:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1223:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1227:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1313:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1536:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1663:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1796:7: warning:
>> "_MSC_VER" is not defined
>> In file included from
>> /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:39,
>> from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.c:103:
>> /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:486:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:779:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:820:7: warning:
>> "_MSC_VER" is not defined
>> /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:922:7: warning:
>> "_MSC_VER" is not defined
>> In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
>> from /tmp/vmware-config0/vmmon-only/linux/driver.c:103:
>> /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7:
>> warning: "_MSC_VER" is not defined
>> In file included from /tmp/vmware-config0/vmmon-only/linux/driver.c:119:
>> /tmp/vmware-config0/vmmon-only/./common/hostif.h:53:7: warning:
>> "WINNT_DDK" is not defined
>> /tmp/vmware-config0/vmmon-only/linux/driver.c: In function
>> ‘LinuxDriverSyncCallOnEachCPU’:
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1423: error: too many
>> arguments to function ‘smp_call_function’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1987: error: ‘struct
>> task_struct’ has no member named ‘euid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1987: error: ‘struct
>> task_struct’ has no member named ‘uid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1988: error: ‘struct
>> task_struct’ has no member named ‘fsuid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1988: error: ‘struct
>> task_struct’ has no member named ‘uid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1989: error: ‘struct
>> task_struct’ has no member named ‘egid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1989: error: ‘struct
>> task_struct’ has no member named ‘gid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1990: error: ‘struct
>> task_struct’ has no member named ‘fsgid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:1990: error: ‘struct
>> task_struct’ has no member named ‘gid’
>> /tmp/vmware-config0/vmmon-only/linux/driver.c:2007: error: too many
>> arguments to function ‘smp_call_function’
>> make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
>> make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
>> make[1]: Leaving directory `/usr/src/kernels/2.6.33.6-147.fc13.x86_64'
>> make: *** [vmmon.ko] Error 2
>> make: Leaving directory `/tmp/vmware-config0/vmmon-only'
>> Unable to build the vmmon module.
>>
>> For more information on how to troubleshoot module-related problems, please
>> visit our Web site at "http://www.vmware.com/go/unsup-linux-products"; and
>> "http://www.vmware.com/go/unsup-linux-tools";.
>>
>> Execution aborted.
>>
>> [root@localhost xyz123]#
>> --
>> users mailing list
>> users@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe or change subscription options:
>> https://admin.fedoraproject.org/mailman/listinfo/users
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>>
>
>
>
> don`t use vmware
>
> use KVM or xen
>
>
>
> --
> ------------
>
> Itamar Reis Peixoto
> --
> users mailing list
> users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>



-- 
Yanglong Zhu
Brown Cancer Center
University of Louisville, School of Medicine
CTR Building, Room 433A
505 South Hancock St.
Louisville, KY 40202
yanglong.zhu@xxxxxxxxx
Tel: 502-852-3685
Fax: 502-852-3661
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux