Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #451513
| Subject | Re: VMware v VirtualBox |
|---|---|
| Newsgroups | sci.electronics.design |
| References | <oa2mg6$7u3$1@dont-email.me> <6ZdxA.19685$u84.10676@fx35.iad> <oa47uo$1r5$1@dont-email.me> |
| From | bitrex <bitrex@de.lete.earthlink.net> |
| Message-ID | <MEhxA.17481$7b3.338@fx18.iad> (permalink) |
| Organization | frugalusenet - www.frugalusenet.com |
| Date | 2017-03-12 15:51 -0400 |
On 03/12/2017 03:38 PM, Don Y wrote: > On 3/12/2017 8:39 AM, bitrex wrote: >> On 03/12/2017 12:34 AM, Don Y wrote: >>> A colleague asked for my opinions of the two. But, I only >>> run VMware. Some googling turns up LOTS of hits re: this >>> issue. But, all seem to be pretty "sterile" writings. >>> >>> Anyone with experience with *both* (or, who left one in favor >>> of the other) to share some first-hand experiences? >>> >>> [AFAICT, he's looking for this as a way of supporting legacy >>> tools w/o dedicating hardware to the task] >> >> For just a single machine to supporting legacy tools, rather than >> "enterprise" >> I prefer VirtualBox. > > Why? (As I say, my only experience is with VMware -- and Sun's Chimera, > but > that's a different fish) I'd imagine building the first virtual machine is > a bit of an effort in *either* environment. But, thereafter, just "more of > the same" It's dead-simple in Vbox. Select the size you want for the new image drive, choose the amount of system memory to be allocated to your machine, select an ISO file and let it install to the virtual drive, and hit "start machine." Once inside the VM you can download and install the "Guest Addons" package which adds stuff like shared host folders, USB passthru and 2D acceleration for desktop graphics. After that it's the same as configuring any other physical machine
Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-11 22:34 -0700
Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-12 11:39 -0400
Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-12 12:38 -0700
Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-12 15:51 -0400
Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-12 14:23 -0700
Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-13 10:21 -0400
Re: VMware v VirtualBox Gerhard Hoffmann <ghf@hoffmann-hochfrequenz.de> - 2017-03-13 16:57 +0100
Re: VMware v VirtualBox Jon Elson <jmelson@wustl.edu> - 2017-03-13 17:37 -0500
Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-13 17:20 -0700
Re: VMware v VirtualBox Martin Riddle <martin_ridd@verizon.net> - 2017-03-12 16:08 -0400
Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-12 15:37 -0400
Re: VMware v VirtualBox Jasen Betts <jasen@xnet.co.nz> - 2017-03-13 11:18 +0000
Re: VMware v VirtualBox Jon Elson <jmelson@wustl.edu> - 2017-03-13 17:33 -0500
Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-14 09:42 -0700
csiph-web