Groups > sci.electronics.design > #451687

Re: VMware v VirtualBox

From	Jon Elson <jmelson@wustl.edu>
Organization	Washington University
Date	2017-03-13 17:37 -0500
Subject	Re: VMware v VirtualBox
Newsgroups	sci.electronics.design
References	(1 earlier) <6ZdxA.19685$u84.10676@fx35.iad> <oa47uo$1r5$1@dont-email.me> <MEhxA.17481$7b3.338@fx18.iad> <oa4e3q$nna$1@dont-email.me> <_VxxA.82555$IM7.6366@fx39.iad>
Message-ID	<mJudnbDIo7uaglrFnZ2dnUU7-T2dnZ2d@giganews.com> (permalink)

Show all headers | View raw

bitrex wrote:

> On 03/12/2017 05:23 PM, Don Y wrote:
> 
>> 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)
> 
> One thing I learned the hard way is that with one particular application
> I had to save any work I did to a shared folder on the host OS -
> sometimes when I saved work from it to the vdisk, restarted the virtual
> machine and attempted to open the file I'd find that it had been
> corrupted.
> 
What I do now is have the virtual guest OS's user directory on the host OS.
That way, the files are available to the host OS even when the VM is not 
running, and it gets backed up with the host OS files.  This does seem 
easier on VirtualBox than VMWare, but both can do this.

Jon

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