Vmware Server 1.0.3 and kernel 2.6.22

Maybe this will be of help to anyone...
The modules for vmware server 1.0.3 don't compile under 2.6.22-ARCH kernel from testing, and as far as I know there is no patch to fix that automatically yet. I was able to to compile them successfully using the information from post 11 in this thread: http://www.vmware.com/community/thread. … adID=92709 - the specific file that I had to edit was "/usr/src/linux-2.6.22-ARCH/include/asm-i386/page.h".

To compile vmware workstation 6 for the new kernel check out this link.
http://npw.net/2007/05/17/vmware-workst … inux-2622/

Similar Messages

Vmware-server 1.0.1 and kernel *.19 [solved]

Hi,
since I upgraded the kernel from 2.6.18 to .19 I cant get my vmware-server running. Has anybody else this problem?
I ran vmware-config.pl again but it always crashes with:
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
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
/tmp/vmware-config2/vmnet-only/userif.c: In Funktion »VNetCopyDatagramToUser«:
/tmp/vmware-config2/vmnet-only/userif.c:629: Fehler: »CHECKSUM_HW« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-config2/vmnet-only/userif.c:629: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt
/tmp/vmware-config2/vmnet-only/userif.c:629: Fehler: für jede Funktion in der er auftritt.)
make[2]: *** [/tmp/vmware-config2/vmnet-only/userif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-config2/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-config2/vmnet-only'
Unable to build the vmnet module.
I try to create this error in english later, but maybe u know the problem already. I found sth about a any-any-patch but I couldnt find out if this is related to arch.
Would be great if somebody could give me a hint.
Btw, Merry Christmas [/i]

Merry Christmas to you too.
Yes. The problem is related to the any-any-patch.
Get the latest version of the patch and run it. That should solve the problem.
If for whatever reason it fails then, and only then, look for this file:
/lib/modules/2.6.18-ARCH/build/include/linux/version.h, and make sure it contains a line for the UTS_RELEASE, and if it does not, add at the end the following: define UTS_RELEASE "2.6.19-ARCH"
Then run the patch again.
Hope it helps.
R

Problem with vmware server 1.0.10 and usb mounting into guest

Hi, I really ve a serious problem here because I ve some reason that I need to use vmware sv 1.0.10 with windows 7 64bit pro as the host and win xp pro sp3 as guest os .... now i can installed vmware on my win 7 with pressing F8 then disble driver signature technique and I also sign vmware driver with win7 using some tool...
However, my problem is that i cant mount USB flash drive into the guest... it just show me my flash drive's name at the toolbar>>removable device>>usb but when i click on it.. nothing happen .. and after that when i check vmware log I've found that my vmware saw my flashdrive normally as it should be... i really ve no idea how to solve this....
I also tried set .vmx config with many methods but nth can help me...
Ps. I know that vmware server may b ve a big issue with win7 compatible things but i do really need to make this version of VM working with my usb flashdrive... plz help me.. Thank you guys all:)))

Hi creamac,
Welcome to communites
Please install vmware tool and then on vmware task bar select connect or unplug usb drive . You
will find that on right hand corner above to task bar of host machine .
"Nature always wears the colors of the spirit."

VMware Server 2.0.2 and Solaris 10 10/08 x86 doesn't install

Hi,
I'm having trouble installing Solaris 10 using Server 2.0.2. I need Solaris 10 for dev/testing purposes. I don't have a spare 64-bit machine to run the latest vSphere Hypervisor 5.1 so I thought I would try Server 2.0.2 since it co-exists with Windows and supports Solaris 10.
I have a Intel Core i5, 8GB, running Win 7 Home Premium 64-bit. I'm able to create a Virtual Machine in Web Access. Event log says the VM is powered on and I see some DVD disk access but Solaris never gets installed. I've tried using ISO image and DVD-ROM disc. Same results. Also tried creating 32-bit and 64-bit Solaris 10 installation. Nothing. I was under the assumption, OS installation would start once the VM was powered on.
Since Web Access doesn't show any major failures alerts, I'm assuming there isn't a hardware issue???
I've included the VMware log file for reference. Hopefully I'm not missing something obvious.
Thanks kindly for your help,

I figured it out. Gotta used a "supported" browser. Either Firefox 2 or 3. Or IE 6 or 7.
Things get outdated real fast. I'm on Firefox 19. The Web Access UI wasn't showing anything in Firefox 19 under the VMs. Screen wasn't garbled or messed up which threw me off, just blank.

[Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH

Hi,
i followed the instructions here https://wiki.archlinux.org/index.php/VM … n.2FPlayer
while running the modconfig command i get this error.
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
In file included from /tmp/vmware-root/modules/vmnet-only/bridge.c:51:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/bridge.o] Fehler 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfSetup«:
/tmp/vmware-root/modules/vmnet-only/netif.c:149:7: Fehler: »struct net_device« hat kein Element namens »init«
/tmp/vmware-root/modules/vmnet-only/netif.c:150:7: Fehler: »struct net_device« hat kein Element namens »open«
/tmp/vmware-root/modules/vmnet-only/netif.c:151:7: Fehler: »struct net_device« hat kein Element namens »hard_start_xmit«
/tmp/vmware-root/modules/vmnet-only/netif.c:152:7: Fehler: »struct net_device« hat kein Element namens »stop«
/tmp/vmware-root/modules/vmnet-only/netif.c:153:7: Fehler: »struct net_device« hat kein Element namens »get_stats«
/tmp/vmware-root/modules/vmnet-only/netif.c:154:7: Fehler: »struct net_device« hat kein Element namens »set_mac_address«
/tmp/vmware-root/modules/vmnet-only/netif.c:155:7: Fehler: »struct net_device« hat kein Element namens »set_multicast_list«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfNetDeviceToNetIf«:
/tmp/vmware-root/modules/vmnet-only/netif.c:196:14: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIf_Create«:
/tmp/vmware-root/modules/vmnet-only/netif.c:311:4: Fehler: Implizite Deklaration der Funktion »compat_alloc_netdev« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/netif.c:311:8: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/netif.c:316:7: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfReceive«:
/tmp/vmware-root/modules/vmnet-only/netif.c:397:4: Warnung: Übergabe des Arguments 1 von »netif_running« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifOpen«:
/tmp/vmware-root/modules/vmnet-only/netif.c:477:4: Warnung: Übergabe des Arguments 1 von »netif_start_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifClose«:
/tmp/vmware-root/modules/vmnet-only/netif.c:525:4: Warnung: Übergabe des Arguments 1 von »netif_stop_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:236:1: Warnung: Kontrollfluss erreicht Ende von Nicht-void-Funktion [-Wreturn-type]
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Unable to install vmnet
Maybe someone has an idea whats going wrong ?
stubb
Last edited by stubb (2011-12-01 23:45:44)

rm /usr/lib/vmware/modules/source/.patched
fixed it

New dedicated Server, incompatiblew with VMware Server 1.0

Hi
my old root running vmware server 1.0 is more than outdated and needs to be replaced, as the downtimes cause of hardware issues get bigger and bigger
Now I need to find a solution to run the virtual windows machines on debian 7.5 (wheezy)
vmware server 2 seems to be not the solution, as its also only working with patches and an outdated kernel in debian squeeze
i need to start some windows server virtual machines, i can do this manually, but i need several running parallel
any ideas?

Hi,
You can successfully run the old VMware Server 1.0.10 on a Debian Wheezy. I'm actually doing it.
Please find all relevant patches at VMware Server 1.0.10 and linux kenel 3.1.0.

Running VMware Server 2 services as a non-root user

Hello,
I have switched from VirtualBox to VMware Server 2 on my Arch64 server and the transition has been relatively painless. I am at the point now where I want to run VMware's services as a non-root user account (I have a service account called "svc-vmadmin" that I'd like to use). I'm generally not comfortable running services as root, but at the same time I'm conscious of the time and effort required vs. overall benefits.
I've done the usual Google searches and even checked the VMware Server 2 user guide and the VMware community, but I can't find specific details on how to achieve this.
Is this even plausible in a Linux environment? I used to run VMware Server 1 under the SYSTEM account on Windows Server, so I'm hopinga similar thing can be done on Arch.
I would greatly appreciate any information or personal experience that fellow Archers can share.
Thanks,
Thom

System services are handled by launchd.
If you look in /System/Library/LaunchDaemons/ you'll see a plist file for each service including org.isc.named.plist, the plist for named.
If you edit this file you'll see it's an XML document that describes the service and how the OS should handle it, including the part:
<key>ProgramArguments</key>
<array>
<string>/usr/sbin/named</string>
<string>-f</string>
</array>
Just append another entry in the array that says <string>-u nobody</string> (or whatever username you want to run as.

VMware-server freeze

I installed vmware-server fromt the AUR, and the installation seemed to go perfectly smoothly. The program opens, but when I select local host on the connection options, the program freezes, and has to be killed. Any ideas as to what might cause this?

On Thu, 14 Dec 2006 22:43:43 GMT, Iain wrote:
> Right now I'm thinking
> that a floppy or CD image would be the easiest method.
cd will work, pxe boot also if you set the vm to bridged..
If you have already compiled drivers or have linux.2 please put them on
http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
Live BootCd and USB Disk from Mike Charles
http://forge.novell.com/modules/xfmod/project/?imagingx
eZie http://forge.novell.com/modules/xfmod/project/?ezie
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Vmware-server-modules and kernel 2.6.19 [solved]

I'm trying to rebuild the vmware server modules from AUR for the new kernel. After adjusting the files for the kernel version and doing makepkg I get the following:
==> Validating source files with MD5sums
VMware-server-1.0.1-29996.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf VMware-server-1.0.1-29996.tar.gz
==> Starting build()...
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/hostif.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/cpuid.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/hash.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/memtrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/phystrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/task.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/vmx86.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmcore/moduleloop.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.mod.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/hub.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c: In function 'VNetCopyDatagramToUser':
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: 'CHECKSUM_HW' undeclared (first use in this function)
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: (Each undeclared identifier is reported only once
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: for each function it appears in.)
make[2]: *** [/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
==> ERROR: Build Failed. Aborting...
It seems the userif module breaks. I haven't a clue how to solve this. :?

Progress:
AUR
which leads to
http://www.vmware.com/community/thread. … 4&tstart=0
EDIT: package in AUR has been updated. Thnx pizzapunk.

[SOLVED] vmware server and kernel 2.6.26

I'm having trouble building the vmware-server-modules and I see that there is a patch for the 2.6.24 and 2.6.25 versions of the kernel. I've got 2.6.26, is there a module patch for this kernel version?
FYI, the error I'm getting while building the vmware-server-modules is:
CC [M] /var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:146: error: unknown field 'nopage' specified in initializer
/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type
/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:150: error: unknown field 'nopage' specified in initializer
/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type
make[2]: *** [/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.26-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/var/abs/local/vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
==> ERROR: Build Failed.
Aborting...
Last edited by murffatksig (2008-08-14 03:39:05)

foutrelis wrote:
I've modified PizzaPunk's PKGBUILD to include the patches from http://groups.google.com/group/vmkernelnewbies/files (VMware-server-vmmon-1.0.6-91891-2.6.26-1.patch & VMware-server-vmnet-1.0.6-91891-2.6.26-1.patch).
If anyone's interested: vmware-server-modules
FANTASTIC! Thanks!

[solved] vmware server 1.0.4 build 56528 and kernel 2.6.25

hi,
i updated to kernel 2.6.25 and tried to reinstall vmware server 1.0.4 build 56528 according to the wiki description.
running the vmware-any-any-update-117-very-ALPHA.tgz patch failed, because vmware-2.6.25.sh tries to patch vmblock.tar, which does not exist. instead of this there is vmppuser.tar in the sources directory.
any ideas?
thx & rgds
hcjl
with vmware server 1.0.5 the same problem occurs.
Last edited by hcjl (2008-05-27 08:56:35)

Yeah I have this exact same problem with the current stable version of VMware. I will definitely try the beta 2.0 and see if my laptop can run Autodesk Inventor with it in a virtual Windows environment.

Vmware server 2: error in vmware-config after update to kernel 2.6.31

Hi,
After upgrading my system today, vmware-config.pl issues the following error:
/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/linux-2.6.31-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.
My previous vmware server 2 installation was patched for kernel 2.6.30 according to the information here:
http://communities.vmware.com/message/1286903
Before attempting to run vmware-config.pl I reinstalled with vmware-install.pl.
Thanks.

For reference I post here the solution to the mouse flickering, in case anyone has the same problem:
http://radu.cotescu.com/2009/10/30/how- … mic-koala/
Just follow step 6 to solve the problem.
JAcky wrote:
dabd wrote:hi
following the instructions here http://blog.mymediasystem.net/uncategor … la-x86_64/
Thank you very much, that works just fine.
I have not noticed any strange VM behavior on my Windows XP installation. But I only use it to test websites with IE and it does not run in full screen mode.
Now I only need to find out why Opera is running at 101% CPU load since the update and I will be all set
Thanks again.

VMware server: Error trying to compile the vmmon and vmnet modules.

Hello,
I am trying to install VMware server following the wiki: http://wiki.archlinux.org/index.php/Ins … _on_Arch64
I can't get very far as I can't even compile vmmon and vmnet and I have no idea on how to solve this problem
[21:02:38][root@phusis]
[/opt/arch32/root/vmware-server-distrib/lib/modules/source]Arch64# make -C vmmon-only auto-build HEADER_DIR=/usr/src/linux-`uname -r`/include CC=gcc SUPPO_SMP=1 GREP=grep IS_GCC_3=no
Using 2.6.x kernel build system.
make: Entering directory `/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only'
make -C /usr/src/linux-2.6.28-ARCH/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.28-ARCH'
CC [M] /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
In file included from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/./include/x86.h:20,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/./include/machine.h:24,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.h:15,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:49:
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/./include/x86apic.h:79:1: warning: "APIC_BASE_MSR" redefined
In file included from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/numa_64.h:5,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/numa.h:4,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/acpi.h:28,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/fixmap_64.h:15,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/fixmap.h:7,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/apic.h:8,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/smp.h:13,
from include/linux/smp.h:30,
from include/linux/topology.h:33,
from include/linux/mmzone.h:763,
from include/linux/gfp.h:4,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:12:
/usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/apicdef.h:132:1: warning: this is the location of the previous definition
In file included from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/./include/machine.h:24,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.h:15,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:49:
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/./include/x86.h:830:1: warning: "PTE_PFN_MASK" redefined
In file included from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/pda.h:8,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/current.h:19,
from /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/processor.h:15,
from include/linux/prefetch.h:14,
from include/linux/list.h:6,
from include/linux/module.h:9,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:12:
/usr/src/linux-2.6.28-ARCH/arch/x86/include/asm/page.h:22:1: warning: this is the location of the previous definition
In file included from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/vmhost.h:13,
from /opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:71:
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/./include/compat_semaphore.h:5:27: error: asm/semaphore.h: No such file or directory
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:146: error: unknown field 'nopage' specified in initializer
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:150: error: unknown field 'nopage' specified in initializer
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl':
/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.c:1670: error: too many arguments to function 'smp_call_function'
make[2]: *** [/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.28-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/opt/arch32/root/vmware-server-distrib/lib/modules/source/vmmon-only'
Do you know what I could do to sort the above issue?
Thanks
Ludo

hi,
i am not able to use the patch. there are always missing files and i dont know the path for this files.
here is the output of the console:
patch -p1 -i /home/felix//Desktop/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmblock-only/include/compat_wait.h new/vmblock-only/include/compat_wait.h
|--- orig/vmblock-only/include/compat_wait.h 2008-10-28 22:47:20.000000000 -0700
|+++ new/vmblock-only/include/compat_wait.h 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 19
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmci-only/include/compat_wait.h new/vmci-only/include/compat_wait.h
|--- orig/vmci-only/include/compat_wait.h 2008-10-28 22:47:21.000000000 -0700
|+++ new/vmci-only/include/compat_wait.h 2009-01-20 04:49:44.000000000 -0700
File to patch: y
y: No such file or directory
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 34
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmmon-only/include/compat_wait.h new/vmmon-only/include/compat_wait.h
|--- orig/vmmon-only/include/compat_wait.h 2008-10-28 22:47:18.000000000 -0700
|+++ new/vmmon-only/include/compat_wait.h 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 49
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmmon-only/include/x86apic.h new/vmmon-only/include/x86apic.h
|--- orig/vmmon-only/include/x86apic.h 2008-10-28 22:47:17.000000000 -0700
|+++ new/vmmon-only/include/x86apic.h 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 64
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmmon-only/linux/driver.c new/vmmon-only/linux/driver.c
|--- orig/vmmon-only/linux/driver.c 2008-10-28 22:47:18.000000000 -0700
|+++ new/vmmon-only/linux/driver.c 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 85
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmmon-only/linux/hostif.c new/vmmon-only/linux/hostif.c
|--- orig/vmmon-only/linux/hostif.c 2008-10-28 22:47:17.000000000 -0700
|+++ new/vmmon-only/linux/hostif.c 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
4 out of 4 hunks ignored
can't find file to patch at input line 173
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmmon-only/linux/vmmonInt.h new/vmmon-only/linux/vmmonInt.h
|--- orig/vmmon-only/linux/vmmonInt.h 2008-10-28 22:47:17.000000000 -0700
|+++ new/vmmon-only/linux/vmmonInt.h 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 188
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmnet-only/bridge.c new/vmnet-only/bridge.c
|--- orig/vmnet-only/bridge.c 2008-10-28 22:47:18.000000000 -0700
|+++ new/vmnet-only/bridge.c 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 203
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmnet-only/compat_wait.h new/vmnet-only/compat_wait.h
|--- orig/vmnet-only/compat_wait.h 2008-10-28 22:47:19.000000000 -0700
|+++ new/vmnet-only/compat_wait.h 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 218
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmnet-only/driver.c new/vmnet-only/driver.c
|--- orig/vmnet-only/driver.c 2008-10-28 22:47:19.000000000 -0700
|+++ new/vmnet-only/driver.c 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 235
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vmnet-only/netif.c new/vmnet-only/netif.c
|--- orig/vmnet-only/netif.c 2008-10-28 22:47:18.000000000 -0700
|+++ new/vmnet-only/netif.c 2009-01-20 04:49:44.000000000 -0700
File to patch:
Skip this patch? [y] y
Skipping patch.
4 out of 4 hunks ignored
can't find file to patch at input line 286
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur orig/vsock-only/include/compat_wait.h new/vsock-only/include/compat_wait.h
|--- orig/vsock-only/include/compat_wait.h 2009-01-20 14:11:34.000000000 +0100
|+++ new/vsock-only/include/compat_wait.h 2009-01-20 14:51:05.000000000 +0100
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
thanks
felix

VMware-server: Any way to get this to work? Kernel issues! SOLVED

Hi all,
I am trying to get VMware server installed, but am having a lot of difficulty.
According to multiple sources of information, I am told I need to install vmware-server-modules first.
When I try to install, yaourt gives the following error: error: target not found: kernel26>=2.6.32.
When I try to install vmware-server, yaourt gives the error error: target not found: kernel26>=2.6.29.
FYI:
$ uname -r
3.2.5-1-ARCH
The Wiki deals with VMware Player and Workstation, but not Server. There is a forum/aur information relating to installing Server which is quite old (mostly 2010, some 2011), however given I am running an up-to-date kernel I seem to be hitting a dead end. Is there anyone who knows how to get this working?
I have seen:
https://bbs.archlinux.org/viewtopic.php?id=101982
https://aur.archlinux.org/packages.php?ID=6182
I have tried VirtualBox in the past but have had issues getting the networking properly configured, so VMware remains my preference. If there are other decent virtualisation options I am willing to listen.
Your assistance would be much appreciated!
Last edited by emile (2012-03-03 09:46:32)

Thank you for your posts. My own research and your comments has convinced me that VMware Server is not the right way forward nowadays.
EXSi:
I have an unused box (Dell GX620 usff) which seems like it would be suitable to run EXSi and 2-3 VMs, but no more due to RAM limits of 4GB on the mobo. I THINK its 64-bit, but not 100% sure - knowing this is an EXSi requirement for recent versions is somewhat annoying. Also, from what I understand, there is no native Linux control application (vSphere is Windows only, right?), which makes VMware feel entirely like the wrong choice for me.
Citrix XenServer:
This looks promising - does anyone use this?
VirtualBox:
I hear your comments ... maybe its time to do some reading on this. Seems like I'll only get it to work if I take the time to do it right. As usual, so no suprises there Given that it will be easier to experiment on my usual system than have to spend time on a new box, I think I'll investigate this first.
Please feel free to leave further comments on this subject - I'm still interested in your experiences. It will however, be marked as SOLVED, as VMware-server is out.

X server won't start after recent catalyst-test and kernel upgrade

Hi,
after recent upgrade of catalyst-test (13.2) and kernel (3.7.5), my x server won't start with this log (WW) and (EE) only:
[ 114.989] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 116.077] (WW) Falling back to old probe method for fglrx
[ 116.093] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[ 116.101] (EE) fglrx(0): DAL initialization failed!
[ 116.101] (EE) fglrx(0): Display Infrastructure Failed
[ 116.101] (EE) fglrx(0): PreInit failed
[ 116.212] (EE) Screen(s) found, but none have a usable configuration.
[ 116.212]
Fatal server error:
[ 116.212] no screens found
[ 116.212] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 116.212] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 116.212] (EE)
[ 116.515] Server terminated with error (1). Closing log file.
My card is mobility radeon hd 5700, I'm running on x86_64 system. I'm using aticonfig generated xorg.conf. I will provide any other information if needed.
I've tried:
- to downgrade to catalyst 12.8 and xorg 1.12 (screen just freezes after trying to get to X, only poweroff button works (system catches the signal and shuts down softly - no errors in Xorg.0.log))
- to use catalyst-total 13.1 / catalyst-generator 13.1 (Xorg.0.log says something about *not* compatible module - i can try it again and give you the whole log, it is probably another problem)
- to use open-source drivers (poor performance, overheating)
- to check nomodeset option (present at all kernel images in generated grub.cfg)
Unfortunately, I could not find any similar issue solved in past few days...

Downgrading kernel to 3.7.4 actually worked for catalyst 13.1. Anyone knows what could be wrong for linux 3.7.5?
Edit: catalyst-test 13.2 beta works with linux 3.7.4.
Last edited by sirkubador (2013-02-05 14:24:44)

Vmware Server 1.0.3 and kernel 2.6.22

Similar Messages

Maybe you are looking for