| 1 |
On 10/20/2011 12:56 PM, Andrey Moshbear wrote: |
| 2 |
> On Thu, Oct 20, 2011 at 05:53, Stefan G. Weichinger<lists@×××××.at> wrote: |
| 3 |
>> Am 19.10.2011 23:14, schrieb Mark Knecht: |
| 4 |
>> |
| 5 |
>>> I've decided to stick with vmware-player-3.1.4 for use as a Netflix VM |
| 6 |
>>> only. All of my real work is done in Virtualbox VMs using both 32-bit |
| 7 |
>>> NT and 64-bit Win 7. The only problem I've had recently is that my |
| 8 |
>>> dual monitor Win 7 VM tends to 'abort' about 40% of the time when |
| 9 |
>>> starting. Once it's up and running it's fine, but getting it started |
| 10 |
>>> on any day is pretty much hit-or-miss. |
| 11 |
>> |
| 12 |
>> hmm, nothing I long for --- |
| 13 |
>> |
| 14 |
>> I stay w/ vmware-player-3.1.5 for now (out of vmware-overlay). |
| 15 |
>> |
| 16 |
>> Thanks, S |
| 17 |
>> |
| 18 |
> |
| 19 |
> I've had rather pleasant experiences with virtualbox. Less |
| 20 |
> libhell/libnazism, too. |
| 21 |
> Plus, less drivers to modprobe (just vboxdrv, vboxnet as needed) |
| 22 |
> instead of the 4 or so needed for vmware. |
| 23 |
|
| 24 |
You don't modprobe. There's /etc/init.d/vmware which you add to the |
| 25 |
default runlevel or simply start manually with "/etc/init.d/vmware start". |
Archives