The only real annoyance is the fetch restriction.Code:ebuild `equery which app-emulation/vmware-modules-264.0` prepare && wget -O - "http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/08/patch3031vmware741.patch" | patch -d /var/tmp/portage/app-emulation/vmware-modules-264.0/work -p1 && ebuild `equery which app-emulation/vmware-modules-264.0` merge
Last edited by deanjo; 10-11-2011 at 04:27 PM. Reason: to make the forums a bit more readable
Just posting to say that indeed I've experienced major file system and memory corruption when trying to use Gentoo in Virtualbox as a development machine. I'd be lucky to make it through a single kernel compile.
After loosing so many filesystems (it literally trashed them beyond repair), i've switched to VMware. No more problems.
It's a shame Oracle doesn't put more support behind Virtualbox to get the quality up to standards. Have you looked at the frequent changelogs? They are a disaster if you care about stability.
Vmware's biggest problem is the lack of frequent updates to follow the latest kernel. But if you don't need to be on the bleeding edge, it works great.
We were teased about some potentially new and interesting VB features... but haven't heard anything since.
vbox or vmware are well running linux under windows . recently i use vmware 7&8 and it is real good when it comes to have 64bit working with a 32bit win xp . i use mostly mksquashfs to compile the live file , it seemed and continue to seem with new xp x64 as fast as under plain linux
i switched to xp x64 and vmware 8 , the new vmware is largely better with the usb stick than previous .
n.b. : running win 7 x64 under xp was nearly impossible
Just a quick(ish) comment as a member of the VirtualBox development team. I have only used VMWare a couple of times, so I won't comment on them or on comparisons to them (though I see that there are enough people with strong opinions in either direction, so I suspect there is an element of one failed to work as well as the other in some given situation). I do think though that Dave was a bit quick with name calling when he started the LKML thread. If you read his first post, it starts "The number of bug reports we get from people with virtualbox loaded are truly astonishing." Given that our kernel module is usually loaded when our software is installed, even if it is not currently in use, it is hardly surprising that people occasionally have kernel oopses when the module is present. I'm sure that some are related to our module (particularly as many people still use old versions with known issues), but assuming that even a large minority are is quite a jump.
Other than that, I'm very sorry that VirtualBox didn't fit all previous posters needs. Obviously there is always a bit of pressure between being conservative with new features and still providing the features everyone (and our customers!) want. I realise that IOMMU is still work in progress and that USB is not always problem-less (USB devices tend to be finicky creatures, just ask some of the people writing drivers for device classes!). Those wanting less features and more stability might note that we are still maintaining the 4.0 and 3.2 series. And people having issues with some particular kernel setup should note that we are open source and accept patches