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,
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,