Bug#438739: vmware-any-any-patch-113
Hi!
A suggested fix...
Would it be possible to create a post-inst script in the created
vmware-{server|workstation|player} package setting the corrent value in
/etc/modprobe.d/vmware ?
As those packages do depend on vmware-kernel-modules anyway, creating
such a configfile sounds fine to me (but then again, I know little about
packaging policies and I'm no DD ;-) ).
According to apt-cache show, vmware-package supports
* VMware Workstation 6.0 (includes VMware Player).
* VMware Player 2.0.
* VMware Server 1.0.
According to modinfo vmmon the correct values would be
parm: vmversion:VMware version you use: 1=VMware 2, 2=GSX 1, 3=VMware
3, 4=VMware 3.2, 5=GSX 2, 6=GSX 2.5, 7=VMware 4, 8=VMware 3.2.1, 9=GSX 2.5.1,
10=VMware 4.5, 11=VMware 4.5.2, 12=GSX 3.2, 13=VMware 5.0, 14=VMware 5.5,
15=Server 1.0, 16=VMware 6.0, 17=TOT (int)
VMware Workstation 6, VMware Player 2:
options vmmon vmversion=16
VMware Server 1:
options vmmon vmversion=15
for the /etc/modprobe.d/vmware file to be created by post-inst.
Thank you!
Kind regards,
Benjamin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438739: vmware-any-any-patch-113
Am Thu, 30 Aug 2007 23:51:52 -0400 schrieb Robert Edmonds [EMAIL PROTECTED]: I would suggest creating a file /etc/modprobe.d/vmware with this line: options vmmon vmversion=17 and then /etc/init.d/vmware-server stop; /etc/init.d/vmware-server start. if that doesn't work, try setting vmversion=15. With vmversion=15 everything seems to work now as wanted. Many thanks for this hint, regards Daniel -- Daniel Knabl www.tirolinux.net [EMAIL PROTECTED] PGP/GPG Fingerprint - please send signed mail only A069 671B 39F2 E9B9 FB34 68BB 4BEC 1344 C8A4 3F0B signature.asc Description: PGP signature
Bug#438739: vmware-any-any-patch-113
reopen 438739 retitle 438739 vmware-package: configure any-any vmversion parameter correctly severity 438739 normal clone 438739 -1 retitle -1 vmware-package: missing debconf prompts forcemerge -1 433880 Daniel Knabl wrote: Aug 29 20:01:00: vmx| POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 161.0. Aug 29 20:01:00: vmx| You have an incorrect version of the `vmmon' kernel module. I have recognized the two lines containing [msg.vmmonPosix.badVersion] [msg.vmmonPosix.badDriver] but I do not know, what to do, to fix it. All the *.deb files were built with the vmware-any-any-update113.tgz from the website mentioned in the README.Debian within the vmware-package. Kernel-headers fit the running kernel, also the make-vmpkg had no output containing errors. When I install vmware-server and the any-any-113 patch by hand, not the Debian way, everything works fine. the problem is that the freestanding any-any modules source package currently builds modules that default to compatibility with vmware workstation 6.0 / player 2.0. ideally workstation / player / server could all use the same set of modules. you can override the version at module load time with the vmversion module paramater: [EMAIL PROTECTED]:~$ modinfo vmmon | grep parm parm: vmversion:VMware version you use: 1=VMware 2, 2=GSX 1, 3=VMware 3, 4=VMware 3.2, 5=GSX 2, 6=GSX 2.5, 7=VMware 4, 8=VMware 3.2.1, 9=GSX 2.5.1, 10=VMware 4.5, 11=VMware 4.5.2, 12=GSX 3.2, 13=VMware 5.0, 14=VMware 5.5, 15=Server 1.0, 16=VMware 6.0, 17=TOT (int) I would suggest creating a file /etc/modprobe.d/vmware with this line: options vmmon vmversion=17 and then /etc/init.d/vmware-server stop; /etc/init.d/vmware-server start. if that doesn't work, try setting vmversion=15. Another problem is, that the vmware-server Debian package seems not to provide multiple bridged interfaces, no multiple NAT-interfaces, and something very annoying, it does NOT provide a way to set the data-dir to something other than /srv/vmware. This should be possible with the debconf interface in an easy way. Also, the mui-package can have a different port than 902 when running vmware-config-mui.pl, which is not available in the Debian package. Why are those vmware-config*.pl files no longer available? Is there an important issue to remove them from the sources? What about providing the same functionality through debconf? This would really be very important, if you want your package to be useable in production environment. the vmware-*.pl install/configure scripts have been removed because they interact poorly with the .deb packaging, and because they're shipped as huge, monolithic scripts (that do stupid things like storing both configuration and primitive package management data in /etc/vmware/locations) that would be extremely difficult to extract needed or excise unwanted functionality from. even if these scripts could be successfully modified, the modified versions could not be distributed in vmware-package. vmware-package is a work in progress; it will take a considerable amount of scripting to be able to replace vmware-config.pl's flexibility in setting up arbitrary vmnet interfaces. by all means, use the vmware-provided tarball+perl distributions if you feel more comfortable with them. I have split this bug into two parts: the any-any compatibility problem and the lack of a good debconf interface. the latter bug has been merged into a similar bug that complains of the same thing. -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#438739: vmware-any-any-patch-113
Am Sun, 26 Aug 2007 13:37:38 +0200 schrieb Daniel Knabl [EMAIL PROTECTED]: I'll be able to provide the informations you need during the following week but not earlier; many thanks for your patience and the fast response. regards Daniel -- Daniel Knabl www.tirolinux.net [EMAIL PROTECTED] PGP/GPG Fingerprint - please send signed mail only A069 671B 39F2 E9B9 FB34 68BB 4BEC 1344 C8A4 3F0B And here we go: dk10:/tmp# make-vmpkg VMware-server-1.0.3-44356.tar.gz [...some output...OK...] dk10:/tmp# ls -la vmware-server/ insgesamt 68268 drwxr-xr-x 2 root root 4096 2007-08-29 20:08 . drwxrwxrwt 8 root root12288 2007-08-29 20:08 .. -rw-r--r-- 1 root root 895 2007-08-29 20:08 vmware-server_1.0.3.44356.0_i386.changes -rw-r--r-- 1 root root 13773074 2007-08-29 20:08 vmware-server_1.0.3.44356.0_i386.deb -rw-r--r-- 1 root root 55848830 2007-08-29 20:08 vmware-server-blobs_1.0.3.44356.0_all.deb -rw-r--r-- 1 root root 172976 2007-08-29 20:08 vmware-server-kernel-source_1.0.3.44356.0_all.deb dk10:/tmp# make-vmpkg -k vmware-any-any-update113.tar.gz [...some output...OK...] dk10:/tmp# ls -la vmware-any-any/ insgesamt 436 drwxr-xr-x 2 root root 4096 2007-08-29 20:11 . drwxrwxrwt 9 root root 12288 2007-08-29 20:11 .. -rw-r--r-- 1 root root559 2007-08-29 20:11 vmware-any-any_113.0_i386.changes -rw-r--r-- 1 root root 102054 2007-08-29 20:11 vmware-any-any-kernel-modules-2.6.22-1-686_113.0+2.6.22-2_i386.deb -rw-r--r-- 1 root root 315260 2007-08-29 20:11 vmware-any-any-kernel-source_113.0_all.deb dpkg -i vmware-any-any/vmware*.deb dpkg -i vmware-server/vmware*.deb [...some output...OK...] All went fine. After this fresh install: dk10:~# uname -a Linux dk10 2.6.22-1-686 #1 SMP Sat Jul 21 06:44:36 UTC 2007 i686 GNU/Linux dk10:~# dpkg -l | grep vmware ii vmware-package0.12 utility for building VMware Debian packages dk10:~# lsmod | grep vm vmnet 33012 13 vmmon1800844 0 dk10:/usr/src# /etc/init.d/vmware-server stop Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet1 done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done Host-only networking on /dev/vmnet8 done Virtual ethernetdone dk10:/usr/src# /etc/init.d/vmware-server start Starting VMware services: Virtual machine monitor done Virtual ethernetdone Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background)done Host-only networking on /dev/vmnet8 (background)done NAT service on /dev/vmnet8 done Starting VMware virtual machines... done When starting the Virtual Machine: Unable to change virtual machine power state: The process exited with an error: End of error message. dk10:/usr/src# cat /tmp/vmware-root/ Aug 29 20:01:00: vmx| Log for VMware Server pid=12768 version=1.0.3 build=build-44356 option=Release Aug 29 20:01:00: vmx| Command line: /usr/lib/vmware-server/bin/vmware-vmx -C -@ /vmware/Debian sid/Debian sid.vmx Aug 29 20:01:00: vmx| vmxvmdb: Index name being generated from config file Aug 29 20:01:00: vmx| VMXVmdbConnectServerd - Trying to discover serverd Aug 29 20:01:00: vmx| MStat: Creating Stat system.cpuusage Aug 29 20:01:00: vmx| MStat: Creating Stat system.ram Aug 29 20:01:00: vmx| MStat: Creating Stat system.uptime Aug 29 20:01:00: vmx| MStat: Creating Stat system.load Aug 29 20:01:00: vmx| Msg_Post: Error Aug 29 20:01:00: vmx| [msg.vmmonPosix.badVersion] Version mismatch with vmmon module: expecting 138.0, got 161.0. Aug 29 20:01:00: vmx| [msg.vmmonPosix.badDriver] You have an incorrect version of the `vmmon' kernel module. Aug 29 20:01:00: vmx| Try reinstalling VMware Server. Aug 29 20:01:00: vmx| Aug 29 20:01:00: vmx| POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 161.0. Aug 29 20:01:00: vmx| You have an incorrect version of the `vmmon' kernel module. Aug 29 20:01:00: vmx| Try reinstalling VMware Server. Aug 29 20:01:00: vmx| Aug 29 20:01:00: vmx| Msg_Post: Error Aug 29 20:01:00: vmx| [msg.vmmonPosix.initFailed] Failed to initialize monitor device. Aug 29 20:01:00: vmx| Aug 29 20:01:00: vmx| POST(no connection): Failed to initialize monitor device. Aug 29
Bug#438739: vmware-any-any-patch-113
Am Sat, 25 Aug 2007 17:22:17 -0400 schrieb Robert Edmonds [EMAIL PROTECTED]: please provide the output from the following commands: uname -a dpkg -l | grep vmware lsmod | grep vm /etc/init.d/vmware-common stop; /etc/init.d/vmware-common start there will usually be log files placed somewhere in /tmp, maybe /tmp/vmware-$USER; please attach these. note that Debian can only provide support for vmware-package, i.e. the Debian package in the archive which generates the vmware-* packages. however, I try to make sure that there are kernel modules which work with the Debian kernels in stable and testing/unstable and that there are no regressions from installing vmware manually to installing from vmware-package generated packages. -- Robert Edmonds [EMAIL PROTECTED] Hi Robert I'll be able to provide the informations you need during the following week but not earlier; many thanks for your patience and the fast response. regards Daniel -- Daniel Knabl www.tirolinux.net [EMAIL PROTECTED] PGP/GPG Fingerprint - please send signed mail only A069 671B 39F2 E9B9 FB34 68BB 4BEC 1344 C8A4 3F0B signature.asc Description: PGP signature
Bug#438739: vmware-any-any-patch-113
Hello again, I've now tried to use the any-any patch version 113, and the installation seemed to work correctly. When I tried to start a machine there was an error message about not beeing able to determine the machine's power state. So I decided to create a new machine and try it again: same result. So there seems to be another issue with the any-any-patch kernel modules. What information will you need to debug this software? What can I provide to assist you in this procedure? Many thanks in advance. regards Daniel -- Daniel Knabl www.tirolinux.net [EMAIL PROTECTED] PGP/GPG Fingerprint - please send signed mail only A069 671B 39F2 E9B9 FB34 68BB 4BEC 1344 C8A4 3F0B signature.asc Description: PGP signature
Bug#438739: vmware-any-any-patch-113
Daniel Knabl wrote: Hello again, I've now tried to use the any-any patch version 113, and the installation seemed to work correctly. When I tried to start a machine there was an error message about not beeing able to determine the machine's power state. So I decided to create a new machine and try it again: same result. So there seems to be another issue with the any-any-patch kernel modules. What information will you need to debug this software? What can I provide to assist you in this procedure? Many thanks in advance. please provide the output from the following commands: uname -a dpkg -l | grep vmware lsmod | grep vm /etc/init.d/vmware-common stop; /etc/init.d/vmware-common start there will usually be log files placed somewhere in /tmp, maybe /tmp/vmware-$USER; please attach these. note that Debian can only provide support for vmware-package, i.e. the Debian package in the archive which generates the vmware-* packages. however, I try to make sure that there are kernel modules which work with the Debian kernels in stable and testing/unstable and that there are no regressions from installing vmware manually to installing from vmware-package generated packages. -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature
