vmware (vmnet is not loaded) issue after kernel update

[marc]

Bruce Marshall said...
> On Wednesday 25 June 2008, P Kapat wrote:
> > I had a similar issue with virtualbox modules, in Hardy though. IIRC
> > there was no module for 2.6.24-18. So I waited before upgrading from
> > 2.6.24-17. And recently 2.6.24-19 was available along with
> > virtualbox-ose-modules compiled for it. So, I guess the moral is to do
> > a manual check before an upgrade. If things don't look good, either
> > pin then or hold them for the time being. Wait it out!
> 
> Well yes....  but virtual box  provides the ability to recompile their module 
> and I have never had a problem with it,   through -19 on Hardy.
> 
> /etc/init.d/vboxdrv setup
> 
> will compile the module for each new kernel. 

Dispassionately, is virtualbox 'better' than vmware? Pros. Cons?

-- 
Cheers,
Marc