[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.

Similar Messages

[solved] vmware-server aur build fails

I'm trying to install vmware-server from aur. Downloaded the .tar.gz file from vmware, placed it in the build directory, and let it go. Build fails with the following:
(in building vmware-server-modules)
/tmp/yaourt-tmp-david/aur-vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmci-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
/tmp/yaourt-tmp-david/aur-vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmci-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
/tmp/yaourt-tmp-david/aur-vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmci-only/./include/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined
make[2]: *** [/tmp/yaourt-tmp-david/aur-vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmci-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/yaourt-tmp-david/aur-vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.33-ARCH'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/yaourt-tmp-david/aur-vmware-server-modules/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmci-only'
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build vmware-server-modules package.
Does anyone know of a solution? virtualbox works great, but doesn't support TI's MSP430UIF FET, which is why I'm trying out vmware.
Last edited by beretta (2010-05-07 17:32:03)

Trying again... I haven't been able to find a solution. Is there something else I should be doing to install vmware-server and vmware-server-modules?

[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] How to add modules to build with the kernel?

Hello i´m trying to learn how to build my own custom kernel and doing it the arch way https://wiki.archlinux.org/index.php/Ke … raditional. But unfortunately dm-crypt was not included in the kernel so it all failed.
svart_alg% sudo mkinitcpio -k 3.15.6 -c /etc/mkinitcpio.conf -g /boot/initramfs-test.img
==> Starting build: 3.15.6
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [lvm2]
==> ERROR: module not found: ‘dm-snapshot’
-> Running build hook: [encrypt]
==> ERROR: module not found: ‘dm-crypt’
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip initcpio image: /boot/initramfs-test.img
==> WARNING: errors were encountered during the build. The image may not be complete.
I have never don any of this before and have no idea of how to add a missing module to the kernel i´m building. So i search on internet and had a very hard time finding a good guide for this but i fond one possible solution. https://www.kernel.org/doc/Documentatio … odules.txt
svart_alg% make -C /home/nigro_alko/Kernel/linux-3.15.6 M=/home/nigro_alko/Kernel/cryptsetup-1.6.5/Makefile.in
make: Entering directory ‘/home/nigro_alko/Kernel/linux-3.15.6‘
mkdir: cannot create directory ‘/home/nigro_alko/Kernel/cryptsetup-1.6.5/Makefile.in’: Not a directory
scripts/Makefile.build:44: /home/nigro_alko/Kernel/cryptsetup-1.6.5/Makefile.in/Makefile: Not a directory
make[1]: *** No rule to make target ‘/home/nigro_alko/Kernel/cryptsetup-1.6.5/Makefile.in/Makefile’. Stop.
Makefile:1310: recipe for target ‘_module_/home/nigro_alko/Kernel/cryptsetup-1.6.5/Makefile.in’ failed
make: *** [_module_/home/nigro_alko/Kernel/cryptsetup-1.6.5/Makefile.in] Error 2
make: Leaving directory ‘/home/nigro_alko/Kernel/linux-3.15.6‘
So is there any one that have time to help a lost little newbie i would bee very happy :-)
Last edited by Moosey_Linux (2014-07-29 15:00:40)

karol wrote:Why do you want a custom kernel in the first place?
Moosey_Linux wrote:i´m trying to learn how to build my own custom kernel
Reason enough IMO. But anyway... you refer to the Traditional build method in the wiki, but is it possible you didn't really read it? Or maybe you only skimmed it? Did you run make menuconfig? Did you try to build everything in instead of using modules? That mkinitcpio output suggests that you did.
As suggested there for first-timers, it's a good idea to start with a kernel configuration that is known to work - the Arch config is the obvious choice, but there are other sources e.g. http://kernel-seeds.org/ .

[Solved] Harddisks: lot of output in both dmesg and kernel.log

Situation:
Since a few weeks I'm having a new little home server. An intel atom d525 cpu with 2gb ram, which seems to be a nice compromise between speed, price and power consumption. I'm wanting to use this server mainly as file server (backup, bulk data), download server, automatic backups, video streaming for the TV and my computer, mpd server and just for some experiments.
For the data I've got 2 disks, 2Tb each in a mdadm raid1 set with a layer of lvm and ext4 as the filesystem. I've used a brand new usb stick of 8Gb for the / filesystem. I know usb sticks are not made to be used as a / filesystem, but it should work and when the stick wears out (years?) I can replace it easily and cheap.
First signs of problems:
After the arch install I went ahead and installed some services. Everything seemed to be fine and I was really happy with the new server. Until after 2-3 days uptime it 'crashed'. I didn't bother looking in the logs or whatever, so I just gave it a fine reset and it went up without troubles. Again 2-3 days later it crashed again. I plugged in the monitor again and it seemed to be the / file system giving some troubles. After some io errors on the / it remounted itself read only, which gives me an unusable server. After some ext4 checks, it happened again the reboot after.
After that I decided it must be either the usb stick or the usb controller be doing something fishy. I've put the / on an old 2gb usb stick and since then it seems to be running fine (uptime now a weak).
Untill the / is full:
Strange, the 2gb / is full whilst a week ago when moving the arch install from the old usb stick, it only used about 1300Mb. After some smart usage of du and find I found out that the logs were to blame. Both the kernel.log en everything.log were 300+mb.
I hope there is somebody here who can help me figure out why the logs are getting filled with these messages and how to fix it. And to tell me if there is a serious problem with the raid1 set (mounted on /home), since I need to be able to rely on it to some extends.
raid set:
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
/dev/sdc1 is the usb stick mounted on /
dmesg:
nmbd(11212): dirtied inode 801 (wins.dat.11212) on sdc1
nmbd(11212): dirtied inode 801 (wins.dat.11212) on sdc1
jbd2/sdc1-8(725): WRITE block 1584712 on sdc1
nmbd(11212): dirtied inode 72329 (?) on sdc1
flush-8:32(1309): WRITE block 3072016 on sdc1
jbd2/sdc1-8(725): WRITE block 1584720 on sdc1
jbd2/sdc1-8(725): WRITE block 1584728 on sdc1
jbd2/sdc1-8(725): WRITE block 1584736 on sdc1
jbd2/sdc1-8(725): WRITE block 1584744 on sdc1
jbd2/sdc1-8(725): WRITE block 1584752 on sdc1
jbd2/sdc1-8(725): WRITE block 1584760 on sdc1
jbd2/sdc1-8(725): WRITE block 1584768 on sdc1
jbd2/sdc1-8(725): WRITE block 1584776 on sdc1
jbd2/sdc1-8(725): WRITE block 1584784 on sdc1
jbd2/sdc1-8(725): WRITE block 1584792 on sdc1
jbd2/sdc1-8(725): WRITE block 1584800 on sdc1
syslog-ng(1224): dirtied inode 5027 (syslog-ng.persist) on sdc1
syslog-ng(1224): dirtied inode 5027 (syslog-ng.persist) on sdc1
jbd2/sdc1-8(725): WRITE block 1584808 on sdc1
flush-8:32(1309): WRITE block 3668432 on sdc1
flush-8:32(1309): WRITE block 3668440 on sdc1
flush-8:32(1309): WRITE block 3668448 on sdc1
flush-8:32(1309): WRITE block 3668456 on sdc1
flush-8:32(1309): WRITE block 3668464 on sdc1
flush-8:32(1309): WRITE block 3668472 on sdc1
flush-8:32(1309): WRITE block 3668480 on sdc1
flush-8:32(1309): WRITE block 3668488 on sdc1
flush-8:32(1309): WRITE block 3668496 on sdc1
syslog-ng(1224): dirtied inode 72847 (kernel.log) on sdc1
syslog-ng(1224): dirtied inode 72847 (kernel.log) on sdc1
flush-8:32(1309): WRITE block 3684888 on sdc1
flush-8:32(1309): WRITE block 3684896 on sdc1
flush-8:32(1309): WRITE block 3684904 on sdc1
flush-8:32(1309): WRITE block 3684912 on sdc1
flush-8:32(1309): WRITE block 3684920 on sdc1
flush-8:32(1309): WRITE block 3684928 on sdc1
flush-8:32(1309): WRITE block 3684936 on sdc1
flush-8:32(1309): WRITE block 3684944 on sdc1
flush-8:32(1309): WRITE block 3684952 on sdc1
flush-8:32(1309): WRITE block 1309280 on sdc1
flush-8:32(1309): WRITE block 1136 on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
dmesg(11213): READ block 265816 on sdc1
kernel.log
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407424 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407432 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407440 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407448 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407456 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407464 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407472 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407480 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407488 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407496 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407504 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407512 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407520 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407528 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407536 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407544 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407552 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407560 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407568 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407576 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407584 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407592 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407600 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407608 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407616 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407624 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407632 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407640 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407648 on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: md127_raid1(1074): WRITE block 8 on sdb1
Jan 24 19:34:58 nas kernel: md127_raid1(1074): WRITE block 8 on sda1
Jan 24 19:34:59 nas kernel: bash(11231): READ block 916240 on sdc1
Jan 24 19:34:59 nas kernel: tail(11231): READ block 916272 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 3692640 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 3709104 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588128 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588136 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588144 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588152 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588160 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588168 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588176 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588184 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588192 on sdc1
Especially the lines with 'dirtied inode' do worry me .
Ps: I do know that running archlinux on a server is not 'smart'. Same for using a usb flash device for /. Both are not considered smart choices, but for a home server which doesn't need to have a 100% uptime not always a bad choice and are not the topic of discussion .
Last edited by evert_ (2011-01-24 21:21:55)

There are both log entries about the flash disk and the raid 1 set. The flash disk (sdc) entries don't seem to be critical, but I have no clue why they appeared...
I make a regular backup of my / to protect myself against loss of data due to wear some day. I've ran a little server in the past on a 4gb usb flash medium for several years, without any problems what so ever.
Last edited by evert_ (2011-01-24 18:52:54)

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.

Start Guest OS Automatically through VMware Server 2 Web Console

Hi All,
Does anyone know how to get the guest OS to automatically start/stop when VMware starts/stops? The user's manual says to click on Edit Virtual Machine Startup/Shutdown Settings, but that link is not there for me under the Commands tab. I also upgraded this from Hardware v4 to v7. I'm not sure if that makes a difference. Any thoughts or ideas would be greatly appreciated, because when my VMware server restarts, I cannot get it to automatically start the virtual machines.
Reference from the User's Manual:
Enabling System-Wide Startup and Shutdown Settings
You can enable virtual machines to be started and shut down automatically and configure how and when virtual machines are started and shut down.
To enable system-wide startup and shutdown settings
1 Select the host in the Inventory panel.
2 In the Commands section of the host Summary tab, click Edit Virtual Machine Startup/Shutdown Settings.
This is within the VMware Server 2 user's guide under Managing Your VMware Server -> Configuring Virtual Machine Startup and Shutdown Settings

Hi Paul,
I see now what you mean. You have to select the host for the entire system, not the guest OS. That's what confused me.
Didn't previous versions have a link on there to define how the startup of the specific guest OS functioned?
Chris

Bump VMware Server 1.0.7 Latest error --Not enough memory...

VMware Server Help Post
Platform:
Intel core 2 Duo E2168.
2G ram, but 1/2 just went missing. If this is causing my problems, the mind wobbles, yet it's easy to fix, yay!
Lots of harddrives! Lots of harddrive space.
gigabit eth.
Nvidia 7600GS 512MB
Highpoint raid card (soft) 132Gigs for VMs
Archlinux w/ 2.6.26.3-1 kernel
kernel-headers 2.6.25.8-1
History:
Four weeks ago--
Patched and installed VMware Server 1.0.5 on Archlinux with kernel 2.6.25... everything worked well. Bliss!
About 2 weeks ago--
Upgraded kernel to 2.6.26... time suck began.
Current status:
After banging on VMware and vmmon patch and source code for a while,
now have on kernel 2.6.26-arch--
VMware Server 1.0.7 with patch ...117d, modified as follows:
In .../vmmon-only/include/iocontrols.h
line 48 #define VMMON_VERSION (168 << 16 | 0) changed to:
line 48 #define VMMON_VERSION (138 << 16 | 0)
Patch reasoning [limited newb alert]:
Without 117d, vmmon fails to compile with error re: .nopage
With 117d, vmmon compiles and installs successfully but VMs
won't start with error re: expect version 138 got 168
With patch modified, now past the version error, but getting the error:
Not enough physical memory is available to power on this virtual machine.
To fix this problem, power off other virtual machines [No others on]
or adjust the additional memory settings to allow more virtual machine
memory to be swapped    [There's plenty of memory]
If you were able to power on this virtual machine on this host computer
in the past, try rebooting the host computer. Rebooting may allow you
to use slightly more host memory to run virtual machines. [Rebooting had no effect]
In log:
Failed to connect to vm: /mnt/VMs/Test Booger/Test Booger.vmx
vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
Error during launch: 11, The process exited with an error:
End of error message
Operation failed to change the VM to the expected power state.
Not enough physical memory is available to power on this virtual machine.
To fix this problem, power off other virtual machines [No others on]
or adjust the additional memory settings to allow more virtual machine
memory to be swapped    [There's plenty of memory]
If you were able to power on this virtual machine on this host computer
in the past, try rebooting the host computer. Rebooting may allow you
to use slightly more host memory to run virtual machines. [Rebooting had no effect]
There's plenty of memory and disk free space--
top -b >> top_out
top - 06:59:46 up 40 min, 0 users, load average: 0.02, 0.05, 0.03
Tasks: 113 total, 1 running, 112 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.1%us, 0.5%sy, 0.0%ni, 97.2%id, 1.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1034920k total, 441944k used, 592976k free, 17604k buffers
Swap: 2000084k total, 0k used, 2000084k free, 227224k cached
df -ha
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 72G 44G 25G 65% /
/dev/sdc1 20G 12G 7.5G 61% /mnt/home2
/dev/mapper/hpt45x_dcafabbcai1
153G 21G 132G 14% /mnt/VMs
I reduced host memory settings to 408MB and guest to 256MB as a test. [No effect]
After the tests I've done, I don't believe this error really has anything to do with low memory.
I don't know whether this is a bug, a patch problem, or, or, or, or .....
And so I post.
What next?
thanx in advance.
Last edited by maxbally (2008-09-15 23:33:21)

Hi Mike,
Mike23 wrote:
Hi, I develop the device which reads the data on TCP(I use ftp://ftp.ni.com/pub/devzone/epd/stm_2.0_installer.zip)
from crio and then displays them on 7 waveform chart ( 5 chart with 150000 history length and 2 with 600 - 1 minute of measurements) and 2 xy graph. After 10 minutes of work there is an error “not enough memory to complete this operation”. On the WIndows Task manger I have seen that there is a filling RAM approximately from 45 % up to 72 % then the mistake jumps out. But I do not know why. Help please.  Labview 8.6Windows Vista3 GB RAMP.S. Forgive for bad English.
It's likely that instead of trying to plot 5 charts with 150000 data-points, you're trying to plot 150000charts with 5 data-points! Try right-clicking on the chart - do you see "Transpose Array" property? If it's checked, UNcheck it (if UNchecked, check it!)
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

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

Tarball for vmware-server-modules' PKGBUILD missing [SOLVED]

Edit: I realized that my subject line was mis-leading
Hello,
I've been an arch user for several months now. Amazingly, I've been able to work my way through all the problems I've had thus far (due, in large part, to the arch community and wikis). This is my first time actually posting for help.
I've been trying to install VMware-Server on my latest install of arch, when I run a 'makepkg' on the vmware-server-modules package I get:
==> ERROR: VMware-server-2.0.2-203138.x86_64.tar.gz was not found in the build directory
and is not a URL.
A link to the missing tarball can be found on the vmware-server-2.0.2 AUR page (http://aur.archlinux.org/packages.php?ID=6182), however, when I click on the link, it 404's. I've done multiple Google, vmware.com, and archlinux.org/forum searches and have found nothing. I'm at a complete loss for what to do at this point. I really can't find anything of use on the subject, am I the only person who's had/having this problem? Any help/suggestions are greatly appreciated.
Last edited by purilepolterguist (2010-07-18 19:21:51)

Turns out I'm just retarded. That's the actual vmware-server package from the VMware download site, which I actually downloaded and unpacked in search of the file itself For those who looked at this post, could no one have just gone, "Hey dumbass, it's the actual file from the VMware site."?

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.

[SOLVED] VMware Workstation 7.1.4 fails to start/build on kernel 3.0

Since new kernel 3.0 update I cannot rebuild vmware modules
~ >>> sudo vmware-modconfig --console --install-all
Unable to initialize kernel module configuration
or start the Workstation
~ >>> vmware
Logging to /tmp/vmware-igor/setup-7740.log
Unable to initialize module building library
Does anybody know what's wrong?
Last edited by karabaja4 (2011-08-12 17:55:38)

Hi, I've been reading these forums since switched from slackware and gentoo to arch about 4 years ago. This is the first time I've been unable to fix a problem from searching here or the wiki
I'm having trouble installing vmware workstation.
So I recompiled the kernel and nvidia linking it to the .0-ARCH.
└⇥ uname -a
Linux myhost 3.0.0-ARCH #1 SMP PREEMPT Wed Aug 10 07:29:07 UTC 2011 x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-56 AuthenticAMD GNU/Linux
For the rest I followed the wiki to install vmware. Everything goes swimmingly until
└⇥ sudo vmware-modconfig --console --install-all
Password:
Stopping VMware services:
VMware USB Arbitrator 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.0.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
/tmp/vmware-root/modules/vmmon-only/linux/driver.c:40:28: fatal error: linux/smp_lock.h: No such file or directory
compilation terminated.
make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-3.0.0-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Unable to install vmmon
Does anyone have a suggestion of where to poke around?

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

Error when starting a converted VM (from vmware server edition)

Hi, i am trying to start a converted VM from VMWARE SERVER. I think i have followed steps to import an VMWARE machine (using resources >> virtual machines images) and it does not return errors when converting VM but then, when trying to start it, it returns
failed:<OVSException: no server selected to run vm('/OVS/running_pool/SIR_xxx') memory=512> StackTrace: File "/opt/ovs-agent-2.2/OVSSiteVM.py", line 77, in start_vm raise e
I have also checked that there is enough memory.
This is the contect for vm.cfg
acpi = 1
apic = 1
builder = 'hvm'
device_model = '/usr/lib/xen/bin/qemu-dm'
disk = ['file:/OVS/running_pool/SIR_xxx/SIR_xxx.img,hda,w',
'file:/OVS/running_pool/SIR_consulnor/SIR_xxx (2).img,hdb,w',
',hdc:cdrom,r',
kernel = '/usr/lib/xen/boot/hvmloader'
memory = '512'
name = 'SIR_xxx'
on_crash = 'restart'
on_reboot = 'restart'
pae = 1
serial = 'pty'
timer_mode = '1'
uuid = 'e23767cc-dc3d-0255-a7ac-65f111b589d7'
vcpus = 1
vif = ['bridge=xenbr0,mac=00:16:3E:71:AF:B1,type=ioemu']
vif_other_config = []
vnc = 1
vncconsole = 1
vnclisten = '0.0.0.0'
vncpasswd = 'xxx'
vncunused = 1
Thanks for your help

user559432 wrote:
failed:<OVSException: no server selected to run vm('/OVS/running_pool/SIR_xxx') memory=512> StackTrace: File "/opt/ovs-agent-2.2/OVSSiteVM.py", line 77, in start_vm raise eDo your servers have Hardware/Full Virtualization enabled? You can check on the console and ensure the console says that Hardware Virtualization is enabled. If not, check in your BIOS that the processor hardware virtualization is enabled. If you don't have an option, your PC may not have the Intel VT-x or AMD-v extensions required to support hardware virtualization.
You can check to see if your processor supports this extension by using:
Intel processor:
# cat /proc/cpuinfo | grep vmxAMD processor:
# cat /proc/cpuinfo | grep svmIf you see a result, it means the processor has that support. You still need to ensure that it is enabled in the BIOS.

[solved] vmware server 1.0.4 build 56528 and kernel 2.6.25

Similar Messages

Maybe you are looking for