On Tue 16 Oct 2007 08:49:57 NZDT +1300, Vik Olliver wrote: > I've found vmware a nightmare, particularly when it doesn't understand a > latest kernel release,
Each time I get a new kernel, I run vmware-config.pl (or whatever it's called), hitting enter on all the defaults. Problem fixed. In fact, the vmware service init script does this automagically, so all that's needed is restart vmware. It needs the kernel source installed though, and I haven't taken the time to find out whether just some of the headers would suffice. > or when you've got a custom kernel it disagrees > with. I hate custom kernels anyway. You do have a very good reason for those custom kernels? Did you add truckloads of inofficial patches into your kernel sources? And you did start with your vendor kernel and modified it only as much as needed? > Qemu is slower but much more reliable - and the network interfaces > actually work. I've never seen trouble with vmware network interfaces. When I tested out firewalls I had 3 network cards in each virtual machine, all interfacing to the host. It worked as expected. > No special kernels required and it runs on anything. How extensive is qemu's hardware support? USB? Firewire? Sound card *recording input*? Does it have the useless-system-time-keeping feature of vmware? Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
