vmware server installation from partners repository in gutsy generates several errors related to xinetd, vmnet, vmmon, vmware-authd, and update-manager

Bug #173261 reported by toobuntu
14
Affects Status Importance Assigned to Milestone
vmware-server (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: vmware-server

Installed vmware-server package from the Canonical partners repository for Gutsy.

See the "IMPORTANT INFORMATION FOR XINETD USERS" and messages about vmnet module, Virtual machine monitor, and Virtual ethernet failing or not being loaded below, near the bottom of this post.

After installation, update-manager displays icon on top panel with a message that there is 1 update available, and aptitude attempts to "safe-upgrade" the vmware-server package from the same version to the same version. This behavior does not cease and also occurred for me in Feisty after aptitude upgraded vmware-server from v1.0.3 to v1.0.4. In Feisty, this behavior occurred even though vmware-server was successfully installed and configured, upgraded, and suitable for production use. As can be seen from the dpkg -s output copied below, installation of vmware-server was okay, but it was not successfully configured, although I am able to open a minimally-functional VMware Server Console.

todd@lap1:~$ cat /etc/issue.net
Ubuntu 7.10

todd@lap1:~$ uname -r
2.6.22-14-rt

todd@lap1:~$ cat /proc/cpuinfo | grep name
model name : Intel(R) Pentium(R) M processor 1.20GHz
todd@lap1:~$ dmesg | grep CPU | grep processor
[ 11.102459] CPU0: Intel(R) Pentium(R) M processor 1.20GHz stepping 08

todd@lap1:~$ dpkg -l | grep vmware
iF vmware-server 1.0.4-1gutsy1 Free virtual machine server from VMware
ii vmware-server-kernel-modules 2.6.22.0-1 vmware-server kernel module dependency packa
ii vmware-server-kernel-modules-2.6.22-14 2.6.22.0-1 vmware-server modules for Linux (kernel 2.6.
ii xserver-xorg-video-vmware 1:10.15.0-0ubuntu1 X.Org X server -- VMware display driver

todd@lap1:~$ dpkg -s vmware-server | grep Status
Status: install ok half-configured

todd@lap1:~$ dpkg -l | grep xinetd
ii xinetd 1:2.3.14-1ubuntu1 replacement for inetd with many enhancements

todd@lap1:~$ cat /var/log/messages|grep vmware #returns nothing
todd@lap1:~$ cat /var/log/messages|grep xinetd #returns nothing

todd@lap1:~$ cat /var/log/messages.log
cat: /var/log/messages.log: No such file or directory

todd@lap1:~$ cat /var/log/daemon.log|grep vmware
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/vmware-authd [file=/etc/xinetd.d/vmware-authd] [line=28]

todd@lap1:~$ cat /var/log/daemon.log | grep xinetd
Dec 1 09:26:01 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=14]
Dec 1 09:26:01 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=28]
Dec 1 09:26:01 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=26]
Dec 1 09:26:01 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Dec 1 09:26:01 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=26]
Dec 1 09:26:01 lap1 xinetd[6242]: removing chargen
Dec 1 09:26:01 lap1 xinetd[6242]: removing chargen
Dec 1 09:26:01 lap1 xinetd[6242]: removing daytime
Dec 1 09:26:01 lap1 xinetd[6242]: removing daytime
Dec 1 09:26:01 lap1 xinetd[6242]: removing discard
Dec 1 09:26:01 lap1 xinetd[6242]: removing discard
Dec 1 09:26:01 lap1 xinetd[6242]: removing echo
Dec 1 09:26:01 lap1 xinetd[6242]: removing echo
Dec 1 09:26:01 lap1 xinetd[6242]: removing time
Dec 1 09:26:01 lap1 xinetd[6242]: removing time
Dec 1 09:26:01 lap1 xinetd[6242]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Dec 1 09:26:01 lap1 xinetd[6242]: Started working: 0 available services
Dec 1 09:31:28 lap1 xinetd[6242]: Starting reconfiguration
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=14]
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=28]
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=26]
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=26]
Dec 1 09:31:28 lap1 xinetd[6242]: Reading included configuration file: /etc/xinetd.d/vmware-authd [file=/etc/xinetd.d/vmware-authd] [line=28]
Dec 1 09:31:28 lap1 xinetd[6242]: removing chargen
Dec 1 09:31:28 lap1 xinetd[6242]: removing chargen
Dec 1 09:31:28 lap1 xinetd[6242]: removing daytime
Dec 1 09:31:28 lap1 xinetd[6242]: removing daytime
Dec 1 09:31:28 lap1 xinetd[6242]: removing discard
Dec 1 09:31:28 lap1 xinetd[6242]: removing discard
Dec 1 09:31:28 lap1 xinetd[6242]: removing echo
Dec 1 09:31:28 lap1 xinetd[6242]: removing echo
Dec 1 09:31:28 lap1 xinetd[6242]: removing time
Dec 1 09:31:28 lap1 xinetd[6242]: removing time
Dec 1 09:31:28 lap1 xinetd[6242]: Swapping defaults
Dec 1 09:31:28 lap1 xinetd[6242]: Reconfigured: new=1 old=0 dropped=0 (services)

todd@lap1:~$ cat /etc/inetd.conf
902 stream tcp nowait root /usr/sbin/vmware-authd vmware-authd

todd@lap1:~$ cat /etc/xinetd.conf
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/

defaults
{

# Please note that you need a log_type line to be able to use log_on_success
# and log_on_failure. The default is the following :
# log_type = SYSLOG daemon info

}

includedir /etc/xinetd.d

todd@lap1:~$ sudo aptitude install vmware-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done
The following NEW packages will be automatically installed:
  libssl0.9.7 vmware-server-kernel-modules
  vmware-server-kernel-modules-2.6.22-14
The following NEW packages will be installed:
  libssl0.9.7 vmware-server vmware-server-kernel-modules
  vmware-server-kernel-modules-2.6.22-14
The following packages will be upgraded:
  xinetd
1 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/83.1MB of archives. After unpacking 139MB will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Preconfiguring packages ...
(Reading database ...
dpkg: serious warning: files list file for package `xinetd' missing, assuming package has no files currently installed.
92063 files and directories currently installed.)
Preparing to replace xinetd 1:2.3.14-1ubuntu1 (using .../xinetd_1%3a2.3.14-1ubuntu1_i386.deb) ...
Unpacking replacement xinetd ...
Selecting previously deselected package vmware-server-kernel-modules-2.6.22-14.
Unpacking vmware-server-kernel-modules-2.6.22-14 (from .../vmware-server-kernel-modules-2.6.22-14_2.6.22.0-1_i386.deb) ...
Selecting previously deselected package vmware-server-kernel-modules.
Unpacking vmware-server-kernel-modules (from .../vmware-server-kernel-modules_2.6.22.0-1_i386.deb) ...
Selecting previously deselected package libssl0.9.7.
Unpacking libssl0.9.7 (from .../libssl0.9.7_0.9.7k-3gutsy1_i386.deb) ...
Selecting previously deselected package vmware-server.
Unpacking vmware-server (from .../vmware-server_1.0.4-1gutsy1_i386.deb) ...
Setting up xinetd (1:2.3.14-1ubuntu1) ...
Stopping internet superserver: xinetd.
Adding `diversion of /etc/init.d/inetd to /etc/init.d/inetd.real by xinetd'
Starting internet superserver: xinetd.

Setting up vmware-server-kernel-modules-2.6.22-14 (2.6.22.0-1) ...

Setting up vmware-server-kernel-modules (2.6.22.0-1) ...
Setting up libssl0.9.7 (0.9.7k-3gutsy1) ...

Setting up vmware-server (1.0.4-1gutsy1) ...
--------- IMPORTANT INFORMATION FOR XINETD USERS ----------
The following line will be added to your /etc/inetd.conf file:

902 stream tcp nowait root /usr/sbin/vmware-authd vmware-authd

If you are indeed using xinetd, you will have to convert the
above into /etc/xinetd.conf format, and add it manually. See
/usr/share/doc/xinetd/README.Debian for more information.
-----------------------------------------------------------

Making sure services for VMware Server are stopped.

Stopping VMware services:
   Virtual machine monitor done

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

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: eth0, eth1.
Which one do you want to bridge to vmnet0? [eth0]

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

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

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes]

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 192.168.163.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 192.168.163.0.

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

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

Configuring a host-only network for vmnet1.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 192.168.14.0/255.255.255.0 appears to be unused.

The following host-only networks have been defined:

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

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

Generating SSL Server Certificate

Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done

todd@lap1:~$ sudo vmware-config-network.pl
Making sure services for VMware Server are stopped.

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 ethernet done

You have already setup networking.

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

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

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

The following virtual networks have been defined:

. vmnet0 is bridged to eth0
. vmnet1 is a host-only network on private subnet 192.168.14.0.
. vmnet8 is a NAT network on private subnet 192.168.163.0.

Do you wish to make any changes to the current virtual networks settings?
(yes/no) [no] yes

Which virtual network do you wish to configure? (0-99) 1

The network vmnet1 has been reserved for a host-only network. You may change
it, but it is highly recommended that you use it as a host-only network. Are
you sure you want to modify it? (yes/no) [no] yes

What type of virtual network do you wish to set vmnet1?
(bridged,hostonly,nat,none) [hostonly]

Configuring a host-only network for vmnet1.

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

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] no

What will be the IP address of your host on the private
network? 192.168.81.11

What will be the netmask of your private network? 255.255.255.0

The following virtual networks have been defined:

. vmnet0 is bridged to eth0
. vmnet1 is a host-only network on private subnet 192.168.81.0.
. vmnet8 is a NAT network on private subnet 192.168.163.0.

Do you wish to make additional changes to the current virtual networks
settings? (yes/no) [yes]

Which virtual network do you wish to configure? (0-99) 8

The network vmnet8 has been reserved for a NAT network. You may change it, but
it is highly recommended that you use it as a NAT network. Are you sure you
want to modify it? (yes/no) [no] yes

What type of virtual network do you wish to set vmnet8?
(bridged,hostonly,nat,none) [nat]

Configuring a NAT network for vmnet8.

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

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] no

What will be the IP address of your host on the private
network? 192.168.88.11

What will be the netmask of your private network? 255.255.255.0

The following virtual networks have been defined:

. vmnet0 is bridged to eth0
. vmnet1 is a host-only network on private subnet 192.168.81.0.
. vmnet8 is a NAT network on private subnet 192.168.88.0.

Do you wish to make additional changes to the current virtual networks
settings? (yes/no) [yes] no

Generating SSL Server Certificate

Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

todd@lap1:~$ cat /tmp/vmware-todd/ui-7171.log
Dec 01 10:00:02: vmui| Log for VMware Server pid=7171 version=1.0.4 build=build-56528 option=Release
Dec 01 10:00:02: vmui| Using log file /tmp/vmware-todd/ui-7171.log
Dec 01 10:00:02: vmui| HAL04LoadHALLibraries: Could not dlopen libhal.so.0.
Dec 01 10:00:02: vmui| HAL05LoadHALLibraries: Could not dlopen libdbus-1.so.1 or libdbus-1.so.2.
Dec 01 10:00:03: vmui| HostDeviceInfoFindHostIDECDROMs: /proc/ide could not be explored. Unable to enumerate host IDE cdroms.
Dec 01 10:00:03: vmui| SMBIOS: can't open /dev/mem
Dec 01 10:00:03: vmui| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.
Dec 01 10:00:03: vmui| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 1.
Dec 01 10:00:03: vmui| HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 1 logical CPUs.
Dec 01 10:00:03: vmui| Using system libcrypto, version 9070BF
Dec 01 10:00:03: vmui| Gtk: Refusing to add non-unique action 'ListNewTeamAction' to action group 'App Actions'
Dec 01 10:00:04: vmui| Dlg::GetButtonInfo(): Duplicate GTK icon/label pair: _Stop and _Stop
Dec 01 10:00:04: vmui| Dlg::GetButtonInfo(): Duplicate GTK icon/label pair: _Forward and _Forward
Dec 01 10:00:04: vmui| Dlg::GetButtonInfo(): Duplicate GTK icon/label pair: _Information and Information
Dec 01 10:00:04: vmui| VmdbVmCfg_UpdateFile: Could not load dictionary file /home/todd/.vmware/preferences: Unable to get information about file "/home/todd/.vmware/preferences": No such file or directory.
Dec 01 10:00:04: vmui|
todd@lap1:~$

todd@lap1:~$ sudo aptitude safe-upgrade
[sudo] password for todd:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages will be upgraded:
  vmware-server
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/79.4MB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n/?] y
Preconfiguring packages ...
(Reading database ... 93132 files and directories currently installed.)
Preparing to replace vmware-server 1.0.4-1gutsy1 (using .../vmware-server_1.0.4-1gutsy1_i386.deb) ...
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 ethernet done
Unpacking replacement vmware-server ...
Setting up vmware-server (1.0.4-1gutsy1) ...
Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

invoke-rc.d: initscript vmware-server, action "start" failed.
dpkg: error processing vmware-server (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 vmware-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up vmware-server (1.0.4-1gutsy1) ...
Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

invoke-rc.d: initscript vmware-server, action "start" failed.
dpkg: error processing vmware-server (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 vmware-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
todd@lap1:~$ sudo aptitude dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages will be upgraded:
  vmware-server
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/79.4MB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Preconfiguring packages ...
(Reading database ... 93132 files and directories currently installed.)
Preparing to replace vmware-server 1.0.4-1gutsy1 (using .../vmware-server_1.0.4-1gutsy1_i386.deb) ...
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 ethernet done
Unpacking replacement vmware-server ...
Setting up vmware-server (1.0.4-1gutsy1) ...
Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

invoke-rc.d: initscript vmware-server, action "start" failed.
dpkg: error processing vmware-server (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 vmware-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up vmware-server (1.0.4-1gutsy1) ...
Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

invoke-rc.d: initscript vmware-server, action "start" failed.
dpkg: error processing vmware-server (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 vmware-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
todd@lap1:~$

As instructed during the installation, and per /usr/share/doc/xinetd/README.Debian, I added the -inetd_compat option to /etc/default/xinetd:
todd@lap1:~$ tail /etc/default/xinetd
# Default settings for xinetd. This file is sourced by /bin/sh from
# /etc/init.d/xinetd

# Options to pass to xinetd
#
# -stayalive comes by default : it can be removed if xinetd is expected
# not to start when no service is configured
#
XINETD_OPTS="-stayalive -inetd_compat"

todd@lap1:~$ sudo /etc/init.d/xinetd restart
Stopping internet superserver: xinetd.
Starting internet superserver: xinetd.

todd@lap1:~$ sudo aptitude dist-upgrade #failed as above

todd@lap1:~$ sudo /etc/init.d/xinetd reload
Reloading internet superserver configuration: xinetd.

todd@lap1:~$ sudo aptitude dist-upgrade #failed as above

todd@lap1:~$ sudo modprobe vmmon
FATAL: Module vmmon not found.
todd@lap1:~$ sudo modprobe vmnet
FATAL: Module vmnet not found.
todd@lap1:~$ sudo modprobe vmware-authd
FATAL: Module vmware_authd not found.

toobuntu (toobuntu)
description: updated
toobuntu (toobuntu)
description: updated
toobuntu (toobuntu)
description: updated
description: updated
toobuntu (toobuntu)
description: updated
Revision history for this message
Stapel (wstapelberg) wrote :

I think I have the same problem. This is what I get when I run dpkg --configure -a after failed install of vmware-server with update manager:

stapel@stapel-laptop:~$ sudo dpkg --configure -a
[sudo] password for stapel:
Setting up vmware-server (1.0.4-1gutsy2) ...
Starting VMware services:
   Virtual machine monitor failed
   Virtual ethernet failed
Module vmnet is not loaded. Please verify that it is loaded before
running this script.

invoke-rc.d: initscript vmware-server, action "start" failed.
dpkg: error processing vmware-server (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 vmware-server
stapel@stapel-laptop:~$

Revision history for this message
toobuntu (toobuntu) wrote :

Changing status to confirmed because of comment here and at the following links:

http://ubuntuforums.org/showthread.php?p=3904081#post3904081
http://users.piuha.net/martti/comp/ubuntu/en/server.html#7

Changed in vmware-server:
status: New → Confirmed
Revision history for this message
Kameleon (kameleon25) wrote :

Same thing here. Only was working before upgrade to Gutsy. I performed the upgrade last night. Today vmware will not load a virtual machine.

Revision history for this message
vigalinux (vigalinux) wrote :

I get the same issue installing package vmware-server 1.0.4-1gutsy2

I am networked only via wifi.

During installation, I would like to choose manually the vmnet0 bridged to my wlan1 connected to internet, this is not an automatic possible choice.

See my ifconfig in:
Bug #112492, first reported on 2007-05-04 by Jordan
vmware-server install ( from Feisty commercial repository ) fails if you don't have an eth0

Revision history for this message
toobuntu (toobuntu) wrote :

Update:

I am heartened by the lack of any response here from a developer that the crew is quite busy preparing for Hardy or is otherwise occupied.

By way of an update, I was thinking the vmnet error could either be due to a faulty kernel module or to the defaults in the config-network script as in https://bugs.launchpad.net/bugs/112492. All previous attempts to install vmware-server were on a Sony Vaio laptop with only the wireless interface active at the time (eth1); eth0 (wired) was simply not plugged in. So I brought my laptop to the office, plugged in the wire and left wireless active as well. Still no go. Then I rebooted from the realtime kernel into the generic kernel, and the installation succeeded.

Please note, however, that the package description for vmware-server-kernel-modules-2.6.22-14 states the following: "All supported kernel types for this architecture are included in this single package." Also, installing vmware-server-kernel-modules in the lowlatency kernel in Feisty did not cause this error; the installation completed successfully,

Revision history for this message
Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in vmware-server (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.