Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #451524
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | sci.electronics.design |
| Subject | Re: VMware v VirtualBox |
| Date | 2017-03-12 14:23 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <oa4e3q$nna$1@dont-email.me> (permalink) |
| References | <oa2mg6$7u3$1@dont-email.me> <6ZdxA.19685$u84.10676@fx35.iad> <oa47uo$1r5$1@dont-email.me> <MEhxA.17481$7b3.338@fx18.iad> |
On 3/12/2017 12:51 PM, bitrex wrote: > 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." Under VMware, you typically use the wizard and just answer multiple choice questions (including "Typical" if you don't have any idea as to the "best" answer for a particular question). There are some issues if the host filesystem has constraints that carry into the guest OS (e.g., the machine's virtual memory can't be larger than the largest supported file size on the host OS's filesystem on which it will be created). And, whether the guest machine will have a separate IP address from the host, etc. [ISTR there is also a question re: supported SCSI HBA vs. IDE, etc.] There's also the choice of whether to use a vdisk or a *physical* disk for the OS (on one of my machines, I use hot-swappable drives as a quick and dirty way to just "pick" the guest OS). And, I think there is an upper limit on the size of the disks that you can support (though I tend to want small disks as each machine is really only created for some specific task instead of as a "general workstation" -- which might need gobs of space for applications) But, these sorts of things are usually not important if you just want to slap together a 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 IME, the biggest "adjustment" is to the whole concept of a machine within a machine. The biggest *risk* coming from tools that have particular hardware requirements that the virtual machine can't emulate.
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