nelze spustit vmware server

Dobrý den, obracím se na Vás s prosbou o radu. Nainstaloval jsem si poslední verzi vmware serveru + mui na FC6 s aktualizovaným jádrem 2.6.20-1.2933.fc6,ale nelze ji spustit. Provedl jsem instalaci serveru pomocí
./vmware-install.pl
pak jsem pred konfigurací patchoval pomocí vmware-any-any-update108
./runme.pl
provedl jsem konfiguraci a po te nainstaloval s drobnou upravou skriptu i mui
./vmware-install.pl
při spuštení vmware v konzoli se mi objeví tato hláška:
vmware is installed, but it has not been (correctly) configured
for this system. To (re-)configure it, invoke the following command:
/usr/bin/vmware-config.pl
Tak jsem se tedy pokusil rekonfigurovat vmware tímto způsobem:
[root@localhost ~]# /usr/bin/vmware-config.pl
Making sure services for VMware Server are stopped.

Stopping VMware services:
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet1 [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
Host-only networking on /dev/vmnet8 [ OK ]
Virtual ethernet [ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the mime type icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application’s icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler “/usr/bin/gcc”. Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.20-1.2933.fc6/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory /tmp/vmware-config2/vmmon-only' make -C /lib/modules/2.6.20-1.2933.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory/usr/src/kernels/2.6.20-1.2933.fc6-i686’
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config2/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config2/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config2/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config2/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config2/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config2/vmmon-only/common/task.o
cc1plus: warning: command line option “-Werror-implicit-function-declaration” is valid for C/ObjC but not for C++
cc1plus: warning: command line option “-Wdeclaration-after-statement” is valid for C/ObjC but not for C++
cc1plus: warning: command line option “-Wno-pointer-sign” is valid for C/ObjC but not for C++
cc1plus: warning: command line option “-Wstrict-prototypes” is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option “-ffreestanding” is valid for C/ObjC but not for C++
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX1]’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMDriver*, Vcpuid)’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
CC [M] /tmp/vmware-config2/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config2/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config2/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config2/vmmon-only/vmmon.ko
make[1]: Leaving directory /usr/src/kernels/2.6.20-1.2933.fc6-i686' cp -f vmmon.ko ./../vmmon.o make: Leaving directory/tmp/vmware-config2/vmmon-only’
The module loads perfectly in the running kernel.

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/vmnet8, and was about to remove
it. Somebody else apparently did it already.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [no]

Do you want networking for your virtual machines? (yes/no/help) [yes]

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.

This program previously created the file /dev/vmnet9, and was about to remove
it. Somebody else apparently did it already.

Would you prefer to modify your existing networking configuration using the
wizard or the editor? (wizard/editor/help) [wizard]

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]

Configuring a NAT network for vmnet8.

The NAT network is currently configured to use the private subnet
192.168.216.0/255.255.255.0. Do you want to keep these settings? [yes]

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 192.168.216.0.

Do you wish to configure another NAT network? (yes/no) [no]

Do you want to be able to use host-only networking in your virtual machines?
[yes]

Configuring a host-only network for vmnet1.

The host-only network is currently configured to use the private subnet
192.168.147.0/255.255.255.0. Do you want to keep these settings? [yes]

The following host-only networks have been defined:

. vmnet1 is a host-only network on private subnet 192.168.147.0.

Do you wish to configure another host-only network? (yes/no) [no]

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory /tmp/vmware-config2/vmnet-only' make -C /lib/modules/2.6.20-1.2933.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory/usr/src/kernels/2.6.20-1.2933.fc6-i686’
CC [M] /tmp/vmware-config2/vmnet-only/driver.o
CC [M] /tmp/vmware-config2/vmnet-only/hub.o
CC [M] /tmp/vmware-config2/vmnet-only/userif.o
CC [M] /tmp/vmware-config2/vmnet-only/netif.o
CC [M] /tmp/vmware-config2/vmnet-only/bridge.o
CC [M] /tmp/vmware-config2/vmnet-only/procfs.o
CC [M] /tmp/vmware-config2/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config2/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config2/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config2/vmnet-only/vmnet.ko
make[1]: Leaving directory /usr/src/kernels/2.6.20-1.2933.fc6-i686' cp -f vmnet.ko ./../vmnet.o make: Leaving directory/tmp/vmware-config2/vmnet-only’
The module loads perfectly in the running kernel.

Shutting down http.vmware: /etc/rc.d/init.d/httpd.vmware: line 213: 4129 Ukončen (SIGTERM) ( trap ‘’ SIGHUP; “$func” “$@” ) >/dev/null 2>&1
[SELHALO]
Starting httpd.vmware: [ OK ]
Please specify a port for remote console connections to use [904]

WARNING: VMware Server has been configured to run on a port different from the
default port. Remember to use this port when connecting to this server.
Unable to find any instance of the super-server “inetd” or “xinetd”. It is
possible that you do not have one of these packages installed on this machine.
Please install “inetd” or “xinetd”.

If you do have “inetd” or “xinetd” installed, make sure that /etc/inetd.conf or
/etc/xinetd.d exists.
The configuration will continue, but you should re-run
/usr/bin/vmware-config.pl after you fix the super-server.

Hit enter to continue.

pak jsem se pokoušel opětovně spustit vmware ale neúspěšně, vyžaduje konfiguraci znovu. Démon běží bez problémů,ale moduly vmmon a vmnet se ani po kompilaci nezavedou. Xinetd je nainstalováno,složka /etc/xinetd.d existuje.
Zkoušel jsem aktualizaci jádra,ale yum žádné balíčky nenabídl. Odinstaloval jsem staré jádro i s ostatními balíčky ale ani to nepomohlo.

děkuji za každou pomoc

A spousti se vam ten xinetd?

chkconfig --list | grep xinetd

Jakou verzi a jak sis nainsaloval?
Já používám tuhle VMware-server-1.0.2-39867.i386.rpm a funguje s tím anyany updatem naprosto bez problémů.
Po instalaci a každém updatu jádra stačí spustit vmware-config.pl a jede se dál.

Po zadani prikazu chkconfig --list | grep xinetd se nic nedeje, naskoci cisty prikazovy radek, predpokladam tedy ze se nespousti :frowning: nainstalovanou mam verzi VMware-server-1.0.2-39867.i386, ale jak server tak mui sem instaloval pomoci archivu, tj. rozbalil a v konzoli spustil vmware-install.pl. Any-any-update ma cislo 108.

A mas nejakej specialni duvod to neinstalovat z rpmka?

ne nemam,ale nasel jsem odkazy na archivy tak jsem to instaloval z toho :slight_smile: ale to uz je jedno,protoze problem je vyresen, stacilo doinstalovat xinetd a spustit ho, pak jsem opetovne spustil konfiguraci a vse jiz probehlo OK. diky vsem za radu a jeste bych se chtel zeptat na jednu zacatecnickou vec. vytvoril jsem si 8GB slozku win XP. Ale jak zviditelnit ostatni disky virtualnimu systemu, popr. jak prenest soubor?

vmware-mount.pl

viz.
http://www.vmware.com/support/reference/linux/loopback_linux.html

tak jsem vyzkousel uvedeny modul spolecne s internetovou strankou, ale nejspise delam neco spatne :frowning: bohuzel jsem jiz nenasel archiv uvadenz na te wobove strance tak jsem pouzil vmware-mount.pl z /usr/bin a provedl nasledujici veci:

[tom@localhost ~]$ su
Heslo:
[root@localhost tom]# cd /usr/bin
[root@localhost bin]# vmware-mount.pl -p /home/WinXPP/WinXPP.vmdk


VMware for Linux - Virtual Hard Disk Mounter
Version: 1.0 build-39867
Copyright 1998 VMware, Inc. All rights reserved. – VMware Confidential

Nr Start Size Type Id Sytem


1 63 10458252 BIOS B Win95 FAT32
[root@localhost bin]# vmware-mount.pl /home/WinXPP/WinXPP.vmdk 1 /mnt/VHD_XP


VMware for Linux - Virtual Hard Disk Mounter
Version: 1.0 build-39867
Copyright 1998 VMware, Inc. All rights reserved. – VMware Confidential

It has been reported that this program does not work correctly with 2.4+ Linux
kernels in some cases, and you are currently running such a kernel. Do you
really want to continue? [N] Y

No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about
to create the /dev/nb0 Network Block Device. Continue? [Y] Y

Creating the /dev/nb0 Network Block Device

No Network Block Device driver detected.

Trying to load the Network Block Device driver kernel module… Success.

Client: The partition is now mapped on the /dev/nb0 Network Block Device.

Using another terminal, you can now browse your Virtual Hard Disk partition in
/mnt/VHD_XP. Hit Control-C in this terminal when done.
Warning: The NBD_DO_IT ioctl returned an error: Broken pipe
[root@localhost bin]#

neni to presne jak v tom odkazu,ale nenapada me nic co s tim vic udelat. zkousel jsem opetovnou instalaci a vse zkusil znovu,ale bez vysledku. v cilove slozce se obsah disku nezobrazuje. diky za kazdou radu.

teďka se dívám, že mě ten warning píše taky, ale až po stisku ctrl+c
doufám, že to nestiskneš hnedka, protože to použiješ až to nepotřebuješ jako pro odmountování

diky za pomoc, ja sem to mackal hned :slight_smile: Myslel sem ze to bude namapovany porad. Uz jsem to rozchodil, ale zda se ze je to pouze pro cteni.

mě to funguje pro zápis naprosto bez problémů

to je divny, mel jsem u slozky nastaveny prava pro vsechno ale po pripojeni se zmenila pouze na r-x tak jsem se prihlasil jako root do konzoly a pomoci MC jsem tam chtel nakopirovat soubor a zamrzlo mi PC tak ze pomohl jedine reset !! ani zmena prav mi nechtela fungovat :frowning:

Já tu mountovací složku mám normálně r-x
Pod rootem to namountuju a v tom okamžiku je už i pod normálním uživatelem celá tato složka jako rwx

A kde máte složku umístěnou? Ja jsem si vytvořil extra složku v /mnt. Mozna je to prikazem, jaký příkaz zadáváte? Máte tam definovaná přístupová práva nebo tak něco? Ja to spouštím takhle:

/usr/bin/vmware-mount.pl /home/WinXPP/WinXPP.vmdk 1 -t vfat /mnt/VHD_XP

a snad uz posledni dotaz, pracujete s virtualnim diskem i pri pustenem virtualnim OS nebo jen pri vypnutem?

složku mám taky v /mnt
na tom virtuálním disku mám myslím ntfs, ale každopádně při mountování nezadávám filesystém
zadávám to jenom takhle
vmware-mount.pl soubor_s_imagem_disku 1 /mnt/win
pokud běží virtuální systém nad tímto diskem tak mě nejde přimountovat, takže to používám jenom offline

vyzkousim jeste preformatovat virualni disk na NTFS, ale nedavam moc nadeji tomu,ze to pak pujde. Kazdopadne dekuji pomoc :slight_smile:

myslel jsem spíš abys to zkusil bez toho -t vfat než přeformátovat…

bez -t vfat je to stejne, tak jsem to zkusil preformatovat, zmena nastala ale k horsimu, ted uz je slozka s virtualnim diskem pristupna pouze rootovi, je uzamcena podobne jako /root, vypada to na prenos souboru pomoci flash disku :frowning:

nic dalšího mě teda nenapadá
Já to mám sice instalovaný z rpm, ale verze je to stejná tak by to mělo fungovat, ikdyž čert ví co to ještě může dělat navíc při instalaci…
Ještě jedna věc co by možná mohla mít vliv je, že mám vypnutej selinux.

mam ho taky vypnutej. tez uz me nic nenapada.