Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.electronics.design > #451704

Re: VMware v VirtualBox

Show all headers | View raw

On 3/13/2017 3:37 PM, Jon Elson wrote:
> 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.

+1

It also makes it easier to make smaller, more "focused" VM's and pass
files between VM's (i.e., treat the VM *as* an application instead of
a complete system).

So, I can create a schematic using a schematic editor hosted by a
particular guest OS instance.  Then, layout the PCB using a layout tool
hosted in a *different* guest OS instance (perhaps even a different
guest OS)

Otherwise, the VM's get bulkier and you end up with more duplication
of applications ("Ah, I need this app in this machine... and this other
machine...")

> This does seem
> easier on VirtualBox than VMWare, but both can do this.

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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